Events Reference
An event is a single action a visitor takes on your site: viewing a product, adding to cart, completing a checkout. TrueTracked records these to build attribution, and forwards them to your ad platforms through TrueSignal.
Most events are sent for you automatically by the tracking script and the Shopify integration. This page lists every event TrueTracked recognises, so you know what is already being collected and what you can send yourself.
Only recognised events are recorded
TrueTracked accepts an event only if it is a standard event from the table below, or a custom event you have defined under Settings → Events. Anything else is discarded before it reaches your reports.
Your workspace ID is visible in the tracking script on every page of your site, so without this rule anyone could push made-up events into your data. It also stops a typo in your own code from quietly creating a second, near-duplicate event that splits your numbers.
A discarded event looks like success, not an error. It returns HTTP 200 with a body of {"success":true,"dropped":"unknown_event"}, so nothing appears in your browser console. The data is simply missing. If an event is not showing up, open your browser's Network tab, find the event request and read the response body.
Standard events
These are always accepted, with no setup required.
| Event | Category | Sent by |
|---|---|---|
page_viewed | pageview | Automatic |
product_viewed | product | Shopify integration, or you |
collection_viewed | product | Shopify integration, or you |
cart_viewed | cart | Shopify integration, or you |
product_added_to_cart | cart | Shopify integration, or you |
product_removed_from_cart | cart | Shopify integration, or you |
search_submitted | search | Shopify integration, or you |
checkout_started | checkout | Shopify checkout |
checkout_address_info_submitted | checkout | Shopify checkout |
checkout_shipping_info_submitted | checkout | Shopify checkout |
payment_info_submitted | checkout | Shopify checkout |
contact_info_submitted | checkout | You |
checkout_completed | checkout | Shopify checkout + order webhook |
purchase | purchase | You (custom checkouts, no webhook) |
email_captured | identity | Automatic |
On a Shopify store the checkout events are handled by the integration, so you do not need to fire them yourself. On a custom site you send the ones that apply. See Tracking Custom Websites for the purchase event in particular.
Event categories are assigned automatically
Each event is filed under a category (pageview, product, cart, checkout, and so on) using the table above. TrueTracked sets this for you, so if you send an event_category field of your own, it is ignored. This keeps the same event filed consistently no matter which of your pages or platforms it came from.
Older event names still work
Earlier versions of these docs used add_to_cart and remove_from_cart. If you send those, they are recorded as product_added_to_cart and product_removed_from_cart. Nothing is lost and you do not need to change existing code, but use the longer names in anything new so your data stays under one name.
Events written by TrueTracked
You may also see attribution_recovered in your data. TrueTracked writes it on its own servers when an order is matched back to an earlier browsing session, so it can restore the campaign that originally drove the sale. It cannot be sent from your website.
Tracking anything else
For actions outside the list above, such as a quiz completion, a brochure download or an outbound click, define your own event name under Settings → Events, then send it from your site.
A note on a few extra names. TrueTracked also accepts product_list_viewed, button_clicked, link_clicked, form_submitted and video_played, but never sends them itself and they cannot be mapped to ad-platform conversions. For engagement tracking, define a custom event instead. Those can be mapped.