Server-sideMeta CAPIGA4
Use case 02
Server-side tracking with data enrichment
The server adds margin, customer type, and order value to the event, then sends one clean hit to each platform.
The situation
The browser only knew the click, the page, and the form. Margin, customer type, and the real order value lived in the shop and the CRM, so the platforms were bidding and reporting on a thinner event than the business had.
What we implement
A server container receives the event, adds the fields the page should not expose, and forwards one event to GA4, Google Ads, and Meta. The browser pixel and the server event share an event ID, so each platform counts the order once.
The result
The bid and the report can use value the browser never held. A purchase is one conversion in each platform, with the order value and the customer context attached.