Littledata integrates with Shopify sites to capture every customer touchpoint, including sales, marketing, customer and product performance data. Our Klaviyo integration works in tandem with our Google Analytics and Segment connections to provide complete data for action and analysis, including audience building, LTV analysis, multi-channel campaign analysis and comparative attribution reports.
Follow this setup guide to ensure that your Klaviyo email campaigns are tracked correctly by Littledata in Google Analytics.
Using Klaviyo for SMS too? Make sure to follow our Klaviyo SMS tracking guide
Using Klaviyo with Google Analytics will ensure that the store sees attribution of Klaviyo campaigns to sales and Customer Lifetime Value (LTV)
Using the Klaviyo destination in Segment, the events Littledata adds can be shared back with Klaviyo.
Klaviyo works alongside Littledata's Shopify to Google Analytics connection, as long as email UTM parameters are set up correctly.
For setup of Klaviyo SMS campaigns see our SMS tracking guide.
UTM parameters are extra data in the link that the user clicks to tell Google Analytics (and Shopify) where the click came from. These parameters are automatically added by Google Ads, but for other platforms (e.g. Facebook or Klaviyo), you will need to add them manually or via the software.
To provide the most reporting flexibility, we recommend having the same UTM parameters across all email flows and campaigns. You can set those up under the Account .. Settings .. UTM tracking menu.
Klaviyo allows dynamic variables to be used in your default UTM tracking settings. To get the most out of your Klaviyo reporting in GA, we recommend using static values for Medium, and dynamic values for Campaign, ID, Customer and Content. We don't recommending `flow` as the Medium, since this this does not map to a default channel in GA.
With static values for Medium (email
), you will be able to see Klaviyo compared against other marketing channels in Google Analytics, and in particular, how Klaviyo campaigns contribute to customer lifetime value and other key metrics for Shopify sales and marketing.
If you don't use Klaviyo for all the emails you send to your customers you might consider using static value of 'Klaviyo' for source
, but since Klaviyo only allows you to add the dynamic List or Segment as a source we think that is most useful.
Here's the full tagging list:
UTM Parameter | Campaign Value | Flow Value |
---|---|---|
Source | List or Segment name | Flow name |
Medium | ||
Source | Campaign name | Flow message name |
Id | Campaign id | Flow id |
Term | Link text or alt text | Link text or alt text |
Customer | External id | External id |
Many Littledata customers create internal spreadsheets to manage UTM naming conventions as well as channel groupings for Google Analytics and run regular QA checks to ensure consistency.
In addition to setting up the UTM Parameter values in your Klaviyo account, you need to enable UTM tracking to ensure that those parameters are applied to all emails in flows and campaigns.
Google Analytics is a powerful reporting tool once you get to know how channel groupings and custom dimensions work. You can analyze your Klaviyo campaign conversions in Google Analytics, alongside other marketing channels with multi-channel attribution.
After you have enabled our recommended settings for UTM tags, you will have access to Klaviyo flow and campaign data in Google Analytics. To see revenue and orders attributed to these campaigns, drill into the Email
channel and add campaign
as a secondary dimension.
If you set up the Flow email name as the utm_campaign
above, then you can look at the contribution of that whole flow to sales. For example, without caring if the user clicked on email 1 or 2 in a 4-email flow, did clicking on any of the emails in that flow -- for example, the 'Browse Abandonment' flow -- result in sales?
Additionally, you can create a segment of users who came via an Instagram campaign, and see to what degree they were influenced by the email sequence.
Klaviyo offers cooperative last touch attribution. This means that they give email and SMS their own configurable attribution window and attribute purchases to the last Klaviyo message a customer interacted with within the attribution window.
By default, Google Analytics uses the last-click attribution model. All credit is assigned to the last channel a user engaged with, and any previous interactions are ignored.
Klaviyo attribution is always more greedy - ignoring contributions from other paid ads or organic visits - so the conversions you'll see in Google Analytics will always be lower.
Under the Advertising > Model Comparison in Google Analytics, you can compare the default email attribution in GA with other attribution models more similar to Klaviyo's dashboard.
You can also look at the Multi-Channel Funnels > Top Conversion Paths report to see where Klaviyo fits into the user journey on your ecommerce site.
Google Analytics data can also be used as a source for other reporting tools, such as Looker Studio and Tableau.
Littledata's Shopify source for Segment automatically sends a rich data set for use with a range of Segment destinations.
Littledata's Segment connection gets all of the post-click events into Segment, and it also sends any event associated with an email address onto Klaviyo as well - providing a richer set of events, without a developer, than Klaviyo's own Shopify event tracking.
For example, you can retarget users in Segment who have purchased a certain value or got certain products to a stage of the checkout - all without writing a line of code.
And by connecting the Klaviyo destination to Littledata's Shopify source for Segment, email opens and clicks will also be gathered.
Read more about how Littledata's Segment connection works and Segment's Klaviyo source documentation.
Email marketing platforms such as Klaviyo, require an email property with any server-side event in order to associate events with a customer (they cannot use an anonymousId
). Littledata adds that email
property whenever an email address is set in the user traits()
object (in device-mode) or from the Shopify customer record (in cloud-mode).
Klaviyo can only accept events linked to a user email, so other anonymous events need to be filtered out or ignored to avoid delivery errors.