When you integrate Google Tag Manager (GTM) with Spiffy we’ll handle passing checkout events and purchase data events to GTM’s Data Layer

Events Tracked

We currently track the following events:

• spiffyPageView: Triggered when a user views a page on Spiffy (upsell, checkout, etc.).
• begin_checkout: Triggered when a user loads the checkout process.
• purchase: Triggered when a user completes a purchase on Spiffy and includes full ecommerce data. This is sent at the END of the checkout flow to ensure things like upsells get included.

Event Data

These events can be accessed via debug mode or within your analytics account.

purchase Event

The purchase event is triggered when a user completes a purchase through one of your checkouts. Here is an example of the data that’s sent:

{
  event: 'purchase',
  ecommerce: {
    transaction_id: 'SPIFFY-12345',
    value: 100.00,            // order total, including tax
    currency: 'USD',
    tax: 10.00,
    shipping: 0,
    coupon: 'SAMPLECODE',
    affiliation: 'Sample Offer',
    items: [
      {
        item_id: 'option:5879',
        item_name: 'Sample Product',
        price: 90.00,         // excludes tax
        quantity: 1,
        index: 0
      }
    ]
  }
});

spiffyPageView Event

The spiffyPageView event contains standard page view data. You can trigger based of this event although we recommend setting up page view triggers off of history_change events in GTM.

Spiffy is a single-page application that doesn’t fully reload on each subsequent page change (hence the speed!) so standard page view events don’t fire properly.

begin_checkout Event

The begin_checkout event is triggered with a user loads the checkout. This event sends data about the checkout page in its default state.