If you or your team are advertising on Meta (Facebook and Instagram), integrating Everflow with Meta is crucial for gaining reliable attribution data that Meta alone cannot provide. Everflow's advanced reporting allows us to send conversion information back to Meta, empowering you to make smarter, data-driven decisions to optimize your campaigns and improve your results.
Everflow achieves this by using Meta's Conversions API to fire Meta pixels. By configuring your postback settings in Everflow as outlined in this guide, you'll be able to seamlessly push valuable conversion data directly into Meta. This integration is key to enhancing your campaign performance insights within the Meta advertising platform.
If you're using the latest Meta SDK, the process for generating an Access Token and completing the Conversions API integration has been simplified. This guide will walk you through the most up-to-date method.
Generate an Access Token
To use the Meta Conversions API, you will need an access token. Inside Events Manager, follow these steps:
Choose the Pixel you want to implement.
Select the Settings tab.
Find the Conversions API section and click on the Generate access token link under Set up direct integration, and follow the instructions pop-up:
To use the Meta Conversions API, you will need an access token. Inside Events Manager, follow these steps:
Choose the Pixel you want to implement.
Select the Settings tab.
Find the Conversions API section and click on the Generate access token link under Set up manually, and follow the instructions pop-up:
Note: The Generate access token link is only visible to users with developer privileges for the business. The link is hidden from other users.
**IMPORTANT** Once the token is generated, be sure to keep a copy of it as you will not be able to see it again, and will need to enter it in the next step.
Add Meta App to your Everflow Partner Login
Login to your Everflow Partner account.
Navigate to Company Settings - Integrations, then click Add Integration on the card.
Fill in the fields with the information collected in Step #1 and Step #2. Business Name can be any name you choose. Save.
Set Up Meta Pixel in Everflow:
In Everflow, when setting up a postback:
Under "Delivery Method," select "Meta."
Under "Postback Level," choose "Specific" and select the relevant offer.
Under "Meta Business," select the Business App created in Step #2.
Under "Meta Pixel," select the Pixel ID. - this is the Dataset ID on the settings page in Meta events manager
Under "Meta Event Name," select the appropriate event that matches the pixel's action.
Select the "Action Source" according to Meta's documentation.
(Optional, for Purchase events) Add Meta Custom Data:
Add "Currency" with the value {offer_currency}.
Add "Value" with the value {payout_amount}.
Under Meta User Data, add "Fbc" with the recommended value: fb.1.{timestamp}.{fbclid}
Network Actions (Partner needs to request this from their Partner Manager):
They should edit the row of the pixel and add the "Event Source URL" (the browser URL where the event happened).
Important Considerations for Facebook Pixels:
fbclid: For optimal tracking, ensure you pass the fbclid.
If using Direct Linking, the Everflow click script automatically tracks it.
If not using Direct Linking, append &fbclid={fbclid} to your affiliate tracking link.
The article mentions that using the latest version of the Meta SDK means you no longer need to create an app in the Meta Developer Settings to generate an Access Token.
Verification: This pixel is server to server only so you will not be able to use the Facebook Pixel Helper Chrome extension to verify that your pixel is firing correctly on the advertiser's landing page after a conversion. You will need to test the events within your Facebook account.
Troubleshooting
If you're not receiving the postback, check on the following:
Ensure the fbclid populates properly in the partner postback. You can do this by looking at the click redirect URL.
Ensure the event_source_url is entered correctly.
Ensure the postback is configured to include all required details. For example, a purchase may require data points like city, state or country code.
To see debug info, you can run a Partner Postback Report. Navigate to Reporting - Partner Postback, and run the report. Then, click the vertical dots on the end of any row to select View Debug Info.