How do I test my postback for AI offers?

A postback you haven't tested is a guess. Testing takes a few minutes and tells you, before you spend on traffic, that sales will reach your tracker or ad network with the right click ID and payout. This answer gives you a three-layer test that checks every part of the chain.

Testing matters even more on AI offers. Sugarlab AI and SpiceStars AI are subscription apps, and paid campaigns for them are optimized on the sales your tracker sees. If the postback is broken, your tracker reports zero sales, your ad network's algorithm stops finding buyers, and you may pause placements that were actually profitable.

Three things must work together:

Test them in this order. Each layer depends on the one before it.

1. Copy your postback URL from the dashboard.
2. Replace each macro with a realistic sample value, for example {sub5} with test-123 and {payout} with 40.
3. Open the resulting URL in a browser or send it with a simple request tool.
4. Check your tracker for a test conversion with click ID test-123.

1. Click your real ad, tracker link or campaign URL, exactly as a visitor would.
2. Follow it through your tracker and landing page to the offer.
3. Open the OmniPink click report and find your test click.
4. Look at the sub field you use for click IDs, usually sub5.

If the click ID is missing, check each hop: the ad network's macro, the tracker's offer URL and any landing page link. See why a postback isn't firing.

A manual test proves the destination works. Only a recorded conversion proves the whole chain. You have two options:

Option A: ask support for a test conversion

Contact support by email at affiliates@omnipink.ai or on Telegram at @OMNIPINK and ask for a test conversion on your link. Share the tracking link you used for your test click and the time of the click. Don't buy through your own link without arranging it first, because self-referrals aren't paid and can be flagged.

Option B: wait for a first small sale

Run your campaign at a small budget until the first sale arrives, then check that it reached your tracker. This tests everything under real conditions, at the cost of a little time.

Open the postback report in the dashboard after a test conversion or first sale:

• Fired: confirms the postback was triggered by the conversion.
• Response code: 2xx means success; 4xx or 5xx means the destination rejected or failed.
• Debug view: shows the exact URL called, with macros replaced, and the destination's reply.

In the debug view, confirm that the click ID is a real value, the payout is a number and the URL points to your tracker.

• Before launching any paid campaign.
• After changing your tracker, landing page or tracking links.
• After a tier upgrade, when your links move to a new offer.
• After editing the postback URL or scope.
• Whenever conversions in your tracker and the dashboard drift apart.

• Manual test accepted by the tracker.
• Test click shows a real click ID in the click report.
• Postback scope covers the offer your links use.
• Test conversion or first sale shows a 2xx response.
• Click ID and payout look correct in the debug view.
• Test conversions removed from your tracker.

Say your tracker gives you this postback URL, where cid is the tracker's click ID and payout is the amount:

https://tracker.example.com/postback?cid={sub5}&payout={payout}

For layer 1, replace the macros with sample values and open the result:

https://tracker.example.com/postback?cid=test-123&payout=40

Your tracker should now show a test conversion for click test-123 with a payout of 40. For layer 2, run a real click through your ad and tracker. In the OmniPink click report, sub5 should show the tracker's real click ID, a long string of letters and numbers, not test-123 and not {clickid}. For layer 3, after a test conversion or a first sale, the postback report's debug view should show the same URL with that real click ID and the real payout in place of the macros, and a 2xx response from the tracker.

Most affiliate trackers work the same way, but each names things a little differently.

In every case, use the tracker's own click ID macro in your tracking link's sub5 field, and the matching parameter name in the postback URL. If the tracker documentation lists a "test conversion" feature, run it as part of layer 1.

• Testing with your normal browser. Extensions and old cookies can change the click path. Use a private window.
• Testing an old link. After a tier upgrade, links move to a new offer. Test the link you will actually publish.
• Forgetting the scope. A postback set up for one offer doesn't fire for the other app. If you promote both Sugarlab AI and SpiceStars AI, check both, or use a global postback.
• Buying through your own link. Self-referrals aren't paid and can be flagged. Ask support for a test conversion instead.
• Leaving test data in your tracker. Test conversions inflate your numbers and confuse optimization. Delete them.
• Changing several things at once. If you edit the link, the postback and the tracker at the same time, you can't tell which change fixed or broke the chain.

If you send conversions to Google, Meta, TikTok or Reddit, the final step happens in your tracker, which forwards the conversion through the platform's conversion API. After layer 3, check that the conversion also appears in the ad platform's events or conversions view. Allow some delay, since platforms often process conversions in batches.

Can I test without spending any money? Layers 1 and 2 cost nothing. Layer 3 needs a test conversion from support or a first real sale.

Why did my manual test work but real conversions don't arrive? The destination works, so the click ID is probably not reaching your tracking link, or the postback scope doesn't cover the offer.

How long until a postback fires after a sale? Usually shortly after the conversion is recorded. If you see the conversion in your report but no postback fire, check the scope and the report filters.

Do I need a separate postback for each app? Not if you use a global postback, which fires for every offer. An offer-specific postback fires only for the offer it is set on, so you need one for each app and tier offer you promote.

Is testing different on CPA and RevShare? The steps are the same. The difference is the payout value: on CPA it is the fixed amount for that sale, and on RevShare it is your share of the payment, so it changes with the plan the subscriber buys. Make sure your tracker accepts decimal values.

How many test clicks do I need? One clean click per link is enough for layer 2. Run one for each traffic source, because each source passes its click ID in its own way.

Should I test again after a tier upgrade? Yes. Your new links point to a new offer, so check that your postback scope covers it and run layers 2 and 3 again.

Contact support if a test conversion shows in your report but no postback fires, or if the debug view shows values you can't explain. Include the postback URL, the test click time and screenshots.

• Why is my postback not firing?
• Postbacks onboarding step
• Adult traffic buying and scaling