Connect this destination to export audience membership as an Audience Membership event, or to write warehouse conversion events onto your Facebook pixel, for use in Events Manager.

This destination writes to your Meta account and is a good fit when you want to:

Make anonymous website visitors available for Facebook ads
Get measurement from warehouse conversion events

This maps to GrowthLoop Audiences and Syncs:

Use it for	Audiences	Syncs
Sending anonymous website visitors as an Audience Membership event	✓
Sending conversion events for measurement		✓
Sending events to the Advanced Measurement API		✓

To export known customers with match fields, use Facebook Ads. Do not use that destination for anonymous visitors or conversion events.

Prerequisites

Make sure you have:

A Facebook business account and the Ad Account that should receive events.
Your Pixel ID. Create one with Meta's pixel instructions, or copy an existing ID from Ads Manager → Events Manager. See Meta's Events Manager help.

If you will export anonymous website visitors, you also need:

MetaRouter set up on your website or application so page views, clicks, and other activity flow into your warehouse. See MetaRouter's getting started guide. GrowthLoop can help you complete this setup.
Anonymous user and event data consolidated in your warehouse so you can build GrowthLoop datasets and filter audiences. GrowthLoop can help you structure that data.

If you will sync to the Advanced Measurement API, set Advanced Measurement Table when you connect the destination.

Set up Facebook Conversions as a destination

In GrowthLoop, click the Destinations tab on the left sidebar.
Click New Destination in the upper right corner.
Search for Facebook Conversions and click Add Meta / Facebook Conversions.

Log in to Facebook with the business account that owns the pixel and Ad Account.
Enter the required information, then click Create.

Field	Description
Destination Name	Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Facebook Conversions".
Sync Frequency	Set the default frequency (for example, hourly or daily). You can override this setting for individual exports and syncs.
Select Ad Account	The Ad Account that should receive events
Facebook Pixel	Your Facebook Pixel ID. Use the same Pixel ID for browser and server events. This field is required
Advanced Measurement Table (optional)	Required later if you will sync to the Advanced Measurement API

GrowthLoop validates the connection. Facebook Conversions then appears in your list of connected destinations.

Export to Facebook Conversions

From within GrowthLoop, export from an audience built on the anonymous visitor datasets. See Export an audience if you need more information on these steps.

After building or selecting an audience, click Export, then search for your Facebook Conversions destination.

For the first export, use a test audience so you can verify the Audience Membership event in Meta.

Configure the export

Setting	Audience export
Export Name	Defaults to the audience name
Campaign type	Choose a one-time or ongoing export
Schedule	Set frequency, start date, end date, and days of the week for ongoing exports

Export behavior

Behavior	What happens
What GrowthLoop writes	An Audience Membership event to your Facebook pixel. Direction is GrowthLoop → Meta.
When it runs	GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. The event can take about 1 hour to appear in Events Manager.
Event	GrowthLoop names the event Audience Membership. You must verify and accept it in Meta before you can use it.
One-time exports	GrowthLoop sends current membership once.
Ongoing exports	GrowthLoop sends updated membership on each scheduled run.

This export does not send conversion events. To send conversion events, create a sync.

Create a sync in GrowthLoop

Create a sync from a warehouse table to write conversion events onto your Facebook pixel. See Syncs for information on how to complete those steps.

Select an Object Type:

Object	Use it for	Sync modes
Conversion	Conversion events in Facebook Ads Manager	Insert
AMAPI	Events on the Facebook Advanced Measurement API	Insert

When you configure the sync:

Connection: Select your Facebook Conversions destination.
Object Type: Select Conversion or AMAPI.
Update Rule: Choose Insert. Conversion and AMAPI both support Insert only. See Sync behavior.
Dataset/Table: Select the warehouse table that holds the events.
Match Field: For Conversion, map an identifier Facebook Conversion API accepts, such as email, phone, External ID, Click ID, Browser ID, Subscription ID, Facebook Login ID, Lead ID, Client IP Address, or Client User Agent.
Sync frequency: Choose 15 minutes, 30 minutes, hourly, or daily.

After you map fields, click Save Sync. Enable the sync with the toggle at the top of the page.

Conversion fields

Destination field	Required	Description
Event Name	Yes	A standard event such as `AddToCart`, `Purchase`, or `Search`, or a custom event. See Meta standard events
Event ID	Yes	A unique string for this event. Required for deduplication with browser or app events
Event Time	Yes	When the event occurred, in ISO 8601. Facebook converts this value to Unix
Action Source	Yes	Where the conversion took place: `email`, `website`, `app`, `phone_call`, `chat`, `physical_store`, `system_generated`, or `other`

You can also map additional Conversion API parameters. See Meta's Conversions API parameters.

AMAPI fields

Destination field	Required	Description
Event Time	Yes	When the event occurred. The API accepts events from the last 72 hours only
Identifier	Yes	One of email, phone, city, state, country, first name, or last name

Set Advanced Measurement Table on the destination before you sync AMAPI.

Sync behavior

Behavior	What happens
When it runs	GrowthLoop sends the sync as a batch on the next successful run.
Insert	GrowthLoop adds new events. Existing events are not updated.
Conversion match	Map an identifier the Conversion API accepts, such as email or phone.
AMAPI match	Map Event Time and one identifier. Events older than 72 hours are rejected.
Audience membership	Syncs do not create an Audience Membership event or a targeting audience.
Deletes	GrowthLoop does not delete previously uploaded events.

Rows without the required fields fail.

Confirm the export was successful

When the run finishes, confirm you can use the data in Facebook Conversions.

Audience export: Open Events Manager and look up the Audience Membership event. Verify and accept that event. After Meta accepts it, use Meta's audience creator to build an audience from Audience Membership.
Conversion sync: Open Events Manager and look up the conversion events.
AMAPI sync: Open Events Manager and look up the Advanced Measurement events.

In GrowthLoop, review counts on the audience Exports tab, or confirm the sync appears in the Syncs table. See Export an audience or Syncs for more information.

Congrats on successfully exporting to Facebook Conversions!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

Problem	Cause	Resolution
Connection fails to validate	Facebook Pixel is empty, or you signed in with the wrong account	Enter your Pixel ID and log in with the business account that owns the pixel and Ad Account
The Audience Membership event is missing	You are looking too soon, or you are not in Events Manager	Wait about 1 hour, then open Events Manager and look for Audience Membership
You cannot build a Meta audience	The Audience Membership event is not verified	Verify and accept Audience Membership in Events Manager
The audience has no anonymous visitors	MetaRouter is not sending events to the warehouse, or the datasets are not set up	Confirm MetaRouter is capturing activity, then build the audience on those datasets
A Conversion sync fails	A required event field is missing	Map Event Name, Event ID, Event Time, and Action Source
AMAPI rows fail	Event Time is older than 72 hours, no identifier is mapped, or Advanced Measurement Table is empty	Use an event from the last 72 hours, map an identifier, and set Advanced Measurement Table on the destination
A sync did not create a targeting audience	Syncs send conversion events only	Export an audience to send Audience Membership, then verify that event