FB Conversion

1. Go to Meta Events Manager → choose the relevant business account.

2. On the left-menu, click “Connect Data” (or “Add Data Source”, depending on interface).

3. Select “Web” as the data source type (since you’re sending web events).

4. Choose or create a dataset (i.e. choose the Pixel / data source name) that represents the web tracking source.

1. After selecting the web data source, Facebook will prompt you to choose a setup method. Choose “Setup Manually” (instead of partner integrations).

2. Next, select both Conversions API and Meta Pixel (i.e. you want both client-side and server-side tracking).

3. Click “Start CAPI Setup”. Once it loads behind the pop up, click Finish.

1. In the CAPI setup flow, you will be asked to choose which customer parameters to send.

2. Among the available identifiers on the third step, select “Click ID (fbc)” under Customer Information Parameters.

This is to capture the fbc parameter (Facebook click identifier) which helps with matching server‑side events to the ad click.

3. You may also choose other identifiers (e.g. email, phone, etc.), but ensure fbc is included for better attribution.

1. In the CAPI setup flow, when prompted to authorize, you’ll see an option to generate an access token.

This is usually under a section like “Authorize via token / Generate token” or “Generate access token for Conversions API.”

2. Click Generate Access Token.

3. Copy the generated token (you’ll use this in AEvent).

4. (Optionally) Make sure you store the token securely (it behaves like a secret key).

5. Aside from the access token, you also have to copy your Pixel ID:

Go to your Integrations and search for the FB Conversion Integration, click Add Integration:

In the pop-up window, name it and click Connect.

Next, use your access token and pixel ID:

You'll see it connected afterwards:

Go to the campaign that you want to use your integration in.

Go to Integrations, find your FB Conversion Integration, and toggle the switch. Click the cog icon in case the integration setting doesn't open automatically:

Next, you have to click 'Send on Registration' and select the event you want to trigger upon registration:

You may also add custom events if needed. Click update settings once you're done.

With that setup, AEvent will send that event to FB upon registration.

And you'll be able to see the events sent on your Events Manager.

In the example below, we'll create an action that will retarget non buyers.

Non buyers are people who visited your cart page, but didn't get to your thank you page. To create this audience, visit this article.

Once I've prepared my audience, I'm now able to target them on my action.

In the example, I'm going to add a 'custom event' that I'll call 'retarget'.

This will allow me to retarget my non buyers using FB Ads, in an attempt to get them back on my site and close the sale.

Targeting the custom audience 4 hours after the event (started):

The action, and the button to click to add a custom event...

After setting up the action, click 'Create':

After creating the action, you'll now see it in your timeline:

If you want to remove your Custom Domain from AEvent, you need to navigate to Integrations, locate your Custom Domain integration, and click on the trashcan icon.

You will then be prompted to confirm deletion.

(NOTE: Removing this integration will immediately affect its use with any campaigns that it is active in, as well as any and all previous and present links that have been sent.)

If you are experiencing issues with this integration but do not desire to REMOVE it, we recommend reconnecting it instead. This will allow its configuration to continue as set within your campaigns.

Once you confirm removal, the integration within AEvent no longer exists.