Advertiser tracking setup

How to receive our click ID in your tracking link and send it back in a postback when a user completes your event. Works with your own server or an attribution platform.

Tracking needs two things from you: a place in your tracking link for our click ID, and a postback to us when the event happens, with that click ID in it. Nothing is billed until that postback arrives.

1. Your tracking link

When a user takes your offer, we redirect them to your tracking link with a click ID attached. You give us the link when you submit a campaign, and it decides where the click ID goes:

A placeholder in the link. We put {click_id} where your link expects its sub ID, and replace it on every click:
```
https://track.example.com/go?campaign=123&sub1={click_id}
```
A query parameter. If there is no placeholder, we add the click ID as a parameter on the end, by default click_id, or any name you tell us:
```
https://track.example.com/go?campaign=123&click_id=4UrYBk82JE5Zcj1D
```

Click IDs are short, URL-safe strings of letters, numbers, - and _. Store the value exactly as received.

2. Your postback

When the user completes the event, send it back to your postback URL. Copy it from Postbacks in your dashboard; it looks like this, with your own token:

https://cashadmedia.com/postback?token=YOUR_TOKEN&click_id={click_id}&event={event}&txn_id={txn_id}&status={status}

Replace each {…} with your own system's macro. For example, if your platform calls the sub ID {sub1} and its transaction ID {transaction_id}:

https://cashadmedia.com/postback?token=YOUR_TOKEN&click_id={sub1}&txn_id={transaction_id}

Only token and click_id are required. Leave out status for an approved conversion and event for a single-step offer. The postback reference lists every parameter and the accepted alternative names.

Keep the token private. Anyone who has it and a valid click ID for one of your offers can report conversions on it. If it leaks, press Replace token on the Postbacks page. The old one stops working at once, so update every postback URL that uses it. The same page lists your last 50 postbacks and what we answered, which is the quickest way to debug a setup.

3. Multi-step offers

If you pay for several events, such as install, level 10 and first purchase, each one is a separate postback with its own event value. We agree the event names when we set up the offer. A postback whose event doesn't match one of the offer's steps is rejected.

4. Test it

Before the offer goes live we send a test click through your tracking link. Fire the postback for it from your system and we confirm it arrived and what it created. After that, every postback you send is logged on our side, accepted or not, so mismatched macros are quick to find.