Setting up conversion tracking
Track every conversion back to the click that drove it, measure the value you earn per source, and automatically catch attribution fraud — click injection, fabricated conversions, and clicks that were already fraudulent.
How it works
- A user clicks your MediaSafe tracking link. We record the click and generate a unique click_id.
- We redirect the user to your landing page and append the click_id as ?ash_cid to the destination URL.
- Your landing page stores that ash_cid value.
- When the user converts, you send a server-to-server postback with the same ash_cid, value, and source.
- MediaSafe ties the conversion to the original click, scores it for attribution fraud, and shows it in your dashboard.
Step-by-step setup
Create a tracking link
In your dashboard, open the Channels section and create a tracking link for your traffic source. Set its destination URL to your landing page. You'll get a short link like https://go.mediasafe.cc/aB3xK9.
Receive the ash_cid on your landing page
When a user clicks the tracking link, we redirect them to your destination and add the click identifier automatically:
https://your-landing.com/offer?ash_cid={CLICK_ID}
Capture this ash_cid value from the URL and keep it — in a hidden form field, a cookie, or your backend — until the user converts.
Send a conversion postback
When the conversion happens (purchase, signup, deposit), fire a single GET request to our conversion endpoint with the stored ash_cid:
https://go.mediasafe.cc/cv?ash_cid={CLICK_ID}&value={VALUE}&source={SOURCE}¤cy=USD
The endpoint returns a 1×1 transparent GIF and never blocks — it's safe to call from a pixel, a redirect, or your server.
Parameters
| Parameter | Description |
|---|---|
ash_cidrequired | The click identifier we appended to your landing URL. Ties the conversion to the original click. |
valueoptional | The monetary value of the conversion. Used for revenue reporting. |
sourceoptional | Traffic source label. If omitted, we use the source from the original click. |
currencyoptional | ISO currency code. Defaults to USD. |
siteoptional | Your public site key. Fallback if the ash_cid can't be matched to a click. |
Integration examples
Conversion pixel (thank-you page)
<img src="https://go.mediasafe.cc/cv?ash_cid={CLICK_ID}&value={VALUE}&source={SOURCE}" width="1" height="1" style="display:none" alt="">
JavaScript
fetch("https://go.mediasafe.cc/cv?ash_cid=" + CID + "&value=" + orderTotal + "&source=facebook");
Server-side (PHP)
file_get_contents("https://go.mediasafe.cc/cv?ash_cid=" . $cid . "&value=" . $total);
What you'll see
Open the Conversions section in your dashboard. You'll see total conversions and revenue, a breakdown of clean / suspicious / fraud verdicts, your conversion rate by source, and every attribution-fraud reason we caught.
FAQ
What if the ash_cid gets lost?
Send the postback with your site key as a fallback. The conversion is still recorded, but without a matched click it's flagged as unattributed (no_click_match).
Are duplicate conversions counted twice?
No. Each click_id can produce only one conversion — repeat postbacks for the same ash_cid are ignored.
What is click injection?
When a click is fired just seconds before a conversion to steal attribution. If the time between click and conversion is suspiciously short, we flag it as click_injection.
Getting started
Conversion tracking is available on Business and Enterprise plans. Set up a tracking link, add the postback, and you're live — or reach us at support@mediasafe.cc.