User Guide
Integrations
Meta (Facebook)

Meta (Facebook/Instagram) Integration

Connect Convultra to Meta to send conversions directly through the Conversions API. This recovers conversions lost to iOS 14.5+ App Tracking Transparency, ad blockers, and browser cookie restrictions — giving Meta better data to optimize your campaigns.

Why connect Meta?

  • Recover iOS 14.5+ conversions — When users opt out of tracking on iOS, Meta's pixel cannot track them. Convultra sends the conversion data server-side, bypassing the restriction entirely.
  • Better campaign optimization — More conversion data means Meta's delivery algorithm can find the right audiences more efficiently.
  • Server-side event matching — Meta's Conversions API uses multiple identifiers to match conversions to ad interactions, resulting in higher match rates than the pixel alone.
  • Automatic deduplication — If you are also running the Meta Pixel, Convultra deduplicates events so Meta never counts the same conversion twice.

Requirements

  • A Meta Business account
  • Access to the ad account you want to connect
  • An active Convultra project with the SDK installed on your website

Setup Steps

Go to Integrations

Navigate to Dashboard → Integrations in Convultra. Find the Meta card and click Connect.

Sign in with Facebook

A Facebook sign-in window will appear. Sign in with the account that has access to your Meta Business suite and ad account. Convultra uses OAuth, so your password is never shared.

💡

Make sure you sign in with an account that has admin or advertiser access to the ad account you want to connect. View-only access will not work.

Select Your Meta Ad Account

After signing in, you will see a list of ad accounts associated with your Meta Business account. Select the one you want to connect.

Configure Pixel ID (Optional)

If you are also running the Meta Pixel on your website, enter your Pixel ID here. This allows Convultra to deduplicate events — so conversions tracked by both the pixel and Convultra are only counted once by Meta.

You can find your Pixel ID in Meta Events Manager under Data Sources → Your Pixel → Settings.

If you are not using the Meta Pixel (or plan to rely entirely on Convultra's server-side tracking), you can skip this step.

Enable Enhanced Conversions (Optional)

Toggle on Enhanced Conversions to send hashed customer data (such as email address or phone number) alongside your conversions. This significantly improves Meta's ability to match conversions to the correct ad interactions.

See the Enhanced Conversions guide for more details on what data is sent and how it is protected.

Send a Test Conversion

Click Send Test Conversion in the Test Center. Convultra will send a test event to Meta's Conversions API and display the result.

A green confirmation means Meta received the event successfully. Your integration is live and ready to send real conversions.

You are all set

Conversions will now be forwarded to Meta automatically through the Conversions API.

Features

Conversions API

Convultra sends all conversion events through Meta's official Conversions API. This is the same server-to-server connection that Meta recommends for reliable conversion tracking, and it is not affected by ad blockers, browser privacy settings, or iOS restrictions.

Pixel Backup and Deduplication

If you are running the Meta Pixel alongside Convultra, both systems may capture the same conversion. Convultra handles this by including a unique event ID with each conversion, allowing Meta to automatically deduplicate and count each conversion only once.

iOS 14.5+ Recovery

Conversions from users who opted out of tracking via Apple's App Tracking Transparency prompt are invisible to the Meta Pixel. Because Convultra operates server-side, these conversions are captured and delivered to Meta regardless of the user's iOS tracking preference.

Test Center

Use the Test Center at any time to verify your connection to Meta is working. The test sends a synthetic event and confirms delivery.

Forward Logs

View every conversion sent to Meta in the Forward Logs tab. Each log entry includes:

  • Timestamp
  • Event name and data
  • Delivery status
  • Match quality score (how well Meta was able to match the conversion)
  • Error details (if any)

Good to Know

OAuth tokens refresh automatically. You will not need to re-authenticate unless you revoke Convultra's access from your Meta Business settings.

For technical setup details (SDK installation, event tracking code, or advanced Conversions API configuration), see the Developer Docs.