Postback Tracking: Connect Affiliate Clicks to Conversions

Map the journey and both systems' requirements

Write down the tracker, the offer system, the outbound destination field, and the conversion receiver. Use their current integration instructions to identify supported macros, required fields, authentication, and accepted event types. A generic URL from another network may use names or conventions your integration does not understand.

Keep campaign dimensions separate from the individual click reference. A Sub-ID may describe a publisher, creative, or placement, while a click ID identifies the interaction being matched. Some integrations use Sub-ID fields to transport click references; document the chosen mapping instead of assuming the field name tells you its role.

Preserve the reference and define the outcome

Follow a controlled click through the offer journey and verify that the agreed reference reaches the system that later reports conversions. Check the actual resolved value rather than a URL template containing a literal macro. If a redirect or checkout handoff drops it, a correctly delivered postback may still be impossible to attribute.

Define whether the notification represents a submitted lead, approved lead, sale, or paid commission. For payout, confirm currency and whether the value is commission or total order revenue. An illustrative $20 affiliate commission on a $100 purchase must not be reported as $100 in earnings simply because the order system knows that larger amount.

• Document the outbound and return field mapping
• State the event status that qualifies
• Confirm amount units, currency, and revenue meaning

Test successful, unmatched, and repeated deliveries

Use the integration's supported test facilities to send one valid event for a controlled click. Inspect both delivery logs and the receiving record. A successful HTTP response confirms a request was handled; it does not by itself prove the event matched the intended campaign or used the correct payout.

Test a missing reference, an unknown reference, and a repeated delivery of the same outcome. Establish how each case is rejected, queued, or recorded. Retain enough evidence to reconcile the result without exposing endpoint credentials. Avoid sending fabricated production sales solely to make a dashboard show activity.

Reconcile approvals and diagnose the failing stage

Compare matched events with the affiliate system's approved outcomes over the same period. Pending approvals, reversals, and delivery delays can change the meaning of apparent discrepancies. Keep the status definitions alongside the report so an approved commission is not compared with a raw lead submission count.

If a sale is absent, work through reference capture, reference preservation, notification delivery, and receiver matching in that order. Use Tracly's campaign links and Sub-ID reporting to organize the campaign context; verify supported conversion integration options before connecting a specific network. This workflow is general integration guidance, not a promise of automatic compatibility with every affiliate platform.

Frequently asked questions

Related articles