You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The [Segment AMP](https://www.ampproject.org/docs/reference/components/amp-analytics#segment){:target="_blank"} 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.
7
7
The component automatically collects default properties and sends a page view.
8
8
9
-
**NOTE:** Since our AMP source sends data directly to our servers, only destinations that support [cloud-mode](/docs/connections/destinations/#connection-modes) are compatible with AMP.
9
+
**NOTE:** Since the AMP source sends data directly to Segment's servers, only destinations that support [cloud-mode](/docs/connections/destinations/#connection-modes) are compatible with AMP.
10
10
11
11
12
12
## Getting started
13
13
14
-
If you're new to [AMP](https://www.ampproject.org){:target="_blank"}, go through their excellent [Quickstart](https://www.ampproject.org/docs/get_started/create_page.html){:target="_blank"}. Once you're setup, follow the steps below to implement Segment.
14
+
If you're new to [AMP](https://www.ampproject.org){:target="_blank"}, go through Amp's excellent [Quickstart](https://www.ampproject.org/docs/get_started/create_page.html){:target="_blank"}. Once you're setup, follow the steps below to implement Segment.
15
15
16
16
### Step 1: Include AMP component
17
17
Before the closing `</head>` tag, include the [`amp-analytics` component](https://www.ampproject.org/docs/reference/components/amp-analytics){:target="_blank"}:
@@ -21,7 +21,7 @@ Before the closing `</head>` tag, include the [`amp-analytics` component](https:
21
21
```
22
22
23
23
### Step 2: Include Segment analytics
24
-
Within you`<body>` tags, include the following Segment analytics snippet:
24
+
Within your`<body>` tags, include the following Segment analytics snippet:
25
25
26
26
```html
27
27
<body>
@@ -185,7 +185,7 @@ In order to enable this feature, you'll need to include a `linkers` object set t
185
185
## Troubleshooting
186
186
187
187
### Can I use client-side Destinations?
188
-
No. All AMP data is sent from Google's servers to our server-side API and subsequently only onto our server-side Destinations. You will only be able to use our server-side destinations and their relevant setting. For example, for Google Analytics, use the "Server-side Tracking ID".
188
+
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".
189
189
190
190
### How do I identify users?
191
191
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){:target="_blank"} this AMP Client ID as an `anonymous_id` and it will be of this format: `amp-REDmCPH4F0QX44kCFomrcA`.
0 commit comments