This page short URL: 7x

As with everything on your site, it is very important to track how your Accelerated mobile pages are used, especially for something as new as AMP. The specification allows for using multiple analytics services providers, but currently only Google Analytics, Google Tag Manager and Facebook Pixel support is automatically handled by weeblrAMP.

Adding other analytics providers is perfectly possible either using a filter or template overrides.

Analytics Type

weeblrAMP AMP analytics provider

To get started, you only need to enable Google Analytics/tag manager or Facebook Pixel, and provide a valid corresponding id for each analytics tool you plan on using.

Tick the checkboxes in front of the analytics provider(s) you want to use. AMP allows multiple providers to be used simultaneously.

If using Google Tag Manager, the only configuration to do is enter your GTM ID in the Web Property ID field. Any further configuration is made in GTM itself.

Note that you must create and use an AMP-specific GTM container: you cannot simply re-use your current GTM id for AMP Pages. Please see below for more details.

If using Facebook Pixel, you also only need your pixel id from Facebook.

Client ID API

weeblrAMP implements the Client ID API, which makes sure AMP pages are tracked properly when displayed on Google Cache and on your site.

Using Google Analytics

weeblrAMP implements fully the Client ID API on AMP pages. But you must also include some code on the standard version of your pages. You have to modify the output of your analytics snippet, as described in Google documentation:

ga('create', 'UA-XXXXX-Y', 'auto', {'useAmpClientId': true});

Consult with the provider of your Analytics plugin, or theme developer to find out how to modify your site Analytics snippet.

Using Google Tag Manager

Please refer to the specific paragraph at the bottom of this page.

Analytics settings

weeblrAMP AMP analytics provider

Checking this box will prevent any analytics data to be recorded until the user has clicked on a User notification display that you must create and enable (it's really simple!).

Checking this box will add the data-credentials="include" attribute to the amp-analytics tag. Please refer to the amp-analytics tag documentation for more details.

Tracked events

weeblrAMP lets you take advantage of the advanced event tracking features of amp-analytics. They are described on this page of Google Analytics documentation, and the amp-analytics components reference documentation can be found here.

Event tracking is a rather advanced topic, but can provide great information about the behavior of your visitors. For instance you can learn about which and when buttons are clicked, or whether visitors scroll down to see your content.

This section only apply to using Google Analytics or Facebook Pixel. If you use Google Tag manager, all event tracking is done inside Google Tag Manager itself, as usual.

You set up event tracking by adding configuration lines to the Events tracked parameter (see screenshot above). You can add event tracking to all pages, or only to some pages. In fact, you can have different tracking for different pages. The syntax is as follow:

  • one event tracking definition per line
  • each line starts with a page selection rule followed by one of the supported events (list below)
  • after the event name, appropriate parameters are listed, each separated by a | character
  • if you start a line with a ; character, the line is considered a comment and not taken into account. Help remembering what each line is for, or temporarily enable/disable lines
  • if you put a - as the only character on the first line of the input field, then the entire event tracking is disabled. Useful for testing for instance

As we use the | character to separate each parameter on a line, please be sure to not use any | in them, particularly in your descriptive labels.

Event: click

This event lets you track clicks on pretty much any HTML element, as long as you can select it with a CSS selector (CSS class combination, id). As per Google Analytics documentation, you need to specify the following information

* | click | css_selector | eventCategory | eventAction [|eventLabel] [|eventValue]
  • *: page selector. All pages are selected with the * symbol. See paragraph below about page selection
  • click: event type
  • css_selector: a CSS selector to an HTML element that exist on your page such as #call-to-action-1 or #header. You can specify multiple selector on the same line, separating them with commas:,a.prev,#go-to-first
  • eventCategory: an arbitrary category for the event
  • eventAction: an arbitrary action name for the event
  • eventLabel: not required - an arbitrary label for the event
  • eventValue: not required - must be an integer number, will be added up to a total at each event

Here are 2 examples:

* | click | #header | Sample category | header-click
* | click | #header2 | Sample category 2 | header-click | Summer sales | 42

The first line will cause clicks on the HTML element with an id of #header to be tracked by analytics, under the Sample category category and be identified as a header-click action. The second line will do the same for a different element and category, but will add a label of Summer sales and increment the counter associated with this event by 42. As both lines start with *, these event tracking instructions will run on all pages of the site.

Again, be sure to actually check the specific Google Analytics documentation page for details about those settings.

Event: scroll

Likewise, the scroll event can be tracked by adding a line defined as follow:

* | scroll | verticalBoundaries | horizontalBoundaries | eventCategory | eventAction [| eventLabel] [| eventValue] 
  • *: page selector. All pages are selected with the * symbol. See paragraph below about page selection
  • scroll: event type
  • verticalBoundaries: a list of vertical scroll positions at which you want the event to be fired. Each position is considered a percentage, and should be an integer number between 0 and 100. Use [] if you do not want to track this scroll direction.

    The list must be separated by commas and surrounded by square brackets: [25,50,90] or [42]

  • horizontalBoundaries: a list of horizontal positions to fire the event, with the same syntax. Use [] if you do not want to track this scroll direction.
  • eventCategory: an arbitrary category for the event
  • eventAction: an arbitrary action name for the event
  • eventLabel: not required - an arbitrary label for the event
  • eventValue: not required - must be an integer number, will be added up to a total at each event

Here are 2 examples:

* | scroll | [50] | [] | Blog scrolls | 50% V scroll 
* | scroll | [50,90] | [90] | Blog scrolls | 50% and 90% V scroll or 90% H scroll

The first line will cause vertical scrolling to 50% to fire an event. The second line will cause the same at 50% and 90% vertical position, plus another event fired if the page is scrolled horizontally to 90%.

You can find details about the scroll event on the amp-analytics page.

We currently only support the feature set of Google Analytics. The following amp-analytics triggers are not supported: timer, visible and hidden

Page selection

In all examples above, we have seen each event tracking specification started with *. This is the page selection rule, which decides on which page of the site the given event tracking will happen or not. This page selection rule lets you fairly easily specify individual pages or groups of pages. The rules you enter are based on the URL of the page.

Basic elements

You specify a rule by listing entire URLs, or part of URLs:

  • Use only the part of URL after the domain name: /growers is OK, is NOT OK.
  • Use the * symbol to indicate any string of characters: /growers/* matches any URL that starts with /growers/, regardless of what's after it
  • Use the ? symbol to indicate any single character: /growers/2?-happy-orange-orchard matches any URL with any letter in lieu of the ?
  • *: selects all pages of the site
  • /growers/: exactly /grovers/. Selects only the /growers/ URL (it needs to have the trailing slash). It won't match /Growers for instance, as this has a capital G at the beginning, and no slash at the end
  • /?rowers/: / followed by any single character followed by rowers/. This will select /growers/, /Growers/ but also /prowers/ or /2rowers/. It won't select /XXrowers/, because there are 2 X, while we allow only one varying character
  • /growers/*: /growers/ followed by any string of characters. Will select, for instance: /growers/, /growers/23-happy-orange-orchard, /growers/something.html
  • /growers/23-happy-*-orchard: /growers/23-happy- followed by any string followed by -orchard. Will select, for instance: /growers/23-happy-orange-orchard, /growers/23-happy-red-orchard, /growers/23-happy--orchard but not /growers/23-happy-orange-orchard-llc, because it ends with -orchard-llc instead of -orchard
  • */growers: any URL ending exactly with /growers. Will select, for instance: /growers, something/growers but not something/growers/ (because there is a trailing slash) or something/growers.html (because of the .html at the end)
  • *hello*: any URL that has hello somewhere. Will select for instance: i-say-hello-world, but also hello-world or i-say-hello
  • *hello*goodbye: any URL that has hello somewhere, followed by any string of characters and then ends with goodbye. Will select for instance: i-say-hello-world-i-say-goodbye, hello-world-goodbye, i-say-hello-you-say-goodbye. It will not select i-say-goodbye-you-say-hello

Google Tag Manager settings

If you select Google Tag manager as your analytics method, then weeblrAMP will display only the following options:

weeblrAMP AMP Google Tag manager settings

All other setup is done through Google Tag manager itself.

As mentioned earlier though, you must use an AMP-specific Google Tag Manager container. You cannot simply re-use your existing GTM container ID, as standard GTM containers are not AMP-compatible.

Container type

When creating your AMP GTM container in Google Tag Manager admin page, be sure to select the AMP container type:

weeblrAMP AMP Google Tag manager configuration

Client ID API

As already mentioned, wbAMP implements the Client ID API. When using Google Tag Manager, you also need to enable this feature in GTM itself.

Important: these steps must be taken on your standard tag container, not on the AMP container.

  1. Navigate to Tag Configuration > Fields to Set.
  2. Set useAmpClientId to true.
  3. Save the new tag configuration.

Please refer to the linked Google documentation for up to date information on how to do this.