Category : Analytics Setup
Important update to Remarketing with Google Analytics
Shine a light on ‘dark’ Facebook traffic
If Facebook is a major channel for your marketing, whether sponsored posts or normal, then you’re underestimating the visits and sales it brings. The problem is that Facebook doesn’t play nicely with Google Analytics, so some of the traffic from Facebook mobile app comes as a DIRECT visit. That’s right – if a Facebook user clicks on your post on their native mobile app they won’t always appear as a Facebook social referral. This traffic is ‘dark Facebook’ traffic: it is from Facebook, but you just can’t see it. Since around 40% of Facebook activity is on a mobile app, that means the Facebook traffic you see could be up to 40% less than the total. Facebook hasn’t shown much interest in fixing the issue (Twitter fixed it, so it is possible), so you need to fix this in your own Google Analytics account. Here are three approaches: 1. Basic: use campaign tagging The simplest way to fix this, for your own posts or sponsored links on Facebook, is to attach UTM campaign tags to every link. Google provides a simple URL builder to help. The essential tags to add are “utm_source=facebook.com” and “utm_medium=referral”. This will override the ‘direct’ channel and put all clicks on that links into the Facebook referral bucket. Beyond that, you can add useful tags like “utm_campaign=events_page” so you can see how many click through from your Facebook events specifically. 2. Moderate: use a custom segment to see traffic What if much of your traffic is from enthusiastic brand advocates, sharing your pages or articles with their friends? You can’t expect them to all use an URL builder. But you can make a simple assumption that most users on a mobile device are not going to type in a long URL into their browser address bar. So if the user comes from a mobile device, and isn’t visiting your homepage (or a short URL you deliberately post), then they are probably coming from a mobile app. If your website is consumer facing, then the high probability is that that mobile app is Facebook. So we can create a custom segment in GA for traffic which (a) comes from a mobile device (b) does not have a referrer or campaign (i.e. direct) (c) does not land on the homepage To start you need to create a segment where source contains 'facebook'. Then add the 'Direct mobile, not to homepage' segment: Next, you can create a custom report to show sessions by hour: You should see a strong correlation, which on the two web properties I tested on resulted in doubling the traffic I had attributed to Facebook. 3. Advanced: attribute micro spikes to Facebook Caveat: you’ll need a large volume of traffic – in excess of 100 visits from Facebook a day – to try this at home The final trick has been proved to work at The Guardian newspaper for Facebook traffic to news articles. Most Facebook activity is very transitory – active users click on a trending newsfeed item, but it quickly fades in interest. So what you could do, using the Google Analytics API, is look for the ‘micro spikes’ in referrals that come from Facebook on a minute-by-minute basis, and then look at the direct mobile visits which came at the same time, and add these direct spikes to the total Facebook traffic. I've played around with this and it's difficult to get right, due to the sampling Google applies, but I did manage to spot spikes over around 5 minutes that had a strong correlation with the underlying direct mobile traffic. Could these approaches work for your site? I'm interested to hear. (Chart: Dark Social Dominates Online Sharing | Statista) Get Social! Follow us on LinkedIn, Twitter, and Facebook and keep up-to-date with our Google Analytics insights.
6 reasons Facebook ads don’t match the data you see in Google Analytics
The referral exclusion list: what it is and how to update it?
The referral exclusion list is only available for properties using Universal Analytics ... so please make the jump and take advantage of the benefits! Let's find out how excluding referral traffic affects your data and how you can correct some of the wrong attributions of sales. By default, a referral automatically triggers a new session. When you exclude a referral source, traffic that arrives to your site from the excluded domain doesn’t trigger a new session. Because each referral triggers a new session, excluding referrals (or not excluding referrals) affects how sessions are calculated in your account. The same interaction can be counted as either one or two sessions, based on how you treat referrals. For example, a user on my-site.com goes to your-site.com and then returns to my-site.com. If you do not exclude your-site.com as a referring domain, two sessions are counted, one for each arrival at my-site.com. If, however, you exclude referrals from your-site.com, the second arrival to my-site.com does not trigger a new session, and only one session is counted. Common uses for referral exclusions list in Google Analytics: Third-party payment processors Cross-subdomain tracking If you add example.com to the list of referral exclusions, traffic from the domain example.com and the subdomain another.example.com are excluded. Traffic from another-example.com is not excluded. Only traffic from the domain entered in the referral exclusions list and any subdomains are excluded. Traffic from domains that only have substring matches are not excluded. How to add domains in the referral exclusion list: Sign in to your Gooogle Analytics account. Click admin in the menu bar at the top of any page. In the account column, use the drop-down to select the Google Analytics account that contains the property you want to work with. In the property column, use the drop-down to select a property. Click tracking info. Click referral exclusion list. To add a domain, click +add referral exclusion. Enter the domain name. Click create to save. The referral exclusion list used contains matching. For example, if you enter example.com, then traffic from sales.example.com is also excluded (because the domain name contains example.com). Need help with these steps? Get in touch with one of our experts and we'd be happy to assist you! Get Social! Follow us on LinkedIn, Twitter, and Facebook and keep up-to-date with our Google Analytics insights.
4 common pitfalls of running conversion rate experiments from Microsoft
5 tips to avoid a metrics meltdown when upgrading to Universal Analytics
Universal Analytics promises some juicy benefits over the previous standard analytics. But having upgraded 6 different high traffic sites there are some pitfalls to be aware of. Firstly, why would you want to upgrade your tracking script? More reliable tracking of page visitors - i.e. fewer visits untracked More customisation to exclude certain referrers or search terms Better tools for tracking across multiple domains and tracking users across different devices Track usage across your apps for the same web property Ability to send up to 20 custom dimensions instead of the previous limit of only 5 custom variables If you want to avoid any interruption of service when you upgrade, why not book a quick consultation with us to check if Universal Analytics will work in your case. But before you start you should take note of the following. 1. Different tracking = overall visits change If your boss is used to seeing dependable weekly / monthly numbers, they may query why the number of visits has changed. Universal Analytics is likely to track c. 2% more visits than previously (partly due to different referral tracking - see below), but it could be higher depending on your mix of traffic. PRO TIP: Set up a new web property (a different tracking code) for Universal Analytics and run the old and new trackers alongside each other for a month. Then you can see how the reports differ before sharing with managers. Once this testing period is over you'll need to upgrade the original tracking code to Universal Analytics to you keep all your historic data. 2. Different tracking of referrals Previously, if Bob clicked on a link in Twitter to your site, reads, goes back to Twitter, and within 30 minutes clicks on a different link to your site - that would be counted as one visit and the 2nd referral source would be ignored. In Universal Analytics, when Bob clicks on the 2nd link he is tracked as a second visit, and 2nd referral source is stored. This may be more accurate for marketing tracking, but if Bob then buys a product from you, going via a secure payment gateway hosted on another domain (e.g. paypal.com) then the return from the payment gateway will be counted as a new visit. All your payment goals or ecommerce tracking will be attributed to a referral from 'paypal.com'. This will ruin your attribution of a sale to the correct marketing channel or campaign! PRO TIP: You need to add all of the payment gateways (or other third party sites a user may visit during the payment process) to the 'Referral Exclusion List'. You can find this under the Admin > Property > Tracking codes menu: 3. Tracking across domains If you use the same tracking code across different domains (e.g. mysite.co.uk and mysite.com or mysite.de) then you will need to change the standard tracking script slightly. By default the tracking script you copy from Google Analytics contains a line like: ga('create', 'UA-XXXXXXX-1', 'mysite.com');. This will only track pages that strictly end with 'mysite.com'. PRO TIP: It's much safer to change the tracker to set that cookie domain automatically. The equivalent for the site above would be ga('create', 'UA-XXXXXXX-1', 'auto');. The 3rd argument of the function is replaced with 'auto'. 4. Incompatibility with custom variables Only relevant if you send custom data already Custom variables are only supported historically in Universal analytics. That means you will need to change any scripts that send custom data to the new custom dimension format to keep data flowing. Read the developer documentation for more. PRO TIP: You'll need to set the custom dimension names in the admin panel before the custom data can be sent from the pages. You can also only check that the custom dimensions are being sent correctly by creating a new custom report for each dimension. 5. User tracking limitations We wouldn't recommend implementing the new user ID feature just now, as it has some major limitations compared with storing the GA client ID. You need to create a separate view to see the logged-in-user data, which makes reporting pageviews a whole lot more complex. Visits a user made to your site BEFORE signing up are not tracked with that user - which means you can't track the marketing sources by user PRO TIP: See our user tracking alternative. Got more tips on to setting up Universal Analytics? Please share them with us in the comments, or get in touch if you want more advice on how to upgrade! Get Social! Follow us on LinkedIn, Twitter, and Facebook and keep up-to-date with our Google Analytics insights.
Widget Tracking with Google Analytics
I was asked recently about the best way to track a widget, loaded in an iframe, on a third-party site with Google Analytics. The difficulty is that many browsers now block 3rd party cookies (those set by a different domain to the one in the browser address bar) – and this applies to a Google Analytics cookie for widgets as much as to adverts. The best solution seems to be to use local storage on the browser (also called HTML5 Storage) to store a persistent identifier for Analytics and bypass the need to set a cookie – but then you have to manually create a clientID to send to Google Analytics. See the approach used by ShootItLive. However, as their comment on line 41 says, this is not a complete solution - because there are lots of browsers beyond Safari which block third party cookies. I would take the opposite approach and check if the browser supports local storage, and only revert to trying to set a cookie if it does not. Local storage is now possible on 90% of browsers in use and the browsers with worst 3rd party cookie support (Firefox and Safari) luckily have the longest support for local storage. As a final note, I would set up the tracking on a different Google Analytics property to your main site, so that pageviews of widgets are not confused with pageviews of your main site. To do list: Build a script to create a valid clientID for each new visitor Call ga('create) function, setting 'storage' : 'none', and getting the 'clientID' from local storage (or created from new) Send a pageview (or event) for every time the widget is loaded. Since the widget page is likely to be the same every time it is embedded, you might want to store the document referrer (the parent page URL) instead Need help with the details? Get in touch with our team of experts and we'd be happy to help! Get Social! Follow us on LinkedIn, Twitter, and Facebook and keep up-to-date with our Google Analytics insights.
How to link Adwords and Google Analytics
If you are running an AdWords campaign you must have a Google Analytics account. We will show you how to link these two accounts so you can unleash the full reporting potential of both platforms. 1. Why should you link Analytics and AdWords? When you link Google Analytics and AdWords, you can: See ad and site performance data in the AdWords reports in Google Analytics. Import Google Analytics goals and ecommerce transactions directly into your AdWords account. Import valuable Analytics metrics—such as bounce rate, avg. session duration, and pages/session—into your AdWords account. Take advantage of enhanced remarketing capabilities. Get richer data in the Google Analytics multi-channel funnels reports. Use your Google Analytics data to enhance your AdWords experience. 2. How to link Google Analytics and AdWords The linking wizard makes it easy to link your AdWords account(s) to multiple views of your Google Analytics property. If you have multiple Google Analytics properties and want to link each of them to your AdWords account(s), just complete the linking wizard for each property. Sign into your Google Analytics account at www.google.com/analytics. Note: You can also quickly open Google Analytics from within your AdWords account. Click the tools tab, select analytics, and then follow the rest of these instructions. Click the admin tab at the top of the page. In the account column, select the analytics account that contains the property you want to link to one or more of your AdWords accounts. In the property column, select the analytics property you want to link, and click AdWords Linking. Use one of the following options to select the AdWords accounts you want to link with your analytics property. Select the checkbox next to any AdWords accounts you want to link with your analytics property. If you have an AdWords manager (MCC) account, select the checkbox next to the manager account to link it (and all of its child accounts) with your analytics property. If you want to link only a few managed accounts, expand the manager account by clicking the arrow next to it. Then, select the checkbox next to each of the managed AdWords accounts that you want to link. Or, click all linkable to select all of managed AdWords accounts under that MCC. You can then deselect individual accounts, and the other accounts will stay selected. Click the continue button. In the link configuration section, enter a link group title to identify your group of linked AdWords accounts. Note: Most users will only need one link group. We recommend creating multiple link groups only if you have multiple AdWords accounts and want data to flow in different ways between these accounts and your analytics property. For example, you should create multiple link groups if you need to either link different AdWords accounts to different views of the same Google Analytics property or enable auto-tagging for only some of your AdWords accounts. Select the Google Analytics views in which you want the AdWords data to be available. If you've already enabled auto-tagging in your AdWords account, skip to the next step. The account linking process will enable auto-tagging for all of your linked AdWords accounts. Click advanced settings only if you need to manually tag your AdWords links. Click the link accounts button. Congratulations! Your accounts are now linked. If you opted to keep auto-tagging turned on (recommended), Google Analytics will automatically start associating your AdWords data with customer clicks. For a deeper view and debugging you should also read the Google Analytics guide. Have any questions on setting this up? Get in touch and we'd be happy to help! Get Social! Follow us on LinkedIn, Twitter, and Facebook and keep up-to-date with our Google Analytics insights.
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