The Facebook Conversions API has been a popular topic for the past year or so. While most marketers understand that they need it, most misunderstand the reason why.
Let’s clear up the following:
- What the Facebook Conversions API is
- Why it’s important
- Whether it’s helpful for iOS 14 data loss
- How to get it set up
What is the Facebook Conversions API?
Look, as much as I’d like to be, I’m not a super nerdy, techy, programmer guy. I’m going to explain this in only the most basic terms — mainly because I understand it in the most basic terms.
The Conversions API creates a direct connection between your data and Facebook. This helps provide a conversions source in addition to the pixel and offline methods.
Why the API is Important
The Facebook pixel was one of the most impactful developments of the past decade for advertisers. It’s certainly been huge for my advertising.
The problem is that the pixel is getting less and less reliable. Its ability to send event data to Facebook is interrupted by cookie blockers, loading errors, and connection problems.
It doesn’t mean that you should use the Conversions API instead of the Facebook pixel. If you use them both, you’re more likely to send Facebook a complete set of data. If Facebook doesn’t have the complete picture, it will negatively impact the platform’s impression of performance.
Consider this: If Facebook doesn’t have all of the event data, it may make it more difficult for your ad set to exit the learning phase. It may lead Facebook to incorrectly favor one ad set over another or one ad over another. Accurate attribution is important.
Adding the API leads to improved reporting, more complete custom audiences, and better optimization. And given the trend of ad blocking and browser privacy changes, we can expect the pixel to get less useful in the future — making the API even more important.
The API, iOS 14 and Data Loss
The Facebook Conversions API started getting more popular once changes related to iOS 14 were first announced. And Facebook confused matters more by recommending the API during this time.
The problem is, though, that the Facebook Conversions API has to follow the same rules for web events that the pixel does for sending data. If someone opts out of tracking, the API will be impacted in the same ways the pixel is.
Again, though, that doesn’t mean the API isn’t important. If you’re getting fewer conversions reported due to iOS 14, that just makes it more important that Facebook gets as many of the events that it can to report on what it can.
It won’t solve problems related to iOS 14, but the Facebook Conversions API will help improve your reporting that is unaffected by iOS 14.
How to Set it Up
Of course, there isn’t a single method for setting up the Facebook Conversions API. And in most cases, it’s not a simple task (there are exceptions!). It depends largely upon how you’re managing your pixel right now.
Within the Events Manager for your pixel, scroll down to Conversions API.
Click to choose a partner. There are several potential integration partners that you can pick from.
Depending on the partner, the instructions for setting up the API will be different. In some cases, it may be just a matter of a few clicks (the rumor is that Shopify and WooCommerce are very easy). In others, it may require some technical assistance.
I used the Conversions API Gateway to set it up. I wouldn’t say it was easy, but it was finally a solution that allowed me to get the process completed. For the longest time, I ran into hurdles.
Other Uses of the API
Beyond sending web events, you can also send offline events or integrate your CRM. The CRM integration, at least for now, is being used by Facebook for Conversion Lead optimization when running Facebook lead ads. I’ll cover that in more detail later.
Do you have the Conversions API set up? What method did you use? Are you seeing an improvement in performance as a result?
Let me know in the comments below!