Conversion tracking is an important feature of any third party ad server. It allows you to measure how many users converted after clicking on your ads, so that you can measure your return on investment (ROI). A conversion can be anything: a sale, a signup, a download, or anything that's valuable for you to measure post-click.

Setting Up a Conversion Tracker

To begin tracking conversions in AdGlare, follow these steps:

Go to the Settings page, then choose Conversion Trackers
Create a new conversion tracker
Configure the tracker by indicating which query parameter you would like to use for the conversion token, for example ct

The value of the query parameter will be a unique conversion token while delivering the ad.

Conversion Tracking Ss1 AdGlare AdServer

Assigning a Conversion Tracker to a Campaign

To use a conversion tracker for a certain campaign:

Open the campaign in your AdGlare
Go to the Settings tab of the campaign
Select the desired Conversion Tracker from the dropdown

AdGlare will now automatically append a unique conversion token to the landing page URL for all creatives under that campaign. You do not need to manually update landing URLs or edit creatives.

Conversion Tracking Ss2 AdGlare AdServer

Storing the Conversion Token on Your End

When a user clicked on your ad, the conversion token will be added to the URL of the landing page. You need to store this token somewhere until the user converts. For example, in a PHP session or client-side using localStorage. Here are some examples where we assume that you've configured your query parameter as ct.

PHP SESSION Example

session_start(); if (isset($_GET['ct'])) { $_SESSION['conversion_token'] = $_GET['ct']; }

JavaScript localStorage Example

const urlParams = new URLSearchParams(window.location.search); const token = urlParams.get('ct'); if (token) { localStorage.setItem('conversion_token', token); }

Callback URL

Your callback endpoint URL to log conversions is:

https://{your_name}.engine.adglare.net/event/CONVERSION_TOKEN_HERE?conv_value=0.00

Replace {your_name} with your customer name that you can derive from your AdGlare portal URL.

Sending the Conversion Event

Once the user converts, you have to send the conversion token back to AdGlare using an HTTP request, so that it will be logged in your reports. You can either send callbacks client-side or server-side.

Client-Side Example (JavaScript)

const token = localStorage.getItem('conversion_token'); if (token) { navigator.sendBeacon('https://{your_name}.engine.adglare.net/event/' + token); }

Server-Side Example (PHP cURL)

$token = $_SESSION['conversion_token'] ?? ''; if ($token) { $url = 'https://{your_name}.engine.adglare.net/event/' . $token; $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_exec($ch); curl_close($ch); }

Reporting Conversion Values

To report the value of the conversions in your reports, you can either:

Use a fixed value (e.g. $25) as a default via your conversion tracker configuration
Add a dynamic value to your callback URL when logging the conversion by appending the conv_value query parameter:

https://{your_name}.engine.adglare.net/event/dAXhTGek9s...&conv_value=49.95

Only numeric values and decimals are supported. The currency symbol used will be based on your global account settings.

Showing Conversion Data in Your Reports

To show the number of conversions, conversion rate and conversion value, head over to the Reports page. Click the Columns icon at the right, and enable all conversion-related metrics.

Conversion Tracking Ss3 AdGlare AdServer

Reducing Token Size

By default, AdGlare captures user dimensions like browser and OS in the conversion token. If you use a content management system that has limited storage space for tokens, you can reduce the token length by capturing only the most important data (campaign ID, creative ID, zone ID, etc).

To reduce the token size, enable the toggle in your conversion tracker setup.

White Label Domains

If you use client-side JavaScript logic to log a conversion, you may want to use your auto_storieswhite label domain for your callback URL. This prevents the callback from being blocked by ad blockers, improving the accuracy of your conversion metrics.

Simply replace the engine domain from AdGlare with your own white labeled engine domain. For example:

https://engine.acme.com/event/dAXhTGek9s...