The browser pixel sees what the visitor’s browser lets it see, which is less every year. The Conversions API is Meta’s server-side route for the same data. Meta’s documentation describes it as a way to connect marketing data from a server, website platform, app or CRM to Meta’s systems, with server events linked to a dataset ID and processed much like events from the Pixel, so they can be used for measurement, reporting and ad delivery. Meta calls the Pixel and the API complementary and offers a one-click setup for website events from Events Manager (Meta).
For commission deals, the API matters when the brand pays creators on Meta-attributed sales. Missing events mean undercounted sales, which means underpaid creators.
Example. A brand runs creator videos as partnership ads and pays a 10 % share of Meta-attributed sales. In a month, the browser pixel alone records 180 purchases. With the Conversions API also sending orders from the store’s server and deduplicating against the pixel, Meta records 215. The creators’ commission base is 19 % larger for the same ads. Example numbers, not a benchmark.
When brands use it. The pain this answers: “I have no idea which creator actually drove sales.” Brands set it up to recover events that ad blockers, privacy settings and in-app browsers drop, and to send events the browser never sees, such as a refund or an offline order. Most store platforms offer it as a setting rather than a project.
The creator’s view. A creator paid on platform-attributed sales depends on the brand’s tracking being complete. “Do you have the Conversions API on” is a fair question before accepting a share of Meta-attributed sales, and the brand’s answer says how seriously it measures.