Skip to content New SourceLoop MCP: chat with your attribution data in Claude, ChatGPT & Cursor
SourceLoop
Meta Ads

How to Sync Revenue and Offline Conversions in Meta Ads

Send SourceLoop's real leads, qualified leads, won deals, and payments to Meta through the Conversions API. Find your Pixel ID, create a System User token, and pick the event for each moment.

On this page
  1. Before you start
  2. Step 1: Find your Pixel ID
  3. Step 2: Create a System User access token
  4. Step 3: Create the sync in SourceLoop
  5. Step 4: Check that events arrive
  6. What’s next

Meta’s browser pixel sees a form fill. It never sees the lead your team qualified, the deal that closed a month later, or the subscription that renewed. This guide sends those moments to Meta through the Conversions API, so its algorithm learns from customers instead of clicks.

For what conversion sync can do across every platform, see the Conversion sync overview.

Before you start

  • Meta Ads connected to SourceLoop
  • Access to Meta Events Manager and Business Settings for the business that owns your pixel
  • An Admin or Editor role in SourceLoop

Step 1: Find your Pixel ID

  1. Open Meta Events Manager.
  2. Pick the pixel or dataset connected to the ad account you use with SourceLoop.
  3. Copy the Pixel ID from the Overview or Settings tab.

Step 2: Create a System User access token

  1. In Meta Business Settings, open Users, then System Users.
  2. Select an existing System User or click Add to create one, for example “SourceLoop”.
  3. Click Assign assets, choose your pixel, and give it at least Standard access.
  4. Click Generate new token, pick your app, and generate the token.
  5. Copy the token. Meta shows it only once.

Step 3: Create the sync in SourceLoop

  1. In SourceLoop, open Activation, then Conversion sync.
  2. Pick a template, such as Good leads with value or Won deals with revenue, or click New sync.
  3. Under Send to, pick your Meta ad account. The first time, SourceLoop asks for:
    • Meta Pixel ID from Step 1
    • System User Access Token from Step 2
    • Test event code (optional), if you want to check sends in Test events first
  4. Click Save pixel.
  5. Under When, pick the moment to send.
  6. Under Send as, keep the suggested standard event or pick another. Choose Use a custom event name to type your own.
  7. Set the Value, keep Who counts on People Meta brought, and choose Last click or First click.
  8. Optionally turn on Send past conversions to include the last 7 days.
  9. Check the preview, then click Save.

Meta matches each person by their ad click when SourceLoop has it, and by hashed email and phone otherwise, which raises match quality.

Step 4: Check that events arrive

  1. In SourceLoop, open the sync and look at Recent sends. Each person sent is listed with what Meta matched on.
  2. In Events Manager, open your pixel. With a test code set, events appear under Test events within a few minutes. Without one, they appear in the pixel’s overview.
  3. Once you’re happy, remove the test code from the sync. While it is set, the sync shows Test mode and Meta doesn’t use the events for ads.

What’s next

Frequently asked questions

  1. Where do I find my Meta Pixel ID?

    In Meta Events Manager. Pick the pixel or dataset connected to your ad account. The ID is the long number shown on its Overview and Settings tabs.

  2. Why a System User token instead of my own?

    A System User is a service account in your Meta Business. Its token doesn't expire the way a personal token does, so your conversions keep flowing when someone changes their password or leaves the company.

  3. Which Meta event does each moment use?

    SourceLoop suggests one per moment. Every conversion goes as Lead, a Good lead as QualifiedLead, won deals and payments as Purchase, trials as StartTrial, and new subscriptions as Subscribe. A stage such as SQL goes under its own name, so you can build a custom conversion on exactly that stage. You can change any of them, or type a custom event name.

  4. Will this double count with my browser pixel?

    Only if both send the same event for the same person. The cleanest setup is to send SourceLoop's moments under events your pixel doesn't fire, such as QualifiedLead or Purchase for a won deal, or under a custom event name.

  5. How do I test without affecting my campaigns?

    In Events Manager, open Test events and copy the test code. Paste it into the Test event code field in SourceLoop. Sends then show in Test events only and are not used for ads. Remove the code once you've checked them, because a sync in test mode never reaches your campaigns.

  6. How far back can I send past conversions?

    Seven days. Meta rejects events older than that, so a new sync can include up to the last 7 days when you turn on Send past conversions.

Track every conversion to its true source

Capture and send full attribution data from every signup, lead, booking, and sale to your CRM and ad platforms, so you know exactly what's driving revenue.

Without SourceLoop

Untagged

Kayden Floyd

kayden@abc.com

  • SourceUnknown
  • MediumUnknown
  • CampaignUnknown
  • Landing pageUnknown
Journey
No touchpoints captured

With SourceLoop

Auto-tagged

Kayden Floyd

kayden@abc.com · Acme Co.

  • Channel Paid Social
  • CampaignFree_demo
  • Landing page/pricing
Journey
Synced to HubSpot Google Ads Meta