Standard Events

AnyTrack uses standard naming conventions that align with the industry best practices. This allows you to use a single naming convention and let AnyTrack translate, format, and forward your events and their related properties to your Conversion API integrations.

AnyTrack standard events

The AnyTrack platform triggers standard events via the AnyTrack JS Tag or via the Server-Side API when the event is triggered by a third-party platform (Affiliate Network, eCommerce platform, Zapier, or an external resource).

If you are using server-side API, read through this guide on Webhooks.

Standard events names

Standard event names are automatically tracked by AnyTrack according to the integration you selected. For example, when Anytrack with Shopify, standard events such as ViewContent, AddToCart and other standard ecommerce event names, are automatically captured by AnyTrack.

You can however trigger the AnyTrack Event tracking Snippet to trigger additional events.

AnyTrack('trigger', 'ViewContent');

//if you want to capture the event click_id and do something with it.
var = click_id = AnyTrack('trigger', 'ViewContent');

In addition to the Event Name, AnyTrack will collect the Event Context such as:

• Device information - browser, useragent, device type
• Time stamps
• Page Title, Location, Referrer, Page Path
• First party data from connected ads integrations and analytics
• Campaign data such as standard UTM parameters
• Event Attributes that you added to the Event Tracking Snippet (see the full list of supported Event Attributes)

Event Attributes

👍

Pro tip

Event Attributes are automatically translated and mapped to Ad Platforms' standard attributes. For example, the brand attribute is mapped to the content_name used in Facebook Conversion API.

When triggering an Event, AnyTrack collects the data you send through your JS tag and will also tie additional parameters that are natively collected through the JS Tag (Cookies, IP, User Agent...).

Customer data attributes

The following parameters are also supported for better matching and attribution. Those values will be automatically formatted and sent to Ad Platforms Conversion API.

👍

Good to know

Customer data attributes should never be sent to pixels via client side javascript, unless you hash the attributes according to pixel's hashing requirements. When using Anytrack, you can send this data via client-side javascript, and anytrack will automatically standardize it before sending it to ad platforms Conversion API (via Server to server integration).

📘

Good to know:

You don't need to hash the data as AnyTrack automatically formats and hashes the required data according to the ad pixels and analytics requirements.

E-Commerce event parameters

If you are integrated with an eCommerce platform, you can add a list of "items" following the parameters below:

Sending Events

You can send Events to Anytrack using the AnyTrack JS snippets or AnyTrack Webhook.

Client Side Event Snippets

  AnyTrack('trigger', 'Purchase', {
  	eventValue: 44.90,
  	currency: "USD"
  });

Server Side Webhook

The webhook relies on identifiers set on the client side to be available in Server Side calls. We recommend using the AnyTrack ClickId which is automatically generated by AnyTrack, but it can also be a userId, cookieid, anonymousId or any other identifier that you can expose in the browser and that will also be available in your Webhook payload.

👍

Good to know:

Refer to the list of standard events and attributes that can be automatically ingested by anytrack, and mapped to your ad platforms APIs such as Facebook, Google Ads or TikTok.

 AnyTrack('trigger', 'Alias', {
  	refId:"8a0sd8f09a8sdf098asdf" //userid in your business exposed via javascript
  });

https://t1.anytrack.io/accountid/collect/

{
    "eventName": "Purchase",
    "click_id": "f8e3bf8dfba8b51ce3340",
    "email": "[email protected]",   
    "refId": "8a0sd8f09a8sdf098asdf", //userid in your business previously exposed via javascript.
    "fullName": "Elon Musk",
    "address": "Milky Way 1",
    "phone": "+1919875666",
    "country": "Space",
    "items": [{
        "id": "20291",
        "name": "Sony MDRZX110/BLK ZX Series Stereo Headphones",
        "quantity": 1,
        "price": 20.00,
        "brand": "Sony"
        },
        {
        "id": "49292",
        "name": "Beats Headphones",
        "quantity": 1,
        "price": 100.00,
        "brand": "beats"
    }],
    "currency": "USD",
    "order_id": "24356562534585",
    "subtotalprice": 120.00,
    "totalprice": 120.00,
    "shippingPrice": 120.00,
    "taxPrice": 10,
    "eventValue": 120.00,
    "transactionId": "#24356562534585"
}

Example of a Client Side JS Tag (purchase event)

Here is a complete example of how to use the event parameter when triggering an event:

🚧

Good to know:

The AnyTrack Tracking Tag must be initiated before the event snippet can work.

<script>  
  var click_id = AnyTrack('trigger', 'Purchase', {  
    value: 29.9, // the total purchase value  
    shippingPrice: 5.9, // optional shipping price  
    taxPrice: 2.9, // optional taxes  
    currency: 'EUR',  
    transactionId: 'XJW0047',  
    email: '[email protected]',  
    firstName: 'John',  
    lastName: 'Smith',  
    items: [{  
      id: '20291', // the item catalog id (required)  
      name: 'Sony MDRZX110/BLK ZX Series Stereo Headphones',  
      quantity: 1,  
      price: 19.9 // the item price (required)  
    }, {  
      id: '49292', // the item catalog id (required)  
      name: '6.35mm Male 3.5mm Female Headphone Stereo Audio Connector',  
      quantity: 1,  
      price: 4.1 // the item price (required)  
    }]  
  });  
</script>

Standard Events: Frequently asked questions

When are 'OutboundClick' events triggered?

The OutboundClick event is triggered when a user clicks on an external link on your website. This could be an affiliate link, a link to a third-party website, or any other external link. During this event, a unique click_id is automatically generated by the AnyTrack tracking Tag.

Do I need to do anything to generate a Click ID?

No. The click_id value is automatically generated by anytrack at run time.

Why do 'OutboundClick' events generate a Click ID?

The click_id is generated during OutboundClick events to track and attribute user interactions on your website, building a comprehensive customer journey timeline. This data is then sent to ad platforms like Google Ads and Facebook Ads, allowing them to accurately attribute conversions to your ads and optimize campaigns.