Folks,
It is important for creators and publishers to understand how their Web Stories are performing, but it currently takes a fair bit of configuration to get useful analytics setup in a Web Story. To help with this and to standardize common events, we've developed a simple component <amp-story-auto-analytics> that will automatically configure your Web Story with a small curated set of analytics events via the most commonly used analytics provider (Google Analytics).
Detailed documentation for <amp-story-auto-analytics> can be found
here.
- You can use <amp-story-auto-analytics> alongside other custom analytics triggers that you setup via <amp-analytics>
- Analytics needs are likely to evolve as the Story ecosystem mature. <amp-story-auto-analytics> may be extended to include additional analytics triggers in the future (and will work without you needing to modify the Web Story)
As a next step, we are developing example dashboards to help you turn these analytics events into useful insights. The examples will assume the presence of analytics triggers setup by <amp-story-auto-analytics>, so we recommend you standardize on the new component whenever possible.
Feel free to reach out to us on
Github or
Slack via the #amp-story channel to connect and provide feedback.
Cheers,
Varun