Configuration

Now that the basic onboarding is complete, let's review all fields in the form and how to use them. The Dataset ID and Ads Account ID were already filled in during the basic onboarding, so we will skip those two.

Enable browser pixel?

The browser pixel is one of the key concepts that Meta is prioritizing. By enabling this option, we will begin sending browser events alongside the server events that you receive automatically. We ensure that both the browser and server events share the same event ID, allowing Facebook to deduplicate events and maximize the benefits from both sources. If you are using our browser integration or any of our apps, enabling this feature will work seamlessly. For headless applications, you will need to add our NPM package to your project to allow support—more on NPM packages.

Product ID mapping

When syncing your product catalog with Facebook, you may be using a different format than what you have in your e-commerce platform. This can result in the content ID expected by Facebook being different from what you're sending from your website. As a result, your catalog match rate will be low. This setting allows you to specify which property from the event you would like to send to Facebook as your product ID.

How can you determine which ID you are using? 1. Go to your Commerce Manager on Facebook. 2. Click on your catalog. 3. Expand a product to find the Content ID. 4. Compare this ID with the value in your e-commerce platform and find which type it is 5. Ensure that the type matches the setting configured in EdgeTag.

Limited Data Use (LDU)

Enabling this option will cause the LDU flag to be sent to Facebook, which may impact your campaign and retargeting performance. You can read more about it in their documentation.

Event test code

To verify that events are being received correctly by the Facebook server, follow these steps: 1. Open the Events Manager and select your Dataset ID. 2. Go to the "Test Events" tab. 3. Click on "Confirm your server’s events are set up correctly." 4. A test code will appear; click the "Copy" button to copy this code. 5. Paste the test code into our form. 6. After saving, trigger some events, and you should be able to see them on the Events Manager Test page.

Remove test code before going to production, as it prevents event recording in the events manager.

Backup Access Token

Your life can be pretty dynamic when you are traveling or testing your system in different browsers and countries using a VPN. Unfortunately, a side effect of this can be that Meta will invalidate your connections as a security measure. This means you may need to log back into Meta or solve a captcha. Additionally, this will result in the revocation of your connection with EdgeTag. You can solve this with Backup Access Token.

To generate a Backup Access Token, navigate to your Events Manager and select the desired Dataset ID. Then, open the Settings tab. Scroll down to the Conversions API section, click the "Generate access token" button, and copy the token. Ensure that you keep this token secure, as it is required to authenticate events sent to Meta.

Parameter Builder Library

Meta has introduced a new option that allows you to fix your Facebook click ID and browser ID using the Parameter Builder Library. You can find more information about this library in their documentation. If you enable this option, we will load the library onto your site.