Track events

Once the Tag is installed, call:

window.thradTag("event", "<event_name>", {
  // any properties you want attached to the event
});

You can send any event name — custom strings are accepted — but using a name from the standard taxonomy below lets Thrad’s optimization and reporting recognise it without configuration.

Standard events

The category column groups events by shape. It isn’t validated on the server today, but it mirrors the property bundles each event tends to carry — useful as a mental model and matches the OpenAI Ads taxonomy.

Event	Category	Fires when…
`contents_viewed`	`contents`	A user views a product, listing, article, or other content unit.
`items_added`	`contents`	A user adds one or more items to a cart, bundle, or selection.
`checkout_started`	`contents`	A user starts checkout.
`order_created`	`contents`	A purchase is completed.
`lead_created`	`customer_action`	A user submits a lead form or requests contact.
`appointment_scheduled`	`customer_action`	A user books a meeting, demo, or consultation.
`registration_completed`	`customer_action`	A user finishes an account or event registration flow.
`trial_started`	`plan_enrollment`	A free trial starts.
`subscription_created`	`plan_enrollment`	A paid subscription starts.
`custom`	`custom`	Any user-defined event not covered above.

Examples

// Content view
window.thradTag("event", "contents_viewed", {
  content_id: "sku_123",
  content_type: "product"
});
 
// Cart add
window.thradTag("event", "items_added", {
  content_id: "sku_123",
  quantity: 2,
  value: 58.00,
  currency: "USD"
});
 
// Lead form submission
window.thradTag("event", "lead_created", {
  form_id: "newsletter"
});
 
// Custom — anything you like
window.thradTag("event", "video_completed", {
  video_id: "promo-q3",
  duration_ms: 32000
});

Event properties

The properties object is free-form — pass any keys you want and they’re stored against the event verbatim. There’s no fixed schema enforced by the Tag.

That said, using consistent property names across your site makes the data much easier to slice in reporting. Common conventions you’ll see in the examples above (content_id, quantity, value, currency, form_id, …) are conventions, not requirements.

For the order completion (purchase), use the Track conversions call instead — conversions are a separate event.

Install Track conversions