Overview
Everflow can fire a Meta pixel using Meta's Conversions API. This guide is to help you configure your postback setup in Everflow to receive Meta pixels using the Partner Portal. This integration is used to push conversion data into Meta from Everflow in order to optimize performance data in Meta.
If you are using the latest version of the Meta SDK, you no longer need to create an app in the Meta Developer Settings in order to generate an Access Token. The article below outlines the latest method to get your Access Token and complete the CAPI Integration. If you are still using the older version, please follow the steps in the video to create an app first.
Note: Our integration with Meta refers to the formerly known integration as Facebook.
A Step-By-Step Guide
Step #1: 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 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 Step #2.
Step #2: Add Meta App to your Everflow Partner Login
Login to your Everflow Partner account.
Navigate to Company Settings - Integrations, then click Add Business 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.
**Please note: the integration is also accessible in the Network account via Control Center - Integrations > Media Buying - Meta, where the integration can be viewed and deleted by a network user.
|
Step #3: Setup Meta Pixel in Everflow
Navigate to Postbacks and decide whether you want to edit an existing postback or add a new one.
Under Delivery Method, select Meta (Meta).
Under Postback Level, select Specific and choose the matching offer.
Under Meta Business, select the Business App created in Step #1.
Under Meta Pixel, select the ID. To find the ID or create a new one - [Click Here]
Under Meta Event Name, select the Event that matches the action of the Pixel. For more details about Events - [Click Here]
Select Action Source. Please reference the documentation linked below to determine the value to enter here.
The action_source, as described by Meta: “This field allows you to specify where your conversions occurred. Knowing where your events took place helps ensure your ads go to the right people."
Note: The Event Source URL will be updated on the network side in Step 4.
(**Optional if the Meta Event is a Purchase) Enter Meta Custom Data.
Click the + Add button and input Currency {offer_currency}.
Click the + Add button again and input Value {payout_amount}.
Scroll down to Meta User Data, and click the + Add button.
Under Data Field, select Fbc. We recommend that you enter the following as the Value: fb.1.{timestamp}.{fbclid}
After completing the setup in your Partner Portal, the Network needs to perform the following actions in their Network Portal:
Navigate to Partners - Postback.
Click Edit on the row of the pixel.
Add the Event Source URL.
The event_source_url, as described by Meta: "The browser URL where the event happened."
Important Notes
For optimal tracking, be sure to pass the fbclid.
If the tracking method is Direct Linking, then the EF.click script automatically tracks the fbclid when it is in the URL.
If you are not using Direct Linking, then the Partner can append the following to their affiliate tracking link:
&fbclid={fbclid}
If you would like to pass values to Meta that you receive from the Advertiser Postback in adv1-5 parameters, be sure to enable the following setting in Control Center - Configuration > Global Settings.
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.
For more info about Meta error codes - [Click Here]
FAQ
Q: Will Everflow be able to pull the correct amount of conversions even if Meta's reporting is off?
A: Yes. Everflow receives conversions either from the first-party cookie or from a server call directly to our platform, with extremely high accuracy. Additionally, there are tools in place that record conversions even if the user deletes their cookies. Transparent reporting will tell you exactly how the conversion was attributed.