Standard Events

Ad platform AI is only as good as the data you feed it. Standard events give ad platforms the consistent, structured signals they need to optimize campaigns. AnyTrack tracks every key action in your customer journey—product views, cart adds, form submits, purchases—using one naming convention that works everywhere.

When you track a Purchase event through AnyTrack, Facebook receives it as a Facebook Purchase, Google receives it as a Google purchase conversion, and TikTok gets CompletePayment. One event name, automatic translation to each platform's format. No custom mapping, no duplicate tracking code, no platform-specific implementation.

How Standard Events Work

Standard events capture Event Data—the specific actions users take on your site—and automatically map them to each platform's expected format. AnyTrack triggers these events through two methods:

1. Browser-side (AnyTrack JS Tag): Captures clicks, page views, form interactions, and client-side actions in real-time
2. Server-side (Webhook/API): Receives conversion data from platforms like Shopify, ClickBank, or Zapier that confirm completed transactions

Server-side events survive ad blockers, iOS restrictions, and browser privacy settings that would otherwise lose 20-30% of your conversions. Read the webhooks guide for server-side implementation.

Automatic Event Tracking

Most standard events track automatically when you connect an integration. Connect Shopify and AnyTrack immediately starts capturing ViewContent when users view products, AddToCart when they add items, and Purchase when orders complete. No code required.

Also trigger events manually using the AnyTrack snippet:

AnyTrack('trigger', 'ViewContent');

//if you want to capture the event `click_id` and do something with it.
var `click_id` = AnyTrack('trigger', 'ViewContent',{
  'id': 'a8df7asdf',
  'label': 'productLabel',
  'brandName': 'Nike',
  'value': 25.00,
  'currency': 'USD'
});

Every event AnyTrack tracks includes rich context that boosts Event Match Quality and gives ad platforms the signals they need to optimize:

• First-Party Data: Browser fingerprints, cookies, and session data that survive privacy restrictions
• Customer Data: Email, phone, name, and location (automatically hashed for privacy)
• Product Data: SKUs, prices, quantities, brands, and categories
• Campaign Data: UTM parameters, ad IDs, and click identifiers that connect conversions back to specific ads
• Device & Behavior Data: Browser type, device, page path, timestamps, and referrer

The more context each event carries, the higher your Event Match Quality score. Higher scores mean better attribution, more accurate lookalike audiences, and improved ROAS. See all supported Event Attributes.

❗️

Remember:

Event names as well as event attributes are case sensitive and are automatically mapped to standard events of ad platforms and analytics.

For example, Events from Shopify integration are mapped according to the following table

Shopify	AnyTrack Events	Facebook	Google Analytics
Order Created	Purchase	Purchase	purchase
Cart Created	AddToCart	AddToCart	add_to_cart
Item Viewed	ViewContent	ViewContent	view_item
Checkout Created	InitiateCheckout	InitiateCheckout	begin_checkout
Checkout Updated	AddPaymentInfo	AddPaymentInfo	add_payment_info

Each ad platform has it's own standard events and mapping.

Event Attributes

Every event can carry rich attributes — customer data, product details, and transaction context — that boost Event Match Quality and improve ad platform optimization. See the full Event Attributes reference for all supported parameters, customer traits, and product attributes.

Sending Events

You can send events to AnyTrack using the AnyTrack JS snippets or AnyTrack Webhook. Integrations available in the catalog have specific guidelines that should be followed.

Client Side Event Snippets

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

Server Side Webhook

Using webhooks to track conversions relies on identifiers set on the client side to be available in server-side calls.

For example:

1. AnyTrack generates a click_id and autotags affiliate links with the click_id value.
2. The affiliate network fires the AnyTrack postback URL with the click_id value.

We recommend using the AnyTrack click_id which is automatically generated, 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.

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

For complete webhook payload examples with all supported attributes, see Event Attributes.