Testing postbacks

A postback that you send with a real token creates a real conversion. It defaults to approved and counts in reports. Test with the tools in the Stats app first.

All three tools are on the program's Integrations page.

1. Check the endpoint

Open the Postback endpoint card and click Test endpoint. DataFlair checks two things: the program is active, and it has a postback token. When both are true, it shows "Postback endpoint is ready to receive events."

This check sends no postback and creates no conversion.

2. Fire a test postback

Find the Fire test postback form in the Field mapping section. Choose an approved affiliate, a conversion type (registration, ftd or deposit) and an amount, then send it.

DataFlair sends a synthetic postback through the real endpoint, so the token check, the validation and the duplicate check all run as they do for live traffic. If the program has a field mapping, the test postback uses your field names.

• The event is marked as a test. It does not earn commission.
• Its postback_id starts with test- and its player_id starts with PLAYER-TEST-.
• It shows in the Postback log tab, and in the Test fires counter.

The form appears once the program has a postback token and at least one approved affiliate.

3. Replay a logged postback

Open the Postback log tab and click a row. The Postback detail panel opens. When a row can be replayed, the panel has a Replay postback button.

A replay sends the logged request through the real endpoint again, with the program's current token. Use it after you fix a cause, such as an affiliate that was not approved yet.

• A replay is not a test. It processes the original event as real traffic. If the original was rejected and now passes, it creates a real conversion.
• Replaying a postback that was already accepted does nothing. DataFlair answers with the duplicate response.
• You cannot replay a test event, or a request that failed authentication.

What to check after a test

1. The Postback log shows the request with the status you expect.
2. The response codes match the error table.
3. Sending the same postback_id twice gives duplicate: true the second time. See Idempotency.