Use AnyTrack Click ID (atclid)

Overview

When your platform (conversion source) isn't listed in the AnyTrack Integrations Catalog, you can still track conversions using AnyTrack's Custom Integration. This method allows you to send conversion data to AnyTrack using a WebHook.

For conversion tracking to work properly, your conversion data must include the AnyTrack click ID (atclid). This unique identifier connects each conversion back to the specific ad click that generated it, enabling accurate attribution modeling.

What is the AnyTrack Click ID (atclid)?

The atclid is a unique identifier generated by the AnyTrack Tracking Tag when a visitor clicks on your ads and lands on your website. This ID is essential for:

• Conversion tracking: Linking sales and leads back to specific ad clicks
• Attribution modeling: Understanding which ads drive the best results
• Campaign optimization: Providing accurate data to improve ad performance

How to Generate, Retrieve, and Use atclid

Step 1: Generate the atclid

The atclid is automatically generated by the AnyTrack Tracking Tag installed on your website. To see how this works, navigate to any webpage where the AnyTrack Tag is installed and run this code in your browser's console:

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

Step 2: Capture the atclid

You need to capture the atclid so you can include it in your conversion data later. You can use Google Tag Manager (GTM) scripting or other automation tools to capture this value.

Here's an example using JavaScript to send the atclid to an external platform via 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 this code, your WebHook endpoint will receive the atclid value. You can use automation platforms like Zapier or Make to capture this data and include it in your conversion tracking workflow.

Step 3: Send conversion events with atclid

1. Create a Custom Integration endpoint in your AnyTrack account
2. Send conversion events that include the captured atclid value
3. Include additional event attributes to improve attribution modeling and ad optimization

For better conversion tracking results, include as many relevant event attributes as possible. This helps train ad network algorithms and improves targeting effectiveness. Check our list of supported event attributes.

Troubleshooting: "No Matches Found" Error

If you see "No match(es) found" or "Missing click_id" errors in your Events Log, it means the atclid value wasn't included in your conversion data.

Why this error occurs:

• The conversion data sent to AnyTrack doesn't include the required atclid
• Without the click ID, AnyTrack cannot link the conversion to a specific website visitor
• The system cannot determine which ad generated the conversion
• The conversion event cannot be processed for attribution modeling

How to fix this error:

1. Verify your atclid capture code is working correctly
2. Ensure the atclid is included in all conversion event data
3. Test your WebHook integration to confirm the click ID is being transmitted
4. Check that your automation platform (Zapier, Make, etc.) is properly forwarding the atclid

Frequently Asked Questions

Can I use any click_id in the conversion data I send to AnyTrack?

No, you must use the specific atclid value generated by the actual visitor on your website. Using a different or incorrect click ID will cause attribution errors or link the conversion to the wrong user. The atclid must match the visitor who generated the conversion event.

What technology powers the AnyTrack click ID system?

Learn more about how AnyTrack click ID works and the technology behind conversion tracking and attribution modeling.

How long is the atclid valid for conversion tracking?

The atclid remains valid for the duration of your attribution window settings in AnyTrack. This ensures conversions can be properly attributed even if they occur days or weeks after the initial ad click.

What happens if multiple people use the same device?

Each unique visitor session generates its own atclid, so conversions are attributed to the correct ad interaction even on shared devices.