server side
QUERY = 'contents'; CATEGORY = 'server-side' // 11 rows
sGTM or Data Manager: The Wrong Question and the Right Distinction
The two do not fill the same gap, and their scopes are not equal either. Data Manager writes only to Google products, sGTM writes anywhere. Which data travels which path, how the two feed each other, and the irreversible cost of getting the order wrong.
Connecting a Backend Record to a Tag Conversion: Where the Uploaded Value Lands
When an additional data source is connected to a Google Ads conversion action, the uploaded record permanently changes the value the tag wrote. Match thresholds, currency differences, double counting risk and the fourteen day non-biddable window.
Reading URLs for Tracking: Gateway Design, ITP and Pixel Sandbox
How URL parts (scheme, host, path, query, fragment) impact tracking. Server-side gateway design, first-party context, Safari LTP and Safari 26 AFP, Shopify Custom Pixel sandbox pitfalls.
Writing the Same Conversion to Four Different APIs: Data Manager's Destination Map
A single order record in your backend goes to Google Ads, GA4 and Floodlight today through three separate integrations. Data Manager collects them under one data model, but every destination has its own account type, identity surface and access gate.
Dedup in OpenAI Ads: Not Counting the Same Conversion Twice
When the pixel and the Conversions API send the same conversion, double-counting happens. OpenAI Ads deduplicates it with three components: Pixel ID, event name, and event_id, keeping the pixel event_id equal to the server id. This guide shows how to generate a stable event_id, match on both sides, and the common mistakes.
Sending Server-Side Conversions with the Conversions API: An OpenAI Ads Guide
The OpenAI Ads Conversions API sends conversion events server-to-server: a POST to the bzr.openai.com/v1/events endpoint with your Pixel ID and API key. This guide shows the request structure, the event fields and their required rules, the batch behavior, testing with validate_only, and dedup with the pixel.
OpenAI Ads Measurement Architecture: How the Pixel and Conversions API Work Together
OpenAI Ads conversion measurement rests on two layers: the browser JavaScript pixel and the server-side Conversions API. This post explains what each layer captures, why both are needed, and how they reconcile the same conversion without double-counting, conceptually, without diving into setup steps.
Meta Pixel Advanced Matching and EMQ: Hashing, fbc/fbp and CAPI Dedup in Practice
Meta Pixel Advanced Matching parameters, SHA-256 hashing rules, fbc/fbp cookie lifecycle, CAPI event_id deduplication and EMQ score. A platform-agnostic technical reference for setting up Pixel and CAPI correctly.
Personal Data Inventory Under Consent Mode: GA4, CAPI, Newsletter and Webhook Leakage Surfaces
Personal data travels in multiple forms across a measurement stack: raw email, hashed PII, pseudonymized IDs, IP. A practical mapping of each data type to Consent Mode v2 signals, with leak-prevention notes.
GTM vs sGTM vs Zaraz vs Gateway: I Tested All Four with Real E-commerce Data
Client-side tracking alone leaves your data 30-40% incomplete. I compared GTM, sGTM, Cloudflare Zaraz, and Google Tag Gateway on a live e-commerce site. Safari 26 impact, Consent Mode v2, and a situational decision guide.