Use Case — AMP Analytics Remote Configuration File
This section illustrates a use case that shows how hosted data layer can be used to serve a remote JSON configuration file for an implementation of AMP Analytics.
Learn more about implementing [Tealium for AMP]/platforms/amp/).
Prerequisites
- An AMP site where you want to run certain tags
Serve a remote JSON file to AMP analytics
Use the following steps to serve a remote JSON file for an AMP Analytics configuration:
-
Identify your AMP configuration
The amp-analytics configuration is specific to your vendor or event tracking needs.
For additional information, see the AMP Analytics documentation.
AMP Analytics JSON configuration example:{ "requests": { "pageview": "https://example.com/analytics?url=${canonicalUrl}&title=${title}&acct=${account}" }, "vars": { "account": "A0123456789" }, "triggers": { "trackPageview": { "on": "visible", "request": "pageview" }, "links": { "on": "click", "selector": ".tracked-links-selector", "request": "event" } } }
-
Upload hosted data layer JSON file
Your AMP configuration file can have any name, for example amp.analytics.config.json. In this use case, the data layer ID for the uploaded file is amp.analytics.config. Once the file is uploaded using the Hosted Data Layer API, it will then be available at the following location:https://tags.tiqcdn.com/dle/ACCOUNT/PROFILE/amp.analytics.config.json
-
Tag your AMP page
The new hosted data layer JSON file can be referenced in your AMP pages using theamp-analytics
tag:<amp-analytics config="https://tags.tiqcdn.com/dle/ACCOUNT/PROFILE/amp.analytics.config.json">
This page was last updated: January 7, 2023