How to track Klaviyo flows and email campaigns in Google Analytics
Klaviyo is one of the most popular email marketing platforms for Shopify stores, but the analytics setup is often overlooked. By following a few simples rules, you can ensure accurate Klaviyo data alongside other sales and marketing data in Google Analytics. In this article we cover how to set up Google Analytics tracking for Klaviyo, including best practices for UTM parameters and dynamic variables, and how this tracking works alongside Littledata's Shopify to Google Analytics connection. Why Klaviyo Klaviyo is a popular customer engagement platform used by over 50,000 Shopify merchants. Their focus is on email and SMS automation, and they have been one of the major success stories in the Shopify ecosystem, recently closing a $200 million funding round. Klaviyo's features for Shopify include: Codeless signup forms Pre-built flow templates for quick automation Email campaigns for customers and leads Advanced segmentation and personalization, including product recommendations Many of Littledata's Shopify customers use Klaviyo in one way or another, as do almost all of our Shopify Plus customers. But we've noticed a trend where even the biggest Klaviyo users aren't correctly tracking Klaviyo flows in GA, which ends up blocking data-driven decisions for growth. Read on to see how to fix this. Why Google Analytics The Klaviyo dashboard has useful built-in reporting, but for ecommerce managers focused on more than just email, there are some significant limitations compared with a dedicated analytics platform like Google Analytics (GA). One key limitation is for sales attribution (marketing attribution for online sales). In Klaviyo, any sale that happens after engagement with an email is attributed to that email. This overstates Klaviyo's contribution to sales. For example, if a user first comes from a Facebook Campaign, then clicks on an abandoned cart email from Klaviyo, then goes on to complete a purchase after being retargeted in Facebook, Klaviyo will claim this as owned revenue attributed to that email engagement and credit Facebook with nothing! Another limitation of reporting in Klaviyo's dashboard is that it's hard to see the contribution of an entire email flow to sales, as opposed to the impact of a particular email message in the flow. In Google Analytics (if set up correctly) you can see multi-channel contribution to sales, comparing apples with apples across different marketing channels. What is UTM tracking? UTM parameters are extra data in the link 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. Why does this matter? Because link clicks coming without a UTM tag will typically be treated by GA as "direct" traffic -- in other words, the source of those visits will be unknown. [note]Read Littledata's free guide to common reasons Shopify doesn't match Google Analytics[/note] Recommended settings To provide the most reporting flexibility we recommend having the same standard UTM parameters across all email flows and campaigns. 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 Source and Medium, and dynamic values for Campaign and Content. You can change these defaults in go to Account > Settings > UTM Tracking UTM Parameter Campaign Email Value Flow Email Value Source (utm_source) 'Klaviyo' 'Klaviyo' Medium (utm_medium) 'email' 'email' Campaign (utm_campaign) Campaign name (Campaign id) Flow email name (Flow email id) Content (utm_content) Link text or alt text Link text or alt text [tip]Content is not a default parameter in Klaviyo, so you will need to add that manually (enter `utm_content` as a new parameter).[/tip] With static values for Source and Medium (Klaviyo / email), you will be able to see Klaviyo compared against other marketing channels in GA, and in particular how Klaviyo campaigns contribute to customer lifetime value and other key metrics for Shopify sales and marketing. We do not recommend sticking with Klaviyo's default UTM settings, where Klaviyo flows, for example, are given a dynamic variable that pulls in the name of the flow. You can already see that type of data in the Klaviyo analytics dashboard -- better to use GA for complete marketing analysis. Whichever naming convention you choose, consistency is essential. Many Littledata customers create internal spreadsheets to manage UTM naming conventions and channel groupings in GA, and run regular QA checks to ensure consistency. Note that we have analytics audit checks within the Littledata app, and we now offer analytics training on Plus plans. Enabling UTM parameters 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. The first step is to enable global UTM settings. Go to Account > Settings > UTM Tracking Switch Automatically add UTM parameters to links to ON. Then click Update UTM Tracking Settings. This will ensure that the UTM parameters are added automatically to all emails sent via Klaviyo. Now that you have enabled UTM tracking, you need to make sure that you are using 'account defaults' for UTM tracking in your flows and email campaigns (as opposed to custom tracking). This should already be the case, but it's good to double-check. Disable any custom UTM tracking for flows or campaigns Make sure that the UTM settings for individual flows are set to 'Yes, use account defaults' Make sure that overall email campaign settings are set to use default UTM tracking as well. In your overall campaign settings, select 'Yes, use account defaults' In addition, when creating/editing a campaign, go to Tracking and make sure that 'Include tracking parameters' is ON and 'Customize tracking parameters' is OFF Tracking across all marketing channels The UTM settings above only solve part of the marketing attribution problem: getting the campaign information to the landing page. Commonly this marketing attribution is lost between the landing page and the order completing. You can try to do this manually with an in-house dev team, but Littledata has built a complete ecommerce tracking solution for Shopify and Google Analytics that works automatically. Our connections use a combination of client-side and server-side tracking to make sure that all marketing channels -- including email, paid channels, organic search and referrals -- are linked to sales, along with all touch points in between. We also track returns/refunds, repeat purchases, and subscriptions, so you can understand customer lifetime value on a deeper level. Read about all of the the events Littledata sends automatically. You can use these events for reporting and analysis, and also to build audiences for your Klaviyo campaigns! Reporting on Klaviyo flows in Google Analytics Google Analytics is a powerful reporting tool once you get to know how channel groupings and custom dimensions work. Here's a quick look at how to analyze your Klaviyo data in GA. Looking at campaign conversions in Google Analytics After you have enabled our recommended settings for UTM tags, you will have access to Klaviyo flow and campaign data in GA. You can look at this on its own, but also compared against other channels for engagement and acquisition. To see revenue and orders attributed to these campaigns, drill into the Klaviyo source 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? Going further, you could create a segment of users who came via an Instagram campaign, and see to what degree they were influenced by the email sequence. Will Google Analytics match Klaviyo? How does the data you now have in Google Analytics compare with what you see in your Klaviyo dashboard? Under the Conversions > Multi-Channel Funnels > Model Comparison Tool in GA, you can compare the default email attribution in GA (last non-direct click), with other attribution models more similar to Klaviyo's dashboard. Keep in mind that there is no model for 'all click' attribution, so the numbers you'll see in GA will always be lower. 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. [note]Google Analytics data can also be used as a source for other reporting tools, such as Data Studio and Tableau.[/note] Using Klaviyo with Segment If you are looking to do more with your Shopify and Klaviyo data, consider Segment. Littledata's Shopify source for Segment automatically sends a rich data set for use with a range of Segment destinations. Not only does our Segment connection get all of the post-click events into Segment, but 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. Read more about how Littledata's Segment connection works, and check out the latest updates to our Shopify source for Segment. The connection now supports analytics destinations such as Mixpanel, Vero and Kissmetrics, and email marketing destinations including Klaviyo, Hubspot and Iterable. [subscribe]
What's new in v2 of our Shopify source for Segment
We've a built a loyal following for our Shopify to Segment connection, and this month we've rolled out the next version, v2, with new events and enhanced functionality. As Shopify and Segment both continue to see unprecedented growth, Littledata is here to ensure accurate data at every ecommerce touchpoint. We've seen a surge in DTC and CPG brands on Shopify Plus that rely on Segment to coordinate customer data across marketing, product, and analytics tools. We have continued to develop our Segment integration to fit all of these use cases. [note]If you installed Littledata's Segment connection previously, please contact us to add the v2 events.[/note] About Segment v1 Last year, we worked with Segment to create a robust Shopify source for Segment users. The aim was to make everyone's job easier, from CTOs to ecommerce managers. Littledata's Segment connection v1: Captures all customer touchpoints on your store, both pre and post checkout Sends data to any of Segment’s hundreds of destinations Works seamlessly with Google Analytics Uses a combination of client-side and server-side tracking to capture browsing activity, orders and refunds Sends user fields for calculating customer lifetime value [subscribe] What's new in Segment v2 Since we launched the first Shopify app for Segment in May 2019, we have continued to make improvements based on user feedback and new use cases. The latest version of our Shopify source for Segment offers several updates and enhancements, including support for email marketing around order fulfilment events; tracking for a range of new order and payment events, including POS orders and order cancellations; and alias calls to support additional analytics destinations such as Mixpanel and Kissmetrics. Fulfilment status Many of our customers use Segment events to trigger transactional emails on platforms like Klaviyo and Iterable. One key email that stores want to customize is the 'Your order has shipped' fulfilment email, and so we now trigger a Fulfilment Update event when the fulfilment status of an order changes. This event includes status, tracking_numbers and tracking_urls (where the shipping integration allows), so the transactional email can include actionable details for the end user. These events can also be used in analytics destinations to look at fulfilment trends by product, or see how marketing campaigns around shipping match real-world delivery times. Support for email marketing Email marketing destinations such as Klaviyo, Iterable, and Hubspot, cannot use an anonymous identifier -- so our Segment connection now sends an email property with all events (when it is known), usually from checkout step 2 onwards. Where the email is captured on landing pages (e.g. popup forms) we also send this with the Product Viewed and Product Added events, to make it easier for you to run retargeting and engagement campaigns. Support for Kissmetrics & Mixpanel destinations To support seamless customer tracking in analytics destinations such as Mixpanel, Vero and Kissmetrics, Segment requires an extra alias call. Littledata ensures the pre-checkout anonymousId is added as an alias of the userId (used from checkout step 2 onwards). Learn more in our developer docs. Customer account creation On Shopify, every checkout (even as a guest) creates a customer record. This was already passed on to Segment with an Identify call and a Customer Created event. However, it is useful to know when this customer creates a password and creates a verified account with the store. For example, some brands use this event to trigger welcome emails or offer discounts. With Segment v2, we now send a Customer Enabled event when the user has confirmed their email address and created a Shopify customer account, with verified_email set as true. Payment of draft orders Some stores (especially B2B brands and wholesalers) create draft orders which are later paid. From November 2020, Littledata's Segment connection triggers an Order Completed event whenever these draft orders are paid, linking them back to the user session when they were created. POS orders Previously POS (point-of-sale) orders were excluded from Order Completed, as this polluted the revenue attribution in Google Analytics or other Segment destinations. However, as Shopify POS and other POS orders have become more popular, we now send a separate POS Order Placed event, so you can track the POS orders and choose whether to add them to your web orders. Payment failure After a customer goes through your checkout and completes an order, there is still a chance the payment fails, usually due to fraud checks. A new Payment Failure event allows you to track these failures, and see if they are more associated with particular marketing campaigns, geographies, products, or other factors. Order cancellations If the admin has cancelled an order, perhaps due to the product being unavailable, an Order Cancelled event is now triggered (including the cancel_reason). This is useful for both tracking/analysis and re-engagement campaigns. Product properties Last, but certainly not least, we've expanded the range of product properties sent with every product for better segmentation. Details such as shopify_variant_id, category and brand are sent with all client-side events and most server-side events. For more information, read our developer docs or schedule a demo today with an analytics expert.
Why does shop.app appear as a referral source in Google Analytics?
You may have noticed a new referral source appearing in your Google Analytics, or an increase in sales from the 'Referral' channel. This is a change Shopify made with the launch of the new Shop app, and can be easily fixed. What is Shop.app? SHOP by Shopify is a consumer mobile app, aggregating products and experiences from many Shopify merchants. It is heavily integrated with ShopPay, and so Shopify is now directing one-click checkout traffic to the shop.app domain instead of pay.shopify.com. How would SHOP fit into the user journey? There are two scenarios: 1. Customer is using Shop.app for checkout and payment Example journey: User clicks on Facebook Ad Lands on myshop.myshopify.com?utm_source=facebook Selects a product Logged in, and directed to shop.app for checkout Returns to myshop.myshopify.com for order confirmation In this scenario we should exclude shop.app as a referrer, as the original source of the order is really Facebook 2. End customer is using Shop.app for browsing / product discovery Example journey: User discovers product on shop.app Clicks product link to myshop.myshopify.com?utm_source=shop_app Logged in, and directed to shop.app for checkout Returns to myshop.myshopify.com for order confirmation Here, shop.app is the referrer but it will show up with UTM source How do I see the true source of the referral in Google Analytics? Firstly, you need to exclude shop.app as a referral source. Only in scenario 2 is SHOP genuinely a source of customers, and there the UTM source tag will ensure it appears as a referrer. Littledata's latest tracking script sets this up automatically. The second fix is harder. Unfortunately, at the time of writing, Shopify only sets utm_source=shop_app in the URL query parameters in scenario 2, and Google Analytics won't consider this a referral unless utm_medium is also set. So it appears under the (not set) channel. I've written a patch for our tracking script so that we set utm_medium as referral if only the source is specified, but you can also edit the default channel grouping in GA so that shop_app is grouped as a referral. Thirdly, you want to differentiate orders going through shop.app from the normal Shopify checkout. Littledata's Shopify app does this by translating the order tag shop_app into the transaction affiliation in Google Analytics, so the affiliation is Shopify, Shop App. Conclusion So if you're a Littledata customer: our app has got you covered. And if not there's a few changes you'll need to make in Google Analytics settings to make sure shop.app traffic is treated correctly.
The growing Polish ecommerce market
What does the future of ecommerce look like in Poland? This week, I was honored to be invited onto a panel discussing ‘Riding the Wave of Ecommerce into the Future’ as part of the Ecommerce Trends Summit. Organized by MIT Sloan Management Institute Polska and the ICAN Institute, the summit offered a timely forum about ecommerce for a country rapidly undergoing digital transformation. As with all countries, Poland has seen a massive shift online post-Covid, and predominantly offline companies are scrambling to catch up with online-first retailers. These laggards were behind on use of modern ecommerce platforms like Shopify, but are now catching up fast as they understand the true cost of maintaining an excellent web channel. Since Shopify launched local language versions of their store admin in 2019 it has been a more popular choice for Europe-based companies, and Shopify is now heavily marketing in France, Germany and other countries. Many brands are extending across these markets, and at Littledata we've built multi-currency tracking into our main SaaS product for Shopify merchants. In the Shopify world, each country site is a separate-but-connected "country store" for localized shopping and payments. I’d expect more Polish companies to migrate to Shopify or other cloud solutions (WooCommerce, BigCommerce, etc) in the near future. The larger brands will likely choose Shopify Plus. [note]See the ecommerce trends we've identified during the COVID-19 crisis[/note] The other themes of the panel were more general to retailers globally: stores need smarter marketing, better personalization and a more unique sales proposition as competition heats up. In addition, Amazon.de (Amazon Germany) is just as big a threat to individual brands as elsewhere, but that makes it just as important for stores to own their own customer channel and direct brand experience. And that means running their own online store. Let’s hope Littledata gets to do more business with Polish ecommerce sites soon! [tip]Book Littledata CEO Edward Upton as an expert ecommerce speaker at your next online event[/tip]
What's new for ReCharge tracking
Are you ready for ReCharge v2.3? The latest version of Littledata's popular ReCharge connection is more powerful and extensible than ever. Subscription ecommerce is booming right now, especially for consumables like wine and coffee. Many Shopify stores are even seeing Black Friday-level traffic. But there's also more competition than ever. ShipBob has noted that subscription discounts are especially popular right now, during the seemingly endless days of COVID-19, as a way to bring new subscribers to your brand. This is a major opportunity -- but it also means that there's a lot more competition. Data is more important than ever to understanding your store performance and benchmarking your site, choosing the best marketing channels for your products and targeting the best customers with a higher lifetime value (LTV). Data is more important than ever to understanding your store performance So what exactly can you track with Littledata's ReCharge integration? ReCharge integration for Google Analytics Our ReCharge connection has gone through a lot of updates over the years, based on feedback from our customers, including smaller Shopify merchants, larger DTC brands on Shopify Plus, and our agency partners around the world. Earlier this year, ReCharge v2 saw the addition of subscription lifecycle events. ReCharge v2.3 is now available to all merchants, with the addition of events to track the ReCharge checkout funnel -- and segment by product and marketing channel. So what's new? Clearer segmentation of first time vs recurring orders When you add Littledata's ReCharge connection we now add three Views in Google Analytics to help segment the data: One-time orders and first-time subscriptions - A good way to track initial purchases. We automatically filter out duplicate and recurring orders from this view. All orders - All orders placed on your store, including one-time orders, first-time subscriptions, recurring orders, and prepaid orders. Raw backup - A raw data backup with no filters! This separation enables stores to easily calculate Customer Acquisition Cost (CAC) on one-time orders and first-time subscriptions. Furthermore, for all the subscriptions that started after you installed Littledata’s ReCharge connection, you can group them by subscriber (Shopify customer ID) or by marketing channel or campaign for insightful Return on Investment (ROI) calculations. Read more about how Littledata works with Views and Filters. Checkout funnel events Starting from June 2020, stores on ReCharge v2.3 can see checkout step events to match the checkout events sent from the Shopify checkout. Littledata’s checkout tracking works without the need to add Google Tag Manager or other tracking scripts to the ReCharge checkout, simplifying implementation -- and reducing the risk that 3rd party script interrupt or intercept the sensitive payment details. Excluding prepaid subscriptions Stores generating prepaid subscriptions were seeing duplicate orders when that subscription eventually got processed. In the new One-time orders and first-time subscriptions view, we filter these duplicates out automatically. Custom dimensions for LTV and more Our ReCharge customers benefit from the same user-scope custom dimensions in Google Analytics that we have for all Shopify stores, allowing you to segment and retarget audiences based on data such as their lifetime spend, date of first subscription, or number of subscription payments. Marketing attribution All of these ReCharge v2.3 updates work with our smart tech for accurate marketing attribution. What's the real ROI on your Facebook Ads? Do customers who pick higher-value subscription bundles come from a particular channel? See how Littledata fixes marketing attribution automatically for Shopify stores, with a combination of client-side (browser) and server-side tracking. [tip]Read our reviews to see what ReCharge customers are saying about Littledata! [/tip] ReCharge integration for Segment Our ReCharge integration is now fully compatible with our Shopify to Segment connection, so if you want to send Shopify and ReCharge events to Segment, we've got you covered. This is a seamless way for ReCharge stores to get revenue and customer information into Segment's hundreds of destinations. Headless Shopify tracking for ReCharge ReCharge Connection v2.3 is fully compatible with Littledata's headless tracking solution. Stores using ReCharge's new Checkout API can use Littledata's headless demo to show you how to get the same seamless customer journey from storefront, through checkout to purchasing. Littledata is the only tracking solution compatible with headless ReCharge setups, including those built by our amazing tech partners like Nacelle. ReCharge in-app analytics ReCharge has also launched a powerful in-app analytics feature available to all users. ReCharge launched Enhanced Analytics for Pro customers in 2019 to allow cohort and metric tracking. This is a powerful feature, but it’s different from what Littledata does. The most successful brands are using both tools. ReCharge’s analytics feature offers easy ways to visualize your ReCharge data in the app, while Littledata fixes sales and marketing tracking and sends that data to Segment or Google Analytics. What you can do ReCharge Enhanced Analytics Littledata + Google Analytics Littledata + Segment Look at trends in subscription sign-ups and cancellations ✔ ✔ ✔ Analyze churn rate by cohort or product ✔ ✔ * ✔ * Visualize cohort retention ✔ Fetch last-click source and medium (UTM parameters) from subscription API ✔ Analyze multi-channel marketing contributions to subscription sales ✔ ✔ ✔ Attribute recurring orders back to marketing campaigns ✔ ✔ ✔ Analyze Customer Lifetime Value including non-ReCharge spend ✔ ✔ Track charge failures by any customer attribute ✔ ✔ Track subscription cancellations or upgrades by any customer attribute ✔ ✔ Track customer updates by any customer attribute ✔ ✔ Track usage of the customer portal on our site by any customer attribute ✔ ✔ See how any ReCharge customer event connects to the pre-checkout behaviour of the user ✔ ✔ Look at cancelation rate by marketing channel ✔ ✔ ✔ Trigger transactional emails based on changes to subscriptions ** ✔ Retarget segments of ReCharge audience in common marketing destinations ✔ * Requires additional analysis in a spreadsheet** In Segment destinations such as Iterable How do you get all this? If you're already a Littledata customer, you can update to ReCharge v2 directly in the app (just login and you'll be prompted to upgrade if you haven't already). New to Littledata? We now offer a 30-day free trial on all plans, and setup only take a few minutes. If you are looking for more support, like account management or analytics training, please contact us about enterprise plans.
Updated Facebook Ad Costs to Google Analytics connection
As part of Littledata’s focus on Facebook Ads data this year, we have rebuilt our Facebook Ad Costs connection to be more dynamic and more robust. If you've been asking how to track Facebook Ads or Instagram Ads in Google Analytics -- or doing cost imports manually with Google Sheets and other tools -- your life just got a whole lot easier. Littledata's new and improved Facebook Ad Costs connection automatically imports cost and campaign data from Facebook Ads to Google Analytics, giving Shopify merchants an unbiased view of multi-channel marketing attribution, user journeys and real ROI on PPC campaigns. The Facebook Ads to Google Analytics connection now has added functionality including: Handles up to 100,000 active Facebook Ads, imported daily to Google Analytics Interprets dynamic campaign parameters Imports up to 90 days of campaign history on the first import Works for both Facebook Ads and Instagram Ads Import multiple Facebook Ad accounts to one Google Analytics property Import one Facebook Ad account to one multiple Google Analytics properties Recommends improved campaign URL parameters when none are given Of course the core functionality remains the same: easily pull campaign details and cost data into GA from your FB Ad accounts. Thank you to our customers who gave feedback to help improve the connection -- we couldn't have done it without you. The updated Facebook Ad Costs connection is available on all paid plans at no additional cost. Start a free trial today and start analyzing your campaigns more accurately.
How Google Analytics dropping Service Provider & Network Domain info affects your Shopify tracking
On February 4th, Google Analytics removed two standard dimensions from reporting – Service Provider and Network Domain – and replaced them with the dreaded (not set) label. Although there’s been cries of anguish from some analytics companies, my view is that Google has sound reasons to remove the dimensions – and there are ways around many of the limitations. Shortly after Google added the above alert to the hover tip within the Google Analytics interface, data in reports stopped reporting the information. Moving forward (and unless Google reverses course on this decision in the coming days), you’re going to start seeing (not set) under the Service Provider and Network Domain dimensions: What are Service Provider and Network Domain? Every time a visitor is tracked on your website, Google captures the IP address in order to geolocate the user (generating Country, State and City dimensions). It also does a reverse DNS lookup to see which networks this IP address is linked with. Service Provider is either the ISP (for a consumer) or the corporate network (for a business internet user). Network Domain is the main domain by which the traffic was routed (e.g. Verizon, Amazon AWS etc.) So why did Google drop them? There’s been no official announcement from Google, but it’s likely to be a combination of three factors. CCPA Storing of any California consumer’s network details is a violation of the California Consumer Protection Act (CCPA). This is much more specific than previous regulations, and as a California-headquarted company, Google wants to stay safely within the law. [tip]Here's everything Shopify merchants need to know about CCPA compliance[/tip] Fingerprinting Even if the Service Provider itself is not identifiable to any individual, it may well be used to generate a unique fingerprint for an individual user, in combination with other dimensions in Google Analytics (browser version, operating system, screen size, pages visited, etc.). Fingerprinting is user identification by covert means, and as such Google also wants to clamp down on in. Lack of usage In ten years of advising high-growth businesses on Google Analytics setup, I've never seen a good use for these reports. Google tracks what are the most common reports used, and apparently they were already flagged for deprecation based on lack of usage. How the change affects your Shopify tracking Some analytics companies (and agencies) are worried about this change for a few reasons : Reason 1: Service Provider and Network Domain dimensions helped filter out spam and bot traffic, which meant less legwork for those doing the reporting. It was easier to sniff out bounce rates that looked too high (or low) to be "real". Take the screenshot below — which Service Provider do you think is probably legitimate and which one is probably a bot/spam? In short, most analytics companies would say before this change, it was easy to uncover bots/spam, and now it's not. Reason 2: Some larger stores used Server Provider and Network Domain dimensions as a quick & easy way to filter out internal traffic from monthly reports. And unfortunately, this change has killed these dimensions' ability to filter. Reason 3: Companies such as Leadfeeder and Leadberry used the Network Domain, plus a database of which companies and people used that domain, to offer a list of sales leads who visited your site. They can mostly work around the limitations by getting their clients to push another tracking script on the site, and looking up IP address themselves — which is OK, providing your website visitors are aware you are doing this in your terms and conditions. In other words, if you're filtering your GA views by network provider, it's possible you'll see internal traffic in your reporting this month. And it might not be obvious, since it's mixed in with all of your site traffic. That is, unless you look at the GA data with better tracking. How can you work around this? For those that really need the lost dimensions there are two solutions: Use Google Tag Manager and an IP lookup service to pass network onto Google Analytics as a custom dimension. Use the recently launched ipmeta.io service to do this.* What now? For some stores using Google Analytics, this sudden change will go unnoticed and won't really impact reporting. For stores that rely on these dimensions to filter out bots/spam and internal traffic for more accurate reporting, the loss of these dimensions will have somewhat of a negative impact. Of course, we'll continue to monitor these changes (and any other surprises that Google may have in store). Don't pay too much attention to the initial outcry — every change has a solution. Littledata users can rest easy — with our Google Analytics app for Shopify, your tracking won't be impacted by these dimensions. You'll continue to see accurate data for better reporting. 🚀 *The current version of ipmeta.io is free and will remain free. The premium version will add more custom dimensions with data on the company behind the visit (if its not an ISP or spider). For example, adding dimensions such as industry codes, company size, revenue, etc. In comparison to similar services, ipmeta.io will be much (about 10x) more affordable to cater to the SMB segment.
What's new in our Shopify apps for Google Analytics and Segment
Littledata is always improving. Over the last 6 months, we’ve worked on numerous features to enhance the accuracy and availability of our ecommerce data analysis for Shopify merchants. Littledata's smart connections make it easy to get accurate data in Google Analytics or Segment. The changes below affect both of our Shopify apps (Segment and Google Analytics for Shopify), marking the biggest major update to our Shopify tracking script and server-side tracking since we released V8 last year. [tip]Check out our release notes for regular updates![/tip] Attribution for email marketing signups In order to provide enhanced email attribution, we've linked 'customer created' and 'customer updated' events back to the original source. Stores building a customer email list can now analyze where those email signups originally came from. By linking customer creation or update events on Shopify’s servers to the original campaign or referrer to the store, Littledata customers can now accurately track the source of email signups. Merchants can now also segment these signup events by whether or not the customer opted into marketing. Checkout steps Tracking checkout steps is essential for ecommerce analytics, but Shopify's native tracking is incomplete and inaccurate. Littledata's Shopify connections solve checkout tracking issues automatically. With recent updates, we’ve made the tracking of checkout steps even more reliable, coping with situations where a user is already logged in, or abandons the cart and then returns later. [note]Did you know by sending the data to Google Analytics, you can easily track your Shopify payments gateway during checkout?[/note] With the help of the full Enhanced Ecommerce specification, you can: track exactly which products follow in each step calculate the value of opportunities to improve each step [subscribe] ReCharge connection, recharged As subscription ecommerce sites continue to scale, they need even more detailed data about the user journey, especially lifecycle events. [tip]Do you trust your subscription tracking in Shopify? Learn how to get accurate tracking for repeat orders[/tip] With our new ReCharge v2 connection, subscription stores can now track the full subscription lifecycle including: subscription updates cancellations failed payments product edits customer profile / information edits [note]See the full slate of ecommerce events you can now track with ReCharge v2[/note] Geolocation of server-side events Stores need accurate information on the location of their customers to retarget campaigns around top-performing regions or cities. The extra events above, plus all the standard order data, are sent from our servers in Virginia, US. But, of course, in your analytics, you want to see them linked to the customers' real location. We now have a belt-and-braces solution for correctly geolocating customer events, passing on the browser's IP address where known, or else sending the shipping address (default customer address) to Google Analytics as a 'Geographical Criteria ID'. CartHook and Bold Cashier We've always supported other checkouts for Shopify, as we know some stores need flexibility with payment, upsell and recurring billing options. And for the most popular checkout solutions, we're always looking at ways to provide advanced tracking automatically. So in the past 6 months Littledata has launched more robust integrations with CartHook and Bold Cashier. New Google Optimize connection Google Optimize is a powerful A/B testing and personalization platform used within and beyond ecommerce. [note]Connect your Shopify store to Google Optimize to test your product pages, store content and messaging with 100% accuracy.[/note] Now, we have an out-of-the-box setup for Shopify, including an anti-flicker snippet. And coming soon... In Q1 2020, we're working on connections for Iterable's email marketing platform, plus a more consistent way of handling Segment's anonymous ID for stores which don't use Google Analytics. Is there something you're eager to see in Littledata? We're always happy to hear feature suggestions — get in touch with our team today!
Subscribe to Littledata news
Insights from the experts in ecommerce analytics
Try the top-rated Google Analytics app for Shopify stores
Get a 30-day free trial of Littledata for Google Analytics or Segment