ads-server-side-tracking

Systematically review server-side tracking implementations including tag management, platform conversion APIs, event deduplication, consent handling, and data quality. Use this when debugging conversion data loss, validating sGTM/CAPI setups, or ensuring privacy compliance in first-party measurement.

• Map collection, consent, transport, transformation, destination, and observability components
• Compare browser and server event taxonomy, parameters, IDs, timestamps, values, and user data
• Verify deduplication, replay handling, retries, latency, and test events safely
• Inspect hashing and data minimization before transmission to destinations
• Reconcile destination diagnostics with source logs and business conversions
• Return schema-valid findings with failure modes, ownership, priority, and verification steps

1. 1.Map your tracking architecture: identify collection points, consent mechanisms, transport layers, transformations, and destinations
2. 2.Export or log events from both browser and server implementations
3. 3.Compare event taxonomy: verify parameter names, IDs, timestamps, values, currency, and user data match
4. 4.Check deduplication logic: review event_id handling, replay prevention, and retry behavior
5. 5.Inspect hashing and minimization: confirm sensitive data is hashed or excluded before transmission
6. 6.Reconcile diagnostics: cross-reference destination reports with source logs and actual business conversions
7. 7.Document findings with schema, failure modes, owner, priority, and reproduction steps