Setting Up Meta Reverse Sync (Conversions API)

Goal: Report lead outcomes back to Meta so your ad campaigns can optimize for leads that actually convert, not just form fills.

This tutorial walks you through enabling the Conversions API integration in VBRI Group CRM. When you complete these steps, every time a lead's status changes (e.g., from Contacted to Qualified) or a deal closes, VBRI Group will automatically send that event to your Meta pixel—helping Meta's algorithm refine your audience targeting.

Time required: ~5 minutes
Requirements: VBRI Group admin access; Facebook already connected via a Lead Chain

Prerequisites

Before starting, confirm:

1. You've already connected Facebook once via a Lead Chain (see the Facebook Lead Ads Setup tutorial's Connect Facebook Account step). Meta Reverse Sync reuses that same connection — there's no separate "connect" step for Conversions API.
2. You have admin access to the Facebook ad account that owns (or has been granted) the pixel you'll use to report events.
3. You understand that Meta Reverse Sync only reports events for leads captured via Meta Lead Ads. Leads from other sources (Website forms, manual entry, etc.) will not be sent to Meta.

Step 1: Open Settings → Integrations

1. Click Settings in the sidebar.
2. Click Integrations in the left menu.
3. Scroll down to the Meta Reverse Sync (Conversions API) card.

Step 2: Enable Meta Reverse Sync

1. On the Meta Reverse Sync (Conversions API) card, check the box next to the Enabled/Disabled badge in the top-right so it reads Enabled.

The Business Manager picker, pixel picker, and event-mapping fields below are always visible in this card — you can review or change them whether or not the integration is enabled, but events only send once it's Enabled.

Step 3: Connect Your Business Manager Account

1. In the same card, find the Connect your Business Manager Account picker.
2. Click it to open a dropdown list of Business Managers linked to your connected Meta account.
3. Select the Business Manager that owns (or has access to) the pixel you want to use.
4. The picker confirms your selection and closes.

Step 4: Choose Your Pixel

1. Find the Choose your Pixel picker below the Business Manager selection.
2. Click it to open a dropdown with two tabs: Owned Pixels and Client Pixels.
   • Owned Pixels: Pixels your Business Manager owns directly.
   • Client Pixels: Pixels that have been shared with your Business Manager by a client (useful for agencies).
3. Select the appropriate tab based on where your pixel lives.
4. Click the pixel you want to use. Its name and ID are displayed.
5. The dropdown closes. The pixel is now selected.

Step 5: Map Lead Status Events

Define which Meta event to send when a lead's status changes. Each status is optional—leave it blank to skip that stage.

1. In the Meta Reverse Sync card, find the section for status event mappings. You'll see fields for:

   • Contacted
   • Qualified
   • Lost

2. For each status you want to track:

   • Click the text field.
   • Enter the Meta event name you want to send (e.g., "Appointment" for Qualified, "Lead" for Contacted, "Disqualified" for Lost).
   • Leave the field empty if you don't want to send an event for that status.

3. When a lead's status changes in VBRI Group, the mapped event will be sent to Meta.

Step 6: Enable and Name the Deal-Won Event

When a deal is marked won in VBRI Group, you can also send a special conversion event to Meta (useful for ad optimization).

1. Find the Deal-won event toggle in the card.
2. Toggle it On.
3. In the Event name field that appears (pre-filled with "Purchase"), enter the event name you want Meta to receive (or keep the default).
4. If the deal has a value set, it's automatically included in the event data sent to Meta.

Step 7: Understand What Data Gets Sent

When VBRI Group sends an event to Meta, it includes:

• Contact fields (whichever the lead has): email, phone, name, city, zip, country.
• Hashing: All contact details are hashed with SHA-256 before leaving VBRI Group, so Meta receives only a fingerprint—not the raw contact info.
• Eligibility: Only leads captured via Meta Lead Ads are eligible for reverse sync. Meta uses the original leadgen ID from the form submission to attribute the conversion event to the right ad.
• Privacy: This integration shares SHA-256 hashes of customer contact details with Meta. Before enabling, confirm your privacy policy and terms of service cover this data sharing.

Step 8: Save and Confirm Events Are Firing

1. Scroll to the bottom of the Integrations page.
2. Click Save Integrations.
3. A green "✓ Integration settings saved" banner confirms it.

To verify events are being sent:

1. Go to your Leads page.
2. Find a lead captured from Meta Lead Ads.
3. Change its status to Contacted (or another mapped status) and save.
4. Within a few seconds, VBRI Group sends the event to Meta. (You won't see a confirmation in VBRI Group, but you can verify in Meta's Conversions API dashboard if needed.)
5. To test the deal-won event, move an opportunity to your Closed Won stage on the Opportunities page. The event will fire automatically.

Troubleshooting

• No pixel appears in the picker: Confirm that the Business Manager you selected has access to the pixel (either owns it or has it shared from a client).
• Events not appearing in Meta: Verify that:
  • The lead was originally captured via Meta Lead Ads (not another source).
  • The lead has at least one match field on file — email, phone, name, city, zip, or country (Meta needs at least one to reconcile the event).
  • Enable Conversion Leads optimization in your Meta ad campaign to use these signals.
• Pixel name disappears after reload: This is expected. The pixel's display name is not persisted in VBRI Group. After a page reload, you'll see only the pixel ID until you reopen the picker—the pixel selection itself remains active.

Next: Once your events are flowing, log into Meta Ads Manager and enable Conversion Leads optimization in your campaigns so Meta can use these signals to improve targeting.