To assess the effectiveness of your advertising activities, conversion monitoring may be essential. And when you execute CPA (cost-per-action) driven campaigns, it is an absolute must. Here, we will explain how to configure conversion tracking on our platform.

Both client-side (cookie-based) tracking and server-to-server (s2s) conversion tracking are supported by our platform. These settings are usually sufficient for keeping track of installs, registrations, and other similar actions.

Postbacks

You must create at least one postback in the Settings / Postbacks menu in order to measure conversions.

Conversion tracking software is called Postback. The conversion is technically saved to the database of the ad server by a URL (or a piece of JS code) that gets a conversion.

After you create a new postback in the system, you will immediately receive a special URL (or JS snippet).

You are allowed to generate as many postbacks as your campaign requires. A certain group of settings can be defined for each postback. You can permit or forbid, for instance, passing custom amounts.

Server-to-server (s2s) conversion tracking

To set up server-to-server conversion tracking:

• Acquire an endpoint URL, you must first establish a postback as previously explained.
• Then, in your advertising campaign, you must include a random parameter to the URL for your landing page. A visitor will immediately replace the placeholder "click" with a special token and forward to the URL.
• After that, you must save the token and, in the event of conversion, send it back to our server by contacting a postback URL.

You can do it with PHP:

Or HTML on a thank you page:

This way the conversion will be recorded. 

Additionally, if you have enabled custom postback amounts, you can send a specific amount in your URL. To do that, add the "&amount=AMOUNT" parameter to the postback URL mentioned above. The AMOUNT value exceeds the campaign’s configured CPA rate and will be reflected this way in statistics.

Client-side tracking

To create client-side (cookie-based) conversion tracking:

1. You must first create a postback and acquire two JS snippets. At the top of the postback view page, you must select "Client-based."

2. Add the _aso clk=click parameter to your landing page's URL. The parameter name must exactly match _aso clk. The tracking won't function properly otherwise.

3. Add the first excerpt on your “Thank you” page and landing page.

4. Place the second snippet on your "Thank you" page.

Additionally, by executing the "_ASO.Postback.send()" method in your code, you may transfer a conversion dynamically. The first snippet is still necessary for this scenario even if you don't need to add the second one to the page.

You may send a custom amount as well (if it's enabled in a postback), as with s2s tracking. You should provide the required amount as the function's first parameter, _ASO.Postback.send, to do that.

Some browsers and anti-ad plugins have the ability to prevent cookies. Conversions might not reach our server in this scenario.

Tester tool

To configure conversions, test tokens can be required, to test a third-party tracker configuration or even own script.

To test a postback URL, click the "Tester" button in the Postback page.