DCR Static Google AMP Cloud API - Revision history

NickParrucci: /* Privacy Policy */

2023-02-23T20:57:05Z

← Older revision		Revision as of 20:57, 23 February 2023
Line 104:		Line 104:
	== Privacy Policy ==		== Privacy Policy ==
	Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:		Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:
	~~http~~://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html		https://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html

Admin2: /* Metadata Keys */

2018-03-20T22:45:04Z

Metadata Keys

← Older revision		Revision as of 22:45, 20 March 2018
Line 46:		Line 46:

	The values passed through the Nielsen keys will determine the breakouts you will see in reporting. If you decide not to use custom segments A and B, then you do not need to pass a value in these keys. It is suggested you use the same segments used in non-AMP pages.		The values passed through the Nielsen keys will determine the breakouts you will see in reporting. If you decide not to use custom segments A and B, then you do not need to pass a value in these keys. It is suggested you use the same segments used in non-AMP pages.
			<blockquote>'''Note''': The value for the 'apid' you pass for AMP measurement should not include the 'P' prefix that is otherwise present on other SDK-related implementations</blockquote>

	=== Metadata for Reporting ===		=== Metadata for Reporting ===

Admin3 at 18:52, 19 March 2018

2018-03-19T18:52:04Z

← Older revision		Revision as of 18:52, 19 March 2018
Line 103:		Line 103:
	== Privacy Policy ==		== Privacy Policy ==
	Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:		Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:
	http://~~www~~.~~nielsen~~.com/~~digitalprivacy#choice~~		http://priv-policy.imrworldwide.com/priv/browser/us/en/optout.html

Admin2: /* Specify the Analytics Provider */

2017-07-05T20:08:49Z

Specify the Analytics Provider

