How the flow works
- ClickAdilla generates a click identifier.
- Your landing page or tracker stores that identifier.
- The visitor completes a defined conversion event.
- Your server, tracker or affiliate network sends an HTTP request to the postback URL.
- ClickAdilla records the conversion against campaign statistics.
Core parameters
| click_id | Links the conversion to the original click and must be captured correctly. |
|---|---|
| campaign_id | Identifies the campaign when included in the landing link. |
| payout | Optional revenue value used for profit reporting. |
| conversion_id | Separates multiple funnel stages such as registration and purchase. |
Never copy another account's token. Use the template shown inside your own Tracking tab and map placeholders to the corresponding macros in your tracker or affiliate network.
Pre-launch test checklist
- Open the campaign link and confirm the click ID reaches the landing page.
- Complete a controlled test conversion.
- Confirm a successful HTTP response and one conversion in statistics.
- Check that payout and conversion stage are assigned correctly.
- Prevent duplicate firing on refresh or repeated callbacks.
Multiple conversion events
The official documentation supports separate requests for funnel stages using conversion_id. Decide which events are informational and which event controls optimization. Sending every page view as a conversion creates misleading data.
Common failure modes
Most errors come from a missing click ID, mismatched macro names, URL encoding, an incorrect account token, duplicate callbacks or testing a different campaign from the one in the postback. Log the final request without publishing secret tokens.
Privacy and consent
If identifiers are stored in cookies or local storage, apply the consent and disclosure rules relevant to the visitor's location. Avoid sending personal data in URL parameters. The official guide specifically notes GDPR and local privacy requirements.
Primary documentation
Compare this explanation with ClickAdilla's current postback URL documentation. Dashboard tokens and available reporting can change.
Example postback flow with a tracker
- Campaign URL in ClickAdilla passes the click macro to your tracker.
- The tracker stores it and redirects to the offer.
- The affiliate network fires a postback to your tracker on conversion.
- The tracker fires the ClickAdilla postback with the stored click ID and payout.
Use the macro names shown in your own Tracking tab — they differ between trackers and networks.
Why postback matters for optimization
Source blacklisting and CPA Goal bidding both rely on conversions reaching ClickAdilla. Without postback, you can only optimize by clicks — which on popunder and push often means optimizing toward bots.