Parameter Mappers: Tracking values in your landing page URL

Updating parameter mapping settings on a campaign

1. Navigate to your Campaign List.
2. Click the "view" button next to your campaign to bring up your Campaign page.
3. Click the Retreaver JS settings tab.
4. Click the Parameter Mappers tab.
5. Click the Edit button, make your changes, and press "Update Campaign".

Detecting publisher IDs from your landing page

Retreaver extracts Publisher IDs (also known as Affiliate IDs or Source IDs) from your landing page query string using Parameter Mappers.

In the image above, we've configured a campaign to detect a Publisher ID from the "afid" parameter of a landing page URL.

In the example landing page URL above, we see that the query string of the URL include an "afid" parameter, and we can see that the afid is set to 1234.

Retreaver.js will detect the value of "publisher_id" using the "afid" mapping, it will then attempt to find a matching number, from either a number pool or a static number to display a number assigned to that specific publisher.

Retreaver can extract unlimited arbitrary URL parameters in the same manner, setting tags on numbers for each parameter mapper that's matched.

You can even have multiple URL Parameters mapping to the same Tag Key if you use different parameter names on different landing pages. We'll use whichever parameter is found in your landing page query string.

Company default parameter mapping settings

1. Click the Settings button on the left.
2. Click Company.
3. Click Edit Company.
4. Click the green plus sign in the Default URL Parameter Mappers section, make your changes, and click Update Company.

Passing data to your landing page from popular systems

You can edit your landing page URL template in popular tracking systems to pass arbitrary tracking parameters to your landing page for Retreaver.js to detect. For each parameter, you must have a parameter mapper present on your campaign to turn the parameter into a Retreaver Tag.

Google Adwords

Google uses "UTM values" to pass data about which ad was clicked.

https://support.google.com/analytics/answer/1033981

Facebook

https://www.facebook.com/business/help/1016122818401732

Cake

https://support.getcake.com/support/solutions/articles/5000546258-tokens-in-the-offer-link 

HasOffers

https://help.tune.com/hasoffers/passing-values-to-an-offer-url/

Voluum

https://doc.voluum.com/en/tracking.html

LinkTrust

https://support.linktrust.com/hc/en-us/articles/115001207231-Tracking-URL-Tokens

As an example, in LinkTrust you would add ?afid=[=AFID=]&sid=[=SID=] to the end of the landing page URL on the Campaign Edit screen.

Parameter mapping cookie storage

Retreaver stores all gathered URL parameters for the entire duration of a leads browser window. In the case a lead clicks through various pages and revisits your lander at a later time on the same browser session - Retreaver will be able to re-associate any gathered URL parameters back to that lead and tag the data to a resulting call generated using the tracking number placed on your page.

Retreaver hashes and stores this data using two different cookies:

The "CallPixels-u" cookie is the most recent visitor URL.
The "CallPixels-ou" cookie is the original visitor URL.

To only use tags from the latest visit, you must clear the "CallPixels-ou" cookie on page load: