In GA Property Settings, click on Data Streams(BETA). Select the correct web data stream, and copy the ‘MEASUREMENT ID’
Step 2.Add Google Analytics: App+Web Configuration Tag in GTM
Navigate to the existing GTM container.
Add a new tag and choose tag type ‘Google Analytics: App+Web Configuration’. Enter Measurement ID saved from Step 1. Make sure ‘Send a page view event when this configuration loads’ is selected if you want to have page_view events automatically collected. Add ‘All Pages’ trigger to this configuration tag and save changes.
Step 3. Add Google Analytics: App+Web Event Tag in GTM
Add a new tag with type ‘Google Analytics: App+Web Event’. In the field ‘Configuration Tag’, select the configuration tag created in Step 2.
Enter event name and add event parameters if needed. Note event and parameter names are case sensitive, can only contain alphanumeric characters and underscores (“_”). Make sure you do not include space in event or parameter names.
In your GA Property Settings, click on Data Streams(BETA). Select the correct web data stream, and click on the edit icon of ‘Enhanced measurement’. On the right-hand panel, you can see all the enhanced measurement settings. Make sure the toggle for ‘Site search’ is on. Click on the cog – ‘Show advanced settings’, update ‘Search Term Query Parameter’ and ‘Additional Query Parameters’ fields and save changes.
In Google Analytics: App + Web Event tag, add a new parameter and insert parameter name as ‘debug_mode’ and value as GTM inbuilt variable {{Debug Mode}}. Save changes and click ‘Preview’. GTM will show a banner across the top of the workspace overview page to indicate that Preview Mode is active.
Once Preview Mode is enabled, navigate to the site where the container is implemented. Refresh the page if needed. Now you can view events in real-time in GA App+ Web DebugView panel.
Google Analytics App+Web session_start event is triggered as soon as your app goes into the foreground (App) or App+Web GTM/gtag configuration tag loads (Web).
Like you, the team at DRD had been in isolation. To maintain our sanity while the world is bunkering down against the CoVid-19 enemy, we have been researching, reading voraciously, and digging up dirt on this new App+Web property. DRD strongly believes in a sharing-is-caring culture, so we hope to answer some who, what why, how questions!
This post, the first of many, is to give you an overview of what this App+Web (AW) is all about. However, before you get too excited and jump on the AW flyaway gravy train, you must know that AW is still in beta. This means that not all desired features are available while some are still in the midst of being improved.
App+Web was launched in July 2019 and is essentially the ‘new Google Analytics’. Despite its name, you don’t need to have an App. Righto, first things first – you have to create a new property in your existing Google Analytics Account. If you already have gtag.js or Google Tag Manager on your site, you can utilize the existing infrastructure to collect data for App+Web. Further, with a few configurations and tags in place, you can start to gather information in your new App+Web Property.
The Concept
It’s undeniable that our noses are more buried in our phones these days. The FOMO, YOLO, FOBO mentality has driven our society to have insatiable appetites to consume more of everything such as news, gossip and latest fashion trends or games. As such, the app industry has exploded with more app downloads year on year.
Given this growing trend of mobile and single-page apps, perhaps the notion of pageviews and sessions have lost some of its relevance compared to when the sessions were first conceptualized yonks ago. In addition to the fact that some apps may not have pageviews, perhaps event-scope concept is a better way of tracking and measuring some interactions. Oh, what about websites, you asked? As website users do click,scroll, play and toggle on websites, a generalized concept will allow web interactions to be measured directly as well.
The idea behind this new AW property is to enable the analyst to combine both app and web interactions and event measurements into consolidated reports within the one platform. Previously, you would have a set of reports for web users and another set for App users. This new development would mean that we can now explore user-centric analytics across various digital platforms efficiently and subsequently as a tool to divulge valuable insights.
App+Web and Firebase
If you are familiar with Firebase, you will be pleased to know that App+Web (AW) works in the same way as AW is built on the Firebase or Google Analytics for Firebase data schema. Because of this, many of the special hit types and data types in traditional websites are more defined by events, parameters and user properties in AW.
Similarities and Differences
While the terms of pageviews, sessions, events are there, the application of the terms are different due to the event-scoped data model. In traditional GA, all hits (pageviews and events) sit within a session and all sessions are then related back to a single user.
Traditional Google Analytics Session-Based Model
For AW, the building blocks of what a user is like, is via the events (which also includes pageviews!) that happen while the user is navigating through the app or website. You will also noticed that the unique events metrics have disappeared and this is because unique events is a session-based metric.
App+Web Event-Based Model
There are also new concepts such as User properties, Parameters and Engaged Sessions to grasp. To put it loosely, User Properties are like user-scoped custom dimensions while parameters are attached to events to provide more context to that particular event. Do note that there are some limitations surrounding the naming of user properties.
The idea behind this is to simplify yet allowing for increased flexibility in data collection and to open a plethora of new tracking opportunities. Therefore, the reports will be different, they will be new and will require a learning curve. Remember the days when you are learning to ride the bike? It was uncomfortable and you probably badly scraped your knees a good few times, but once you’ve mastered the bike-riding.. freedom never tasted so good! Keep that happy thought in your head while gritting through the AW learning pain.
There are also challenges that come without sessions, such as Goals and setting what was previously session-based goals. Segments in AW is bit different to what you are used to in Universal Analytics but you’ll be pleased to know that you can still apply sequential segments to your data.
Views and Data Stream
You will also notice that there are no Views and in its place, there are Data Streams, which essentially are your data sources like iOS, Android or Web. Given that there are no Views in AW, we do face the ‘how-do-I-filter-data’ challenge. In time, we hope to give you more information on how to overcome this issue.
App+Web Interface and Reports
The interface is not that much different to the current GA set up. On the left hand panel, there are the Users, Demographics, Behaviour, Conversions and Event as its own heading (instead of being nested under Behaviour). Within each report, you have various widgets presenting different things such as active users, source/medium, page title and campaign overview.
Within the same left hand menu pane, you will also find the Analysis Hub. This hub enables you to gain deeper insights as well as form different visualisations by simply dragging and dropping metrics and dimensions. We have Exploration, Segment Overlap, Funnel Analysis,User Explorer and Path Analysis reports to content ourselves with.
Do I or Do I Not?
You are probably on Universal Analytics at the moment, and if your website was around before 2013, you were probably on Classic Analytics. When Universal Analytics (UA) came into play, a lot of development was focussed on UA and the Classic cousin was left out. Following the crumbs of the cookie trail (pardon the pun!), we are of the belief that App+Web is likely to take over GA (UA) and will be made the primary analytics tool.
Given all the above, we think it would be a good idea to have both AW and UA running in tandem, to familiarize yourself with AW while the development kinks are ironed out. After all, additional knowledge never hurts!
User properties are attributes that can be used to describe segments of your user base, such as geographic location etc, pretty much like dimensions, but user-scoped. There are currently a number of default user properties such as age, app version/store, country, device brand/category/model, first open time, gender, interests, language, new/established and OS version. You can also add up to 25 uniquely named user properties per App+Web property.
One thing you must understand about user properties, is that you need to preset them, and register or create them in the interface before you can use them.
There is also a limit on the number of user properties of 25 registered user properties per App+Web property, and a limit of 100 registered user properties per App+ Web 360 property.
