Use these best practices as general recommendations to successfully integrate the Conversions API. These recommendations are designed to help you make the most effective use of the Conversions API. Follow the implementation and post-implementation recommendations to ensure a smooth integration and optimal results when sharing data with Meta.
In addition to the following best practices, we recommend that you watch this video for a more hands-on tutorial on using the Conversions API. The video guides you through how to:
When setting up your campaign, simplify the account structure and use the following established campaign best practices:
We recommend that you use the Conversions API in addition to the Meta Pixel, and that you share the same events using both tools. We call this a redundant event setup. For example, if you share
Initiate Checkout, and
Contact events using the Meta Pixel, you should also share those same events from your server using the Conversions API.
The Conversions API allows you to share website events that the Pixel may lose due to network connectivity issues or page loading errors. The Conversions API can also be used to share other types of important events and data that occur offline or at a later time that the Pixel cannot.
When sending redundant events using the Meta Pixel and Conversions API, ensure that both events use the identical
event_name and that either
event_id or a combination of
fbp are included. We recommend including all of these parameters to help Meta properly deduplicate events and reduce double reporting of identical events. Learn more about deduplication, when it’s necessary and how to set it up.
All website events
All website events
By using the Conversions API, you agree that the
action_source parameter is accurate to the best of your knowledge. We also recommend including the
event_id event parameters for all events.
Sending additional customer information parameters may help increase Event Match Quality. Only matched events can be used for ads attribution and ad delivery optimization, and the higher the matching quality, the better. While unmatched events cannot be used for attribution or ad delivery optimization, they can still be used for basic measurement. Examples of high-quality customer information parameters include:
Following the release of Graph API version 13.0, we will be updating the baseline requirements for which combinations of customer information parameters are considered valid with a Conversions API event. These changes will help us provide better feedback for when an event has a combination of customer information parameters that is so broad that it is unlikely to be effective for matching.
An event is considered invalid if it only includes customer information parameters that consist of one of the following combinations, (or a subset thereof).
For example, if an event had only the customer information parameters
country (this could correspond to a man, in Menlo Park, California, USA), it would be rejected because those customer information parameters are a subset of one of the above combinations.
fbc Parameters Are Refreshed
fbc parameters are cookie values typically set on your site visitors’ browsers in connection with Meta’s first-party cookie solution, and are subject to change. If you send them as user parameters, you should regularly refresh their values.
These values will be set as first-party cookies when the Meta Pixel is implemented on your website and can be retrieved for use in Conversions API requests.
Sharing events when they happen can help your campaigns achieve the best results. You can share server events using the Conversions API in real time or in batches close to real time.
We recommend using the Test Events tool to validate your Conversions API connection. Typically, developers should use their own customer information parameters (for example, name, email address, phone number) for test events, because these events may get discarded if they don't match a Facebook or Meta account.
You can use the Test Events tool to:
Fill out the required and recommended data parameter fields in the Payload Helper tool to see how your payload should be structured and to get recommendations for which parameters to include.
The code samples in our documentation include Business SDK examples in Python, Java, Ruby, PHP, and Node. They can save some development effort, such as hashing user parameters, which is done automatically in the Business SDK.
If you are not planning to use the Business SDK, we recommend that you implement hashing.
The Conversions API supports all offline events and should be used as the comprehensive container for these types of events. Examples include physical store sales, phone calls, actions taken on devices (such as smart TVs or game consoles), and offline subscriptions.
When sending offline events, be sure to include the
action_source event parameter, and choose the appropriate value (should not be
website). The action source is required to determine the campaign objectives for which the event is intended.
By using the Conversions API, you agree that the
action_source parameter is accurate to the best of your knowledge.
Partners or agencies that share events on behalf of their advertisers should send a unique
partner_agent string, including platform name as documented. If applicable, work with your dedicated Meta representative to decide on a suitable agent string.
By default, website platform partners may consider whether to offer Conversions API selectively or to opt-in advertisers. The Meta Pixel and Conversions API share the same business terms, and we recommend that you opt-in your customers to also share their data using the Conversions API when they set up the Meta Pixel. While we believe using both tools will strengthen and secure their data-sharing for the long term, we also suggest that you provide your customers with information about both the Conversions API and Meta Pixel to help inform their choice.
If you share server events using the Conversions API, you can see the Event Match Quality (EMQ) for each event in Events Manager. An event’s EMQ score (out of 10) indicates how effective your server event’s customer information may be at matching it to a Facebook or Meta account. Learn more about EMQ best practices here.
Event Match Quality is currently available only for web events. For other event types such as offline and physical store events, app events, conversion leads or any integration under alpha or beta stages, contact your Meta representative for guidance on improving event match quality.
When using the Conversions API, we recommend that you test and optimize your Meta advertising strategy. Some testing options include: