Tracking test (S2S integration test)

Runs a real click and a real conversion through the platform so you can see each step work: the click is recorded and redirected, the postback creates a conversion, and the publisher's postback fires.

What you can do here

• 1 · Fire a click — Pick a campaign and publisher, set the country and optional sub parameters, and fire. You get the click ID, detected device and the redirect URL with macros replaced.
• 2 · Send conversion postback — Uses the click ID from step 1. Set status, payout, revenue, currency, transaction ID, goal and the advertiser token or campaign secret.
• Results — Postback response, publisher callback URL, duplicate detection and the raw response body.
• Macro inspector — Every macro available for that click with its actual value.

Limitations

• Restricted: Network admins only; partner accounts get a 404.
• Not supported: The chargeback status option isn't recognised by the server; a new test conversion sent with it is recorded as approved. Use rejected instead.
• Depends on: The campaign must be able to take the click (active, publisher allowed, within targeting and caps) or step 1 fails.

Common mistakes

• Reusing the same transaction ID — The second postback is treated as a duplicate — that's the duplicate protection working. Change the transaction ID to record another conversion.
• Testing on a live campaign — Test conversions are real and count toward caps, reports and invoices. Use a pending campaign (test traffic) or reject the test conversion afterwards.

Related

• Tracking tools
• Conversions not tracking