Paid Media Decoded

Module 08 Tracking & conversions

Server-side: CAPI & equivalents

Send the same event twice, once from the browser and once from your server, and count it once.

7 minBeginner4 steps

The browser copy can go missing

The tag runs in the browser. An ad blocker, a page error or a slow connection can stop it. A copy sent from your server does not depend on the browser. Send the event twice so one copy can survive.

The tag sends one copy

The tag sends the event as soon as the page tells it to. This is the copy most platforms build their browser tracking around. The browser copy is fast and easy to lose.

Your server sends the second copy

Your server already knows about the order. It sends the same event to the platform from a machine, not from a browser. The server copy does not depend on the visitor’s browser.

One ID keeps it to one conversion

Both copies carry the same event ID. The platform sees two copies of one event and counts one. Google’s route works differently: it matches hashed customer data instead. Without a shared ID, two copies can become two conversions.

Platform
Interactive diagram
Sequence diagram · Default state
PathMessage
Browser → WebsiteThe shopper pays on the website.
Website → TagThe browser copy of the purchase goes to the tag.
Tag → PlatformThe tag sends Purchase with event ID A104.
Website → ServerThe same purchase is written into the order system.
Server → PlatformYour server sends Purchase with the same event ID A104.
Platform → PlatformThe platform finds the same event ID twice and keeps one copy.

Analytics settings

Allow Google Analytics? It helps us see which lessons people use. You can change this in Analytics settings.

Search the course

Type to find lessons, terms and sources.