Once chosen, that’s it - the default marketing analytics tool is Google Analytics. To select the marketing tool for your tracking, simply click the radio dial in the upper left corner of the Google Analytics card. Click 'Integrations' from your navigation bar.įrom here you will see that GaggleAMP can be connected to several different marketing tools for tracking, such as:
Google amp analytics how to#
How to Connect Google Analytics to Your GaggleAMP Accountįrom the Manager Dashboard, navigate to your profile image (or initials) in the upper right-hand corner and select 'Gaggle Settings' from the drop-down. Let’s take a look at how to connect your GaggleAMP account to your Google Analytics. That’s why GaggleAMP can be tracked within Google Analytics, giving you a holistic view of the performance of your campaigns.
Google amp analytics code#
Using Google AMP-linker and Tealium JavaScript Code extensions provide for a more robust tracking implementation in the modern web.Have you ever sat down to do an analysis of your marketing ROI, only to find that your clicks are not attributed correctly or, worse, there was no mechanism to track your engagements in the first place? While in your gut you might feel the campaigns are worth their weight in gold, metrics do not lie. For the specific Google AMP use case, you can use Google and Tealium features together help. While cross-domain tracking has never been an exact science, modern web browsers continue to make this more difficult. Use tealium_visitor_id in EventStream connectors (server-side), or iQ tags (client-side) as a standard visitor identifier for your vendors.įor more information on EventStream or client-side mapping, please visit here. and check to see if this is the first-time visit Look for amp_cid value in URL query string Sort this as the first JavaScript extension scoped to "All Tags - Before Load Rules" Here is a simple JavaScript Code extension to accomplish this:
In this case, we are only using this visitor ID for the case when we have a first-time visitor that is arriving from an AMP HTML page. The next step is to read the value from the URL and use it as your visitor ID. This lets the AMP HTML analytics vendor know that outgoing links to '' should be tagged with an amp_cid value. Enable the AMP-linker by adding a configuration entry. Google's legacy iframe tracking where the website hosts an HTML page that runs TMS inside of it may be better suited for more complex tracking scenarios. This solution does not solve for all use cases (such as visitors moving between non-AMP to AMP pages by clicking back button and doing multiple Google searches). The primary use case is specifically for tracking a visitor that navigates from an AMP page to a non-AMP page (as opposed to the other direction, which is rare). Google Analytics tags automatically picks up this value, so the following describes how to use this ID in a non-Google Analytics use case.įor a data collection use case where Tealium collects event data on your AMP pages (Tealium Collect AMP Analytics integration here), you can leverage the Google-generated CID value as your Tealium visitor ID for the rest of the visitor's engagement with your content. This is referred to as the Google Client Id (CID). To help reduce the impact of this issue, Google AMP provides an AMP-linker tool that enables a visitor ID (generated by Google) on the AMP page to be passed along to the source domain so that you can connect the dots and see a more complete visitor path. And when that visitor clicks a link to eventually arrive on your original website, it becomes difficult to build an accurate visitor path report using traditional web analytics tools. This creates an interesting analytics challenge when your visitors are viewing your content, but are still on.
Google decided with AMP HTML cache to copy the world's content to their own CDNs on, effectively keeping visitors on the domain even after clicking a Google search result.
0 kommentar(er)
