You will be able to explain why platforms ask for server-side events and what they do.
Farah checked her numbers one Monday and found a gap she could not explain. Her online shop recorded 40 orders from the past week. Meta's Events Manager, fed by her pixel, showed 31 purchases. The figures are examples, but a gap like that is normal. Nine orders had happened, and the platform never heard about them.
Nothing was broken in the usual sense. The pixel was installed and working. It simply could not see every visitor. This lesson explains why, and what the platforms now ask you to add so they can see more of what happens.
A pixel runs in the visitor's web browser. When someone completes a purchase, code on the page sends a message from their browser to the ad platform. That works only if the browser lets the message through.
Increasingly, it does not. Some browsers limit tracking by default. Ad blockers and privacy extensions stop many tracking messages entirely. On iPhones, apps must ask permission before tracking people across other companies' apps and websites, and many people say no, which limits what an app like Instagram can link up. Cookie banners that a visitor declines can stop tags from firing. A visitor who clicks an ad on their phone and buys later on a laptop is hard to connect from the browser alone.
Each of these removes a few events. Together they can leave a platform seeing noticeably fewer conversions than really happened. That matters for your reports, but it matters more for the auction. As lesson 3.1, What a pixel does and why the auction needs it, explained, the platform learns from conversions it can see. Fewer visible conversions means less to learn from.
The answer the platforms offer is to send events a second way, from your own systems instead of the visitor's browser. These are called server-side events.
When an order is completed, your website or shop platform already knows about it, because it has to record the order. A server-side connection sends that same event directly from your website's server, or from the platform that hosts your shop, to the ad platform. Browser settings and ad blockers do not stand in the way, because the visitor's browser is not involved in that message.
Meta calls its version the Conversions API. TikTok calls its version the Events API. Both accept events such as purchases and leads from your server, along with details that help match the event to a person on their platform.
Google approaches it a little differently. It offers a way to improve conversion measurement by sending hashed first-party customer details, such as the email address or phone number a customer typed into your checkout or form, along with the conversion. Look up the current name of this feature in Google Ads help, because Google renames products often. The details are hashed before they are sent, meaning they are turned into a scrambled code using a standard method, so the platform can match them against its own signed-in users without receiving the plain email address.
Meta and TikTok use hashed customer details in the same way when you send server events. Better matching means more of your conversions get credited to the right ad.
Most advertisers end up sending each important event both ways: from the browser through the pixel and from the server through the API. That gives the best coverage, because each route catches events the other misses. It also creates a risk. If both messages arrive and the platform treats them as separate, one sale becomes two.
The fix is deduplication. You give the browser event and the server event the same identifier, often called an event ID, along with the same event name. When the platform receives two events with matching details, it keeps one. Meta and TikTok both describe how to set this up in their help pages, and most built-in integrations handle it for you.
If you build a custom connection, test deduplication carefully. Double-counted conversions make a campaign look twice as good as it is and teach the platform from false data.
You do not need to write server code to get most of this. Many shop builders and website platforms offer ready-made connections to Meta's Conversions API, TikTok's Events API and Google's first-party matching, usually as an app, plugin or setting. Shopify and WordPress, for example, both have ways to connect these, through apps or plugins whose names and features change over time.
For Farah, this meant turning on a data sharing setting in the Meta app her shop platform offered, then checking in Events Manager that purchases were arriving from both the browser and the server, with deduplication working. Her gap did not close completely, and it never will. It narrowed enough that the platform had more to learn from.
Priya's site runs on WordPress with a simple booking form. Her route was a plugin that connects the form to Meta's Conversions API, plus the Google option for sending hashed form details with each booking.
Server-side connections send customer details, so they come with privacy duties. Lesson 3.3, Consent, privacy and the PDPA, covers those next. First, find out what your own platform already offers. In the activity below you will check your website platform's integrations for these server-side options.
Check whether your website platform, such as Shopify or WordPress, offers a built-in integration for Meta's Conversions API or Google's first-party matching.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).