The purpose of this document is to provide instructions for installing your Creatable link (c-link) tracking pixel for the purpose of enabling the first-party tracking of links shared by creators.
window._tvpa = window._tvpa || ;
li: "XXXXXXX", // Account ID
tvpa.src = ('https:' == document.location.protocol ? 'https' : 'http') + '://a.tvpage.com/tvpa.min.js';
var s = document.getElementsByTagName('script'); s.parentNode.insertBefore(tvpa, s);
Once installed, this pixel will always load on your site, if the URL of the page contains a trackable c-link variable, the analytics pixel will fire a subsequent request.
It is a best practice to use a tag manager to install this pixel as it makes the process of managing tracking pixels in general much easier.
Our analytics system utilizes 2 separate cookies for conversion tracking. One cookie is a first-party cookie, the other is a third-party cookie. This to ensure that older sessions can be captured, tracked and attributed correctly as third-party cookies are phased out.
Name: __tvpa, Type: first party cookie, Domain: .yourdomain.com, Value: 32 character hash
Name: __tvpab Type: third party cookie, Domain: .tvpage.com, Value: 32 character hash
After you have completed the installation, if you wish to validate that the pixel is working correctly, this can be easily tested with the following steps.
- Obtain a link to a page where the tracking pixel has been installed. For the purposes of these steps, let’s assume: https://www.domain.com/product.html
- Append to this URL the following parameter: ?_dl=000000;123456789
- Once you have combined your page URL and the test parameter, open up a web browser and open the Dev Tools console. If needed, select the Network tab so that you can observe the network requests.
- Paste the URL into the web browser, and you should see lots of network requests being made, if you filter this by “_tvpa” you will see a short list of network requests after the page has completely loaded.
- There should be a total of 3 network requests that are made. If you look at the URL parameters of each of these requests, you should see the rt= parameter. The 3 different requests being made are rt=cid, rt=hb and rt=dl.
If you examine the rt=dl request’s URL parameters, you should see the li=, ui= and ct= parameters populated with your account ID, and the 2 values that were parsed from the page’s original URL request. If this request is not present, then there is a problem with the implementation of the tracking pixel, please contact firstname.lastname@example.org and we will work with you to get it working as expected.