← Older revision		Revision as of 20:08, 5 July 2017
Line 19:		Line 19:
	</amp-analytics></syntaxhighlight>		</amp-analytics></syntaxhighlight>

	For more information on the Analytics type, you can refer to the [https://www.ampproject.org/docs/guides/analytics/analytics-vendors\| Analytics vendors] section of Google's AMP Developer Documentation.		For more information on the Analytics type, you can refer to the [https://www.ampproject.org/docs/guides/analytics/analytics-vendors Analytics vendors] section of Google's AMP Developer Documentation.

	== Configure Metadata ==		== Configure Metadata ==

Admin2: /* Example Implementation */

2017-07-05T20:08:26Z

Example Implementation

← Older revision		Revision as of 20:08, 5 July 2017
Line 97:		Line 97:
	</amp-analytics></syntaxhighlight>		</amp-analytics></syntaxhighlight>

	You can find more information about dynamic variables on [https://github.com/ampproject/amphtml/blob/master/spec/amp-var-substitutions.md#page-and-content\| Google's AMP documentation].		You can find more information about dynamic variables on [https://github.com/ampproject/amphtml/blob/master/spec/amp-var-substitutions.md#page-and-content Google's AMP documentation].

	<blockquote>'''Note''': append <code>#development=1</code> at the end of your URL to see AMP debug logs in the console. This can be helpful when troubleshooting</blockquote>		<blockquote>'''Note''': append <code>#development=1</code> at the end of your URL to see AMP debug logs in the console. This can be helpful when troubleshooting</blockquote>

Admin2 at 20:07, 5 July 2017

2017-07-05T20:07:04Z

← Older revision		Revision as of 20:07, 5 July 2017
Line 5:		Line 5:

	== Import AMP Analytics Javascript Library ==		== Import AMP Analytics Javascript Library ==
	~~Please~~ ensure that the following line is included in the <code><head></code> of the webpage:		If you have not already, you will need to import the AMP JS library in the <code><head></code> of your webpage in order to make an AMP page:
			<syntaxhighlight lang="html"><script async src="https://cdn.ampproject.org/v0.js"></script></syntaxhighlight>


			Next, please ensure that the following line is included in the <code><head></code> of the webpage:
	<syntaxhighlight lang="html"><script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script></syntaxhighlight>		<syntaxhighlight lang="html"><script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script></syntaxhighlight>
			<blockquote>'''Note''': AMP pages require all traffic to be using HTTPS, including the webpage itself</blockquote>

	== Specify the Analytics Provider ==		== Specify the Analytics Provider ==
Line 28:		Line 33:
	\|-		\|-
	\| apv \|\| current version of the Nielsen implementation \|\| <code>1.0</code> \|\| ✓		\| apv \|\| current version of the Nielsen implementation \|\| <code>1.0</code> \|\| ✓
			\|-
			\| apn \|\| name of the website \|\| <code>My AMP Website</code> \|\|
	\|-		\|-
	\| section \|\| section of the site to be measured \|\| <code>Entertainment</code> \|\| ✓		\| section \|\| section of the site to be measured \|\| <code>Entertainment</code> \|\| ✓
Line 80:		Line 87:
	"apid": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",		"apid": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
	"apv": "1.0",		"apv": "1.0",
			"apn": "My AMP Website",
	"section": "Entertainment",		"section": "Entertainment",
	"segA": "Music",		"segA": "Music",
Line 88:		Line 96:
	</script>		</script>
	</amp-analytics></syntaxhighlight>		</amp-analytics></syntaxhighlight>

			You can find more information about dynamic variables on [https://github.com/ampproject/amphtml/blob/master/spec/amp-var-substitutions.md#page-and-content\| Google's AMP documentation].

			<blockquote>'''Note''': append <code>#development=1</code> at the end of your URL to see AMP debug logs in the console. This can be helpful when troubleshooting</blockquote>

	== Privacy Policy ==		== Privacy Policy ==
	Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:		Nielsen uses cookies for browser measurement. In order to comply with our privacy restrictions, we ask that you make a link to our Digital Privacy Policy available on your site. You can find our privacy policy here:
	http://www.nielsen.com/digitalprivacy#choice		http://www.nielsen.com/digitalprivacy#choice

Admin2: /* Metadata Keys */

2017-06-27T00:19:42Z

Metadata Keys

← Older revision		Revision as of 00:19, 27 June 2017
Line 35:		Line 35:
	\| segB \|\| custom segment to be used to break out reporting \|\| <code>News</code> \|\|		\| segB \|\| custom segment to be used to break out reporting \|\| <code>News</code> \|\|
	\|-		\|-
	\| segC \|\| Reserved custom segment for Google AMP \|\| <code>'Google AMP'</code> \|\| ✓		\| segC \|\| Reserved custom segment for Google AMP \|\| <code>Google AMP</code> \|\| ✓
	\|}		\|}

Admin2: /* Metadata Keys */

2017-06-27T00:19:27Z

Metadata Keys

← Older revision		Revision as of 00:19, 27 June 2017
Line 35:		Line 35:
	\| segB \|\| custom segment to be used to break out reporting \|\| <code>News</code> \|\|		\| segB \|\| custom segment to be used to break out reporting \|\| <code>News</code> \|\|
	\|-		\|-
	\| segC \|\| Reserved custom segment for Google AMP \|\| <code>'AMP'</code> \|\| ✓		\| segC \|\| Reserved custom segment for Google AMP \|\| <code>'Google AMP'</code> \|\| ✓
	\|}		\|}

Admin2: /* Metadata for Reporting */

2017-06-27T00:19:11Z

Metadata for Reporting

← Older revision		Revision as of 00:19, 27 June 2017
Line 53:		Line 53:
	\|-		\|-
	\| Custom Segment B \|\| segB \|\| available segment for custom reporting. Custom segments will roll into the sub-brand		\| Custom Segment B \|\| segB \|\| available segment for custom reporting. Custom segments will roll into the sub-brand
			\|-
			\| Custom Segment C \|\| segC \|\| Custom segment C is reserved for reporting ‘Google AMP’. The Google AMP custom segment will be available under sub-brand and will include the total metrics for all your AMP pages
	\|}		\|}

Admin2: /* Example Implementation */

2017-06-27T00:18:13Z

Example Implementation

← Older revision		Revision as of 00:18, 27 June 2017
Line 81:		Line 81:
	"segA": "Music",		"segA": "Music",
	"segB": "News",		"segB": "News",
	"segC": "~~Branded_Content~~"		"segC": "Google AMP"
	}		}
	}		}