# Analytics for AMP **Support:** * Community ✓ * Maintenance ✕ * Flagship ✕ Segment doesn't manage or update community libraries. These libraries are available on GitHub under the MIT License for the open-source community to fork or contribute. The [Segment AMP](https://www.ampproject.org/docs/reference/components/amp-analytics#segment) component makes it easy to send your data to lots of tools without having to learn, test or implement a new AMP component every time. The component automatically collects default properties and sends a page view. **NOTE:** Since the AMP source sends data directly to Segment's servers, only destinations that support [cloud-mode](/docs/segment/connections/destinations/#connection-modes) are compatible with AMP. ## Getting started If you're new to [AMP](https://www.ampproject.org), go through AMP's excellent [Quickstart](https://www.ampproject.org/docs/get_started/create_page.html). Once you're setup, follow the steps below to implement Segment. ### Step 1: Include AMP component Before the closing `` tag, include the [`amp-analytics` component](https://www.ampproject.org/docs/reference/components/amp-analytics): ```js ``` ### Step 2: Include Segment analytics Within your `` tags, include the following Segment analytics snippet: ```html ``` Replace `WRITE_KEY` with the write key you obtain from the AMP Source you've set up within the Segment UI. For sources in [EU workspaces](/docs/segment/guides/regional-segment/), use the following snippet: ```html ``` By default, the snippet will automatically fire a page event which you can read more about [in the Page section of this documentation](/docs/segment/connections/sources/catalog/libraries/mobile/amp/#page). ## Page The Page method lets you record page views on your website, along with your choice of [custom properties](/docs/segment/connections/sources/catalog/libraries/mobile/amp/#getting-started) about the page being viewed. A `page` call is included by default when you include Segment Analytics into your code with the ability to customize the `name` of your page: ```html ``` ## Track The Track method (referred to as `click` in AMP) lets you record any actions your users perform. In order to track these `click` events simply add a trigger with a `selector`, which behaves the same way as [CSS Selectors](https://www.w3schools.com/cssref/css_selectors.asp), which will send that event once the user clicks: ```html ``` ## Properties ### Default properties A few properties are automatically collected with each page view and track call: ```json { "anonymousId": "amp-", "context.locale": "en-US", "context.page.path": "/article", "context.page.url": "http://example.com/article", "context.page.referrer": "referrer", "context.page.title": "My Article", "context.screen.width": 600, "context.screen.height": 800 } ``` ### Custom properties If you would like to collect additional, custom properties, include an `extraUrlParams` object. All properties you'd like to include must follow the format of `properties.`: ```html ``` ### UTM parameters Segment's AMP Source doesn't collect UTM parameters for you but you can define them as a property. An example of this is shown below: ```html ``` ## AMP Linker In order to maintain a merged session for a user navigating from an AMP page served from AMP cache to AMP pages hosted on your domain, you will need to use the [AMP Linker](https://amp.dev/documentation/examples/advertising-analytics/joining_analytics_sessions/) feature. It works by decorating outgoing links from AMP cache with params such as AMP Client ID in a URL parameter and gets written into a first-party cookie. In order to enable this feature, you'll need to include a `linkers` object set to `true` within your configuration. ```text ``` ## Troubleshooting ### Can I use client-side Destinations? No. All AMP data is sent from Google's servers to Segment's server-side API and subsequently only onto Segment's server-side destinations. You'll only be able to use Segment's server-side destinations and their relevant settings. For example, for Google Analytics, use the "Server-side Tracking ID". ### How do I identify users? Because AMP is static, it doesn't provide many options for persistently identifying users. AMP provides a basic cookie mechanism called an AMP Client ID which is a uniquely generated cookie for every unique end user's AMP session. Depending on Google's caching settings, you may receive multiple AMP Client IDs for the same user. Segment will [capture](https://github.com/ampproject/amphtml/blob/b8abe2137f1a50ca6173a258fced64e41a46c763/extensions/amp-analytics/0.1/vendors.js#L1629-L1659) this AMP Client ID as an `anonymous_id` and it will be of this format: `amp-REDmCPH4F0QX44kCFomrcA`. ### How do I manage user identities client-side and server-side? There is no user identity management client-side with AMP, so to join user sessions together you'll need to capture the AMP Client ID on your server-side and join it with your `user_id` in your warehouse. ```text AMP Source: amp_client_id as anonymous_id Server Source: amp_client_id as anonymous_id, user_id as user_id ``` This identity schema will allow you to join down funnel interaction with earlier website browsing behavior. On the server-side, you can grab the `amp_client_id` from the `ajs_anonymous_id` header. ### Why aren't all my IDs prefixed with an 'amp-'? All AMP events won't consistently have an 'amp-' prefixed ID as this is only included in the event that the AMP page is directly visited on your domain. For further details refer to the various `Client ID` scenarios in relation to AMP pages [in Google's docs](https://developers.google.com/analytics/devguides/collection/amp-analytics/client-id) (Segment can only guarantee that if the third scenario happens, the AMP ID will get generated and picked up). See a live [AMP with Segment analytics](https://segment-amp.firebaseapp.com).