Run this test once when setting up a new publisher integration - to confirm that the tracking link, conversion attribution, and publisher postback are all configured correctly. If you later change the postback URL or other settings, run it again to verify.
Before you start
Make sure the following are in place before testing:
Offer status is set to Active
Publisher is approved on the offer
Publisher has set up the offer on their side and shared their test tracking link with you
Publisher postback URL is configured in Swaarm
Method 1 - Test Publisher Integration tool (recommended)
Go to Tools → Test Publisher Integration.
Select the offer you want to test
Select the event (use Default for install, or select a specific in-app event)
Paste the publisher's test tracking link
Click Test Integration
After a few seconds you'll see one of two results:
✅ Test Successful
the click was tracked, a test conversion was generated, and the publisher postback fired correctly. The integration is working.
✅ Test Successful but publisher says they didn't receive the postback
Go to Reports → Conversion Report, find the test conversion, and check:
Pub. Postback URL column - confirms what URL Swaarm fired
Response Code column - a non-200 response means the publisher's server rejected or didn't receive it. Ask the publisher to check on their end
❌ Test Failed
something went wrong. A short message will indicate the general issue. To further investigate you can always look into the conversion report or reach out to the technical client service team via the chat button or email.
Error message | What to check |
No click ID found in the redirect | The publisher's tracking link isn't passing the click ID correctly. Go to Tools → Scan Offer, paste the publisher's link, and inspect the redirect chain to see where it breaks. |
Publisher postback not configured | Go to Publishers → [Publisher name] → Postback Links and verify the postback URL is saved correctly. |
Method 2 - Manual test using Scan Offer (advanced)
Use this option when you need more control - for example, inspect the full redirect chain, or manually fire a postback with a custom click ID.
Step 1 - Get the Swaarm click ID
Go to Tools → Scan Offer
Paste the publisher's test tracking link in the Tracking Link field
Select the Country and OS matching the offer targeting
Click Scan
In the URL chain that appears, find and copy the Swaarm click ID
ℹ️ Swaarm click IDs always start with a capital A or capital B (example, BnKaIuIAAAGdZ_2MhwAAcGcAAACHAAAAAAAAACcPAAADHv4)
Step 2 - Fire a test postback
For a default event (install):
Replace {yourdomain} with your Swaarm domain and [CLICK_ID] with the click ID you copied in Step 1 and open the URL in your browser:
For a specific event (e.g. purchase):
Go to the offer's Events tab, copy the event postback URL for the desired event, add click ID you copied in click_id parameter, and open the URL in your browser:
Step 3 - Verify the result
Go to Reports → Conversion Report and search for the click ID you used. The conversion should appear with:
Decision: Passed
Status: Approved
Publisher postback fired ✓
To confirm the publisher postback was fired, add the Pub. Postback URL column to your Conversion Report view - it shows the exact URL that was sent to the publisher and the HTTP Code response received from their server.
Scan Offer vs Test Publisher Integration - when to use which
Situation | Use |
Routine setup verification | Test Publisher Integration |
Need to inspect the full redirect chain | Scan Offer |
Need to test a specific event postback manually | Test Publisher Integration |
Want to verify advertiser link reaches the store | Scan Offer |
Quick check that postback fires end-to-end | Test Publisher Integration |
FAQ
1) The publisher doesn't see the conversion - how do I check if the postback was sent?
In the Conversion Report, check the Pub. Postback URL column - it shows the exact URL Swaarm fired to the publisher. Also check the HTTP Code column to see how the publisher's server response. If Decision is Passed but the postback column is empty, the postback URL may have not been configured correctly.
2) The postback was sent but the publisher still didn't receive it - what now?
There may be a delay on the publisher's side. Copy the fired postback URL from the Pub. Postback URL column in the Conversion Report and share it with the publisher - ask them to check it internally.
3) The publisher's test link doesn't redirect in Scan Offer - why?
Check that the Platform and Country selected in Scan Offer match the offer's targeting. If it still doesn't redirect, confirm with the publisher whether there are any restrictions or advanced targeting on their side.
4) The publisher test link redirects to the Swaarm tracking link, but the Swaarm link doesn't redirect to the landing page - why?
Check that the Platform and Country in Scan Offer match the offer's settings, and that there are no budget caps or advanced targeting restrictions on the offer. You can also check the Failed Click Rules for this offer in Explorer or Custom Report.
5) The publisher click ID is missing from the postback - why?
Check the postback macros configured on the publisher's postback URL. If any macro is incorrectly formatted, Swaarm won't fire the postback at all. The click ID macro is #{click.publisher.clickId} - note that the # is part of the macro syntax and must not be removed. See all publisher postback macros →
6) How do I test a specific event postback?
In the Test Publisher Integration tool, select the offer and then choose the specific event from the Event dropdown - it shows all events configured on that offer. Select the one you want to test, paste the publisher's tracking link, and click Test Integration.
