Analytics API

The analytics API can receive events to allow full-funnel analytics and data parity with element and script implementations.

By default, Tipser elements send tracking events to the Analytics API.

API Integrations

You must implement a tracking script if you are implementing with Tipser APIs. Script tracking enables Tipser to provide you with a data dashboard of full-funnel customer actions.

Currently Tipser only supports defined tracking events. We provide both an endpoint for custom pixels and a tracking script that utilizes the API.

Event Tracking Flow

The following example demonstrates how a shopper might interact with your site, and what tracking events they might generate:

1. Shopper loads a page

User action

Event name

The user consents to the data policy.

--

The user rejects the data policy.

--

The cart component renders on the page visited by the user.

view_cart-tab

2. Shopper discovers a product

User action

Event info

Event name

The user views a store component, or part of it.

view_shop

The user views a collection component, or part of it.

view_collection

The user views a product tile component.

If they refresh or leave and then return, another instance of the event is generated.

view_product_tile

3. Shopper researches and assesses the product

User action

Event info

Event name

The user clicks either a standalone product tile or a product tile in a collection.

click_product

The user views the product details page, either as a modal or as an embedded product page.

By default, this event is sent with the click product event, but this is customizable.

view_product_details

The user adds a product to their cart, or increases the quantity of the product in the cart.

Increasing the quantity by any number triggers one event, and a parameter describes the updated quantity.

add_to_cart

The user removes a product from their cart, or decreases the quantity of the product in the cart.

Decreasing the quantity by any number triggers one event, and a parameter describes the updated quantity.

remove_from_cart

4. Shopper decides to purchase

User action

Event info

Event name

The user views the cart page.

view_cart

The user opens the checkout view.

If the user refreshes the page or leaves and returns, another instance of this event is generated.

view_checkout

The user clicks the payment button.

click_payment_button

The user views the order confirmation page.

If the user refreshes the page or leaves and returns, another instance of this event is generated.

purchase_completed

Not all event types are represented in this example. Many events can be mapped onto a timeline, but some cannot.

For a complete list of events, see Supported events quick reference.