Generate, retrieve and use atclid

In this article, you will learn how to generate, retrieve, and use the atclid so you can include it in your conversion data sent to AnyTrack. If your platform (conversion source) is not listed in the AnyTrack Integrations Catalog, you can still track conversions using the AnyTrack’s Custom Integration. This option allows you to send conversion data to AnyTrack using a webhook. For this data to become a valid conversion event, it must include the click ID value (atclid).

Overview

The atclid is generated by the AnyTrack Tracking Tag installed on your website. You can generate it using an AnyTrack JavaScript function (`var atclid = AnyTrack('atclid');), then use webhook code to send it to a platform where you can collect it—such as Zapier or Make. From there, you can include the atclid in the conversion event data you send to AnyTrack.

Generate, Retrieve, and Include atclid

atclid generation

To see an example of atclid generation, navigate to any of your webpages where the AnyTrack Tag is installed, then run the following code in the browser's console:

var atclid = AnyTrack('atclid'); console.log(atclid);

atclid retrieval

Now you need a way to capture the atclid so you can use it later. To do this, you can use GTM scripting or other tools. In this example, I use a code to send the atclid via a POST request to an API (a webhook):

AnyTrack(function() {  
  var atclid = AnyTrack('atclid');  
  fetch("https://browserhook2.free.beeceptor.com", {  
    method: "POST",  
    headers: { "Content-Type": "application/json" },  
    body: JSON.stringify({ atclid: atclid })  
  });  
});

After running that code, my API shows the received atclid value, you can choose to use Zapier or Make to be able to make the atclid value part of the automation flow that will send the conversion data to AnyTrack.

Include the atclid

Create a Custom Integration endpoint in your AnyTrack account and, now you can send conversion events that include the atclid value in them. In addition to the atclid, you can and should include as many event attributes as possible, this will help training the ad network algorithm, making your targeting better. Check our our list of supported event attributes.

Solving Error: No Matches Found

The "No match(es) found" and "Missing click_id" errors in the Events Log of an integration occur when the atclid value is not included in the event data sent by your platform to AnyTrack. While the data is received, the absence of the click_id makes it impossible to associate the conversion with a specific website visitor. As a result, the ad that led to the conversion remains unknown. Without the click_id, AnyTrack cannot process the payload as a valid event.

FAQ

• Can I use any click_id in the conversion data I send to AnyTrack?
  No, you must send the atclid value generated by the visitor on your site, using a different clickId will cause an error or the event will be attributed to the wrong user. You need to use the atclid of the visitor on your site that generated the conversion event.
• What is the technology behind the clickId?
  Learn all about what the clickId is.