Add managing user state docs #7433
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Suggest that you change terminology in image from "google.com" to something more generic and use google.com as example. |
The contents of this doc are discussed in much more detail in the new amp-managing-user-stage.md doc
|
ping @bpaduch @cramforce |
ghost
approved these changes
Feb 9, 2017
| ### Display contexts for AMP pages | ||
|
|
||
| You can think of AMP as a portable content format that enables content to be loaded fast anywhere. AMP documents can be displayed via three noteworthy contexts: | ||
|
|
There was a problem hiding this comment.
This table would look better if you specified width, the old-fashioned HTML way (sorry, no markdown).
There was a problem hiding this comment.
converted to tables
spec/amp-managing-user-state.md
Outdated
|
|
||
| **Case #1: Initial visit.** Upon first landing on the non-AMP page, there will be no cookie. If you checked for the cookie before one was set, you’d see no values set in the cookie corresponding to the `uid`: | ||
|
|
||
| ``` |
There was a problem hiding this comment.
For all your code blocks, please specify a language - html, hs, or text
Example:
```text
blah,blah
...
| @@ -0,0 +1,444 @@ | |||
| # Managing non-authenticated user state with AMP | |||
|
|
|||
spec/amp-managing-user-state.md
Outdated
|
|
||
| ### Task 3: Process analytics pings from pages on the publisher origin | ||
|
|
||
| Because of the setup performed in Tasks 1 and 2, when someone accesses the AMP version (from any context) or the non-AMP version on the publisher origin the analytics ping will use the same identifier. By following the guidance in Task 2 to choose a Client ID "scope" that was the same name as the name of the cookie you used in Task 1, AMP reuses the same cookie. |
There was a problem hiding this comment.
Any reference to specific Tasks, please link to them - helps the user
spec/amp-managing-user-state.md
Outdated
|
|
||
| This is illustrated in the table below: | ||
|
|
||
| | An analytics ping coming from... | ... looks like this: | |
There was a problem hiding this comment.
This table would look better if you used HTML and specified width so that the 1st column isn't so squished, and hard to read.
|
Addressed all comments from @bpaduch |
torch2424
pushed a commit
to torch2424/amphtml
that referenced
this pull request
Feb 14, 2017
* Add managing user state docs * Adding image resources * Delete placeholder for image folder * Add amp-managing-user-state.md * Delete cross-origin-tracking.md The contents of this doc are discussed in much more detail in the new amp-managing-user-stage.md doc * Change tables to HMTL, specify language of code blocks * Fix orig_user_id and user_id that didn't get updated * Added TOC; added some more code block type indicators * Add links for tasks
mrjoro
pushed a commit
to mrjoro/amphtml
that referenced
this pull request
Apr 28, 2017
* Add managing user state docs * Adding image resources * Delete placeholder for image folder * Add amp-managing-user-state.md * Delete cross-origin-tracking.md The contents of this doc are discussed in much more detail in the new amp-managing-user-stage.md doc * Change tables to HMTL, specify language of code blocks * Fix orig_user_id and user_id that didn't get updated * Added TOC; added some more code block type indicators * Add links for tasks
Closed
mauricionr
reviewed
Jul 12, 2017
|
|
||
| Through usage of features that require Client ID, AMP will do the “under the hood” work to generate and store client ID values and surface them to the features that require them. One of the principal features that can use AMP’s Client ID is [amp-analytics](https://www.ampproject.org/docs/reference/components/amp-analytics), which happens to be exactly what we’ll need to implement our analytics use case example. | ||
|
|
||
| On AMP pages, construct an analytics-analytics ping containing the Client ID: |
There was a problem hiding this comment.
@rudygalfi what is analytics-analytics?
There was a problem hiding this comment.
It should be amp-analytics. Thanks - I'll fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will introduce a guide on managing non-authenticated user state in AMP.
Major sections are: