This documentation explains how to implement Webtrekk tracking for Accelerated Mobile Pages (AMP).

The following implementation options are available:


The following table provides an overview of which tracking options are supported. This is useful to show you various possibilities or limitations of the implementation methods that you should consider individually and according to your requirements before implementing the tracking of your AMP pages.


Tracking Optionamp-analyticsamp-iframes
User recognitionIt is not possible to recognize the visit or visitor across pages when he switches between AMP pages and regular pages since different EID cookies are used for the respective pages.It is possible to recognize the visit or visitor across pages when he switches between AMP pages and regular pages since the same EID cookies are used for the respective pages.
New vs. returning user(Fehler)(Haken)
Origin policy (see "Iframe Origin Policy")(Fehler)(Haken)
Video tracking(Haken)(Fehler)
Link tracking(Haken)(Fehler)
Tag Integration(Fehler)(Haken)
AMP variables(Haken)(Fehler)
SSL in your domain(Fehler)(Haken)
Referrer(Haken)(Fehler)
Referrer type(Haken)(Fehler)
Search engine and keyword(Haken)(Fehler)
Campaign(Haken)(Haken)
Browser resolution(Fehler)(Fehler)
Browser/ end device(Haken)(Haken)
Screen(Haken)(Haken)
Recommended by AMP(Haken)(Fehler)