Digital Measurement Onboarding - Revision history

NickParrucci: /* Step 5: Go Live */

2023-04-04T18:40:21Z

Step 5: Go Live

← Older revision		Revision as of 18:40, 4 April 2023
Line 36:		Line 36:

	=== Step 5: Go Live ===		=== Step 5: Go Live ===
	* Ensure your App Store description is updated with a disclaimer informing users of Nielsen measurements.
	* Nielsen will perform post-launch data validations and inform clients of any discrepancies.		* Nielsen will perform post-launch data validations and inform clients of any discrepancies.

ColinBrown at 00:56, 10 September 2020

2020-09-10T00:56:42Z

← Older revision		Revision as of 00:56, 10 September 2020
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}}{{Breadcrumb\|US DCR & DTVR}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

KimBritt: breadcrumb

2017-12-12T15:01:35Z

breadcrumb

← Older revision		Revision as of 15:01, 12 December 2017
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital~~}} {{Breadcrumb\|Digital Audio~~}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

Admin at 15:05, 20 October 2017

2017-10-20T15:05:14Z

← Older revision		Revision as of 15:05, 20 October 2017
Line 7:		Line 7:
	=== Step 1: Client Onboarding ===		=== Step 1: Client Onboarding ===
	* Client contacts Nielsen Client Service representative.		* Client contacts Nielsen Client Service representative.
	* Nielsen Client Team helps the client identify the most suitable product / implementation (DCR / DTVR / DAR etc. and Implementation type.		* Nielsen Client Team helps the client identify the most suitable product / implementation (DCR / DTVR / DAR etc.) and Implementation type.
	* Nielsen Client Team provides the pre-requisites for the integration and the downloads needed.		* Nielsen Client Team provides the pre-requisites for the integration and the downloads needed.

AlexGutierrez: Team review/update

2017-10-02T17:18:49Z

Team review/update

← Older revision		Revision as of 17:18, 2 October 2017
Line 26:		Line 26:
	=== Step 3: Integration ===		=== Step 3: Integration ===
	* Develop the player application and integrate the SDK. Set the appid, the application name (appname), and assign a software version (appversion) to the application.		* Develop the player application and integrate the SDK. Set the appid, the application name (appname), and assign a software version (appversion) to the application.
	** ~~Use the test appid during development, test, and certification.~~		** Nielsen TAM will provide support for any queries, troubleshooting etc. related to SDK.
	** Implementation Engineer (from Nielsen) will provide support for any queries, troubleshooting etc. related to SDK.
	* Once the player application is developed with the SDK integrated, complete the Pre-Certification Checklist provided by Nielsen TAM and submit along with the application for certification.		* Once the player application is developed with the SDK integrated, complete the Pre-Certification Checklist provided by Nielsen TAM and submit along with the application for certification.

	=== Step 4: Certification ===		=== Step 4: Certification ===
	The certification process ~~takes up~~ to ~~three weeks to complete~~.		The certification process can take anywhere from 4 to 10 business days, depending on the app/website complexity and products being implemented.
	* ~~Implementation Engineer~~ performs sanity testing before submitting the application to Nielsen QA team.		* Nielsen TAM performs sanity testing before submitting the application to Nielsen QA team.
	* Nielsen QA team will perform the required testing.		* Nielsen QA team will perform the required testing.
	* Upon QA sign-off, the player application will be certified.		* Upon QA sign-off, the player application will be certified and client will be notified that they are able to launch the app/website to production.

	=== Step 5: Go Live ===		=== Step 5: Go Live ===
	* ~~Upon certification, replace the test <code>appid</code> and <code>sfcode</code> used in the player application~~ with ~~the corresponding production <code>appid</code> and <code>sfcode</code>.~~		* Ensure your App Store description is updated with a disclaimer informing users of Nielsen measurements.
	* Submit the production-ready application to Nielsen ~~TAM for data validation~~.		* Nielsen will perform post-launch data validations and inform clients of any discrepancies.
	* ~~Upon successful data validation from~~ Nielsen ~~TAM, submit the production~~-~~ready application for distribution.~~
	~~For more information, refer to the respective Developer Guide pages – [[iOS SDK API Reference\|iOS]], [[Android SDK API Reference\|Android]] or [[Browser SDK API Reference\|Browser]]~~.

AlexGutierrez at 17:10, 2 October 2017

2017-10-02T17:10:27Z

← Older revision		Revision as of 17:10, 2 October 2017
Line 20:		Line 20:
	* The subsequent page will provide the links to download the SDK and the time-stamped copy of the license agreement (in PDF).		* The subsequent page will provide the links to download the SDK and the time-stamped copy of the license agreement (in PDF).
	* Download the required SDK (iOS / Android / Browser) and Release Notes.		* Download the required SDK (iOS / Android / Browser) and Release Notes.
	* Based on the details received from the client, Nielsen TAM performs the following checks and assigns ~~two appids (~~for ~~Test & Production)~~ and ~~two sfcodes (for Test & Production)~~ to the client.		* Based on the details received from the client, Nielsen TAM performs the following checks and assigns an App ID for each application or website, and an sfcode to the client.
	** Whether all third-party vendors (transcoding, encoding, etc.) listed are certified by Nielsen (if applicable)		** Whether all third-party vendors (transcoding, encoding, etc.) listed are certified by Nielsen (if applicable)
	** Whether the CMS variable mapping for data is correct / valid		** Whether the CMS variable mapping for data is correct / valid

KimBritt: fix bc

2017-09-15T15:46:56Z

fix bc

← Older revision		Revision as of 15:46, 15 September 2017
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} ~~{{Breadcrumb}}~~ {{Breadcrumb\|Digital Audio}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|Digital Audio}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

KimBritt: breadcrumnb

2017-09-15T15:46:31Z

breadcrumnb

← Older revision		Revision as of 15:46, 15 September 2017
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb}} {{Breadcrumb\|Digital Audio}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

KimBritt: genericised breadcrumb to work for digital audio

2017-09-15T15:45:13Z

genericised breadcrumb to work for digital audio

← Older revision		Revision as of 15:45, 15 September 2017
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb~~\|DCR & DTVR~~}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

KimBritt: Removed data elements duplicate info

2017-09-15T15:44:12Z

Removed data elements duplicate info

← Older revision		Revision as of 15:44, 15 September 2017
Line 41:		Line 41:
	* Upon successful data validation from Nielsen TAM, submit the production-ready application for distribution.		* Upon successful data validation from Nielsen TAM, submit the production-ready application for distribution.
	For more information, refer to the respective Developer Guide pages – [[iOS SDK API Reference\|iOS]], [[Android SDK API Reference\|Android]] or [[Browser SDK API Reference\|Browser]].		For more information, refer to the respective Developer Guide pages – [[iOS SDK API Reference\|iOS]], [[Android SDK API Reference\|Android]] or [[Browser SDK API Reference\|Browser]].

	~~=== Data Elements Checklist ===~~
	~~{\| class="wikitable"~~
	\|-
	~~! Data Item !! Description~~
	\|-
	~~\| appid \|\| Your Nielsen Technical Account Manager will provide you with your appID to start testing with. It may require a mapping exercise to ensure content is credited appropriately.~~
	\|-
	~~\| appname \|\| Name of your application~~
	\|-
	\| sfcode \|\| sfcode will be provided by Nielsen and specifies which Nielsen collection facility the app should connect to. Connect to a development server during development and switch to production server once app has been certified by Nielsen.
	\|-
	~~\| dma \|\| If the app is supplying the Nielsen designated market area code (dma), consult Nielsen Technical Account Manager before doing the same.~~
	\|-
	~~\| ccode \|\| If the app is supplying the country code (ccode), consult Nielsen Technical Account Manager before doing the same.~~
	\|-
	~~\| CMS Metadata \|\| Discuss about the unique CMS metadata details with Nielsen Technical Account Manager prior to launch.~~
	\|}