Guides
Help center for Most conversion automation and pixel activation.
Implement first-party data consent in server-side delivery
A server queue does not automatically know a visitor's current choices. Keep the decision record, event and destination policy connected so each send can be explained.
Preserve event time through queues and time zones
A timestamp can be validly formatted and still describe the wrong moment. Compare source, queue and payload values before blaming a reporting window.
TikTok Events API migration: Unified Endpoint Guide
TikTok Events API migration uses the unified /event/track/ endpoint for web, app, offline, and CRM sources. Check the source-specific schema and distinguish successful receipt from matching and attribution.
Safari ITP Cookie Restrictions: Keeping Attribution With Server-Side Tracking
Safari caps browser cookies to 7 days - or 1 day after a tracked click. Here is what that kills, what survives, and how a first-party server setup keeps attribution.
Postback vs Conversions API: Two Server Channels With Different Jobs
A postback tells your tracker about a conversion; the Conversions API tells the ad platform. They are not rivals - most profitable funnels run both.
Shopify GTM vs the Google & YouTube App: Who Controls Your Tracking
The built-in Google & YouTube app sets up conversion tracking fast but hides every knob that matters. Here is what GTM and sGTM give you back, and how to migrate without duplicate purchases.
TikTok Events API Gateway: Multi-Account Server-Side Delivery Explained
TikTok's Events API Gateway serves many ad accounts from one host, deduplicates pixel and server events, and onboards new accounts in minutes.
TikTok Events API Server-Side GTM: Setup Guide
Step-by-step TikTok Events API server-side GTM integration through your own Google Tag Manager server container, covering tokens, tags, deduplication, and testing.
Meta CAPI Batching and Rate Limits: The Delivery Rules
The Conversions API accepts several events in one request - and one bad event can fail the whole batch. This guide covers the documented batching structure, the acceptance rules that decide whether a request survives, what a rejected batch means for retry logic, and the delivery discipline that keeps a busy funnel inside the platform's limits without guessing at undocumented numbers.
Snapchat Conversions API GTM: Server-Side Delivery Through sGTM
Server-side GTM has no native Snap tag - a custom template on sendHttpRequest posts the Snap payload, where the match key gate and client_dedup_id decide whether delivery works at all.
Reddit Conversions API Setup: Pixel ID, Token, and Deduplication
Reddit's Conversions API accepts server events within seven days of the conversion. Here is the documented setup path: token, payload, match keys, and deduplication.
Meta CAPI Gateway Self-Hosted Setup: AWS Deployment Walkthrough
The Meta CAPI Gateway runs in your cloud account - provisioned from Events Manager, deployed via AWS, and priced from the cloud resources it uses.
Snapchat Conversions API Setup: Token, Match Keys, and Signal Quality
Snap rejects conversion events without a match key. Here is the documented Snapchat CAPI setup: token, required fields, hashing, dedup, and test events.
Server-Side GTM Migration: Steps, Hosting, and Honest Wins
Move your tags from the browser to a server container you control - with a checklist for migration, hosting choices, deduplication, and realistic expectations.
Pinterest Conversions API Setup: Token, Deduplication, and Event Quality
Pinterest's Conversions API takes web, app, and offline conversions server-side - no app ID required, just a business account and a token from Ads Manager.
Pinterest Conversions API GTM: Server-Side Delivery Through sGTM
Server-side GTM has no native Pinterest tag - but its custom template API posts the Pinterest Conversions API v5 payload from your own server, with event_id dedup and the under-one-hour delivery window Pinterest asks for.
Meta CAPI Gateway vs Direct Integration: Which Delivery Fits Your Stack
The Meta CAPI Gateway runs in your own cloud account, while direct integration posts events from your server. Here is how to choose without overbuilding.
Cross-Platform Conversion Parameters Matrix: One Event, Six Networks
Routing one conversion to Meta, TikTok, Reddit, Snap, Pinterest, and Google? This matrix maps which deduplication and click parameter each network expects.
ChatGPT Ads Server-Side GTM: Sending Conversions API Events From a Server Container
Server-side GTM can deliver ChatGPT Ads conversions through a custom template built on Google's sendHttpRequest API - here is the endpoint, payload, and validation.
Server-Side Tracking for Performance Marketing: How the Stack Works in 2026
A conceptual entry point to server-side tracking for performance marketers. See how the pipeline is built, when browser pixels stop being enough, which stacks exist, and where to go next for Meta CAPI, TikTok Events API, and sGTM migration details.
Google Consent Mode gcs/gcd Parameters: Full Decoding Guide
Google tags report consent state on every hit through two query parameters: gcs and gcd. Google documents what they are for but not how gcd is encoded, so the decoding matrix comes from reverse engineering. This guide assembles the official G1-- table, the 12-character gcd layout, and all nine consent letters.
Server-Side Tracking vs Browser Pixel: What Media Buyers Need in 2026
Compare browser pixels and server-side conversion tracking, then choose pixel-only, server-only, or hybrid for your funnel.
Reddit Conversions API GTM: Server-Side Delivery Through sGTM
Server-side GTM has no native Reddit tag - but its custom template API has everything needed to POST the Reddit Conversions API v3 payload from your own server, with click_id and conversion_id mapped from the event model.