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 the Spiffy (upsell, checkout, etc.). Because Spiffy is a single-page application page views operate differently. Anything you rely on
• spiffyPurchase: 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.

spiffyPurchase 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: 'spiffyPurchase',
    'ecommerce': {
        'purchase': {
            'actionField': {
                'id': 'SPIFFY-12345',
                'affiliation': 'Sample Offer',
                'revenue': 100.00,
                'tax': 10.00,
                'shipping': 0.00,
                'coupon': 'SAMPLECODE',
                'currency': 'USD',
            },
            'products': [
                {
                    'name': 'Sample Product',
                    'id': 'P123',
                    'price': 90.00,
                    'quantity': 1,
                }
            ],
        },
    },
}

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 doesnt fully reload on each subsequent page change (hence the speed!) so standard page view events dont fire properly.