Designing Reliable Conversion Postback Tracking

Generate or receive a stable click ID before the routing and tracker handoffs that need it, then preserve the value to the conversion system. Do not use mutable display names or a timestamp alone as the join key.

Specify endpoint, method, authentication, required fields, event names, value and currency formats, timestamp semantics, encoding, and accepted responses. Version incompatible changes so senders and receivers do not silently disagree.

Use server-side credentials or signatures, validate identifiers and numeric fields, require protected transport, and avoid exposing secrets in browser code. Send only data required for attribution and the approved reporting purpose.

Assign a unique conversion or event key and treat duplicates idempotently. Bound retry schedules, distinguish temporary failures from permanent validation errors, and retain correlation logs without recording sensitive credentials.

Sample click IDs from route event to tracker record, destination action, postback receipt, and downstream report. Investigate the first missing or changed field and keep routing decisions separate from later conversion-value interpretation.