AutoTrack

AutoTrack is the client-side event detection engine built into the AnyTrack Tracking Tag. It monitors user interactions on your website and fires standard events — OutboundClick, FormSubmit, ViewContent, AddToCart — the moment they happen. No custom code, no event listeners to write, no manual configuration.

AutoTrack only fires events for platforms you have integrated in AnyTrack. When it detects an interaction with a tracked element, it captures the element attributes (item details, form name, link URL, quantity, value) and sends them as event attributes along with the event. This gives your ad platforms rich data for attribution and optimization.

Events AutoTrack Captures

AutoTrack watches for four categories of client-side interactions:

OutboundClick

Fired when a visitor clicks an affiliate link, merchant link, or any outbound link tied to an integrated platform. AutoTrack captures:

• Destination URL
• Link text and anchor attributes
• The AnyTrack Click ID (atclid) appended by AutoTag

This works for standard HTML anchor tags and links managed by WordPress plugins like PrettyLinks and ThirstyAffiliates.

FormSubmit

Fired when a visitor submits a form on your site. AutoTrack captures the form name, form ID, action URL, and any field values mapped through your tracking configuration. For detailed setup options, see the Form Tracking guide.

ViewContent

Fired when a visitor views a product page, landing page, or other content page tied to an integrated eCommerce or affiliate platform. AutoTrack reads product details from the page (item name, price, category) and includes them as event attributes.

AddToCart

Fired on eCommerce sites when a visitor adds a product to their cart. AutoTrack captures the item details, quantity, and value from the cart action. The specific behavior depends on your platform integration:

For the full list of supported platforms, check the Integration Catalog.

How AutoTrack Ties to Your Integrations

AutoTrack does not track everything on your site. It specifically monitors interactions with elements that belong to platforms connected in your AnyTrack Integration Catalog. When you add an affiliate network, eCommerce platform, or lead gen tool as an integration, AutoTrack knows which links, forms, and checkout flows to watch.

This means:

• Add a Shopify integration, and AutoTrack starts capturing cart and purchase events on your Shopify store
• Connect an affiliate network like ClickBank, and AutoTrack fires OutboundClick for links pointing to ClickBank offers
• Integrate a form builder, and AutoTrack picks up form submissions automatically

If a link or form is not tied to any integration in your catalog, AutoTrack ignores it.

Element Attributes in Tracked Events

Every AutoTrack event includes attributes extracted from the tracked element. These attributes flow through to your ad platforms as event attributes, improving Event Match Quality and enabling value-based bidding.

AutoTrack vs Server-Side Tracking

AutoTrack handles client-side events only — interactions that happen in the visitor's browser. Server-side conversions (postback callbacks from affiliate networks, webhook notifications from eCommerce platforms) are processed separately through your server-side integrations.

Both data paths feed into the same AnyTrack processing pipeline, where deduplication prevents the same conversion from being counted twice.

AutoTrack and AutoScan

AutoScan crawls your site to discover which elements can be tracked. AutoTrack is the runtime engine that captures interactions with those elements as visitors use your site.

Verifying AutoTrack Events

Open your site in a browser, interact with a tracked element (click an affiliate link, submit a form, view a product page), then check the Integration Event Log in your AnyTrack dashboard. The event should appear within seconds, showing the event type, destination, and captured attributes.

If events are not appearing:

• Verify the Tracking Tag is installed and loading
• Confirm the relevant platform is connected in your Integration Catalog
• Check that the element is a standard HTML tag (not JavaScript-only navigation)
• Make sure the destination is not in your ignored sources list