Skip to content
GROWTH DEPT.MTA
DocsCustom events

Guides

Custom events

A custom event counts a conversion that is not an order, such as a visit to a sign-up page or an add to cart, and credits it to the ads and channels that led to it, the way orders are credited. Set them up under Settings > Custom Events; a brand can have up to 25.

What an event counts#

Each custom event counts one of the events the pixel already collects, so nothing new needs to be added to your pages:

EventCollected when
Page viewA page of the store loads.
Product viewA product page loads.
Add to cartA product is added to the cart.
Checkout startedCheckout begins.

A visitor counts at most once per custom event per day, in the brand's time zone, so reloading a thank-you page is one conversion. If the pixel is not installed yet, see Shopify connection.

Limiting it to pages#

By default an event counts on any page. A path rule limits it to pages whose path matches:

  • Any page: every page.
  • Path is: the path is exactly the value, such as /pages/thank-you.
  • Path contains: the path contains the value anywhere.
  • Path starts with: the path begins with the value, such as /collections/.

How conversions are credited#

Each conversion is credited with the same attribution models, touches and lookback as an order, and each custom event is a metric of its own, listed under Custom events in Customize table.

  • Accrual performance dates the credit on the touch, and a window keeps only conversions that came within that many days of it, so the 7-day figure includes the 1-day figure.
  • Cash snapshot dates the credit on the conversion, with the lifetime window.

See Attribution models for the models, windows and accounting modes.

When a change shows#

Creating, changing or deleting a custom event takes effect in the next processing run. A changed event is counted again over the brand's whole lookback, so its history follows the new definition rather than mixing the old and the new.

Questions about the API: support@growthdept.ai.