Digital Measurement Onboarding: Difference between revisions

From Engineering Client Portal

m (Admin moved page Onboarding to Digital Measurement Onboarding without leaving a redirect)
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Breadcrumb|}} {{Breadcrumb|Digital}}{{Breadcrumb|US DCR & DTVR}} {{CurrentBreadcrumb}}
[[Category:Digital]]
== Steps to Release a Nielsen-enabled Application ==
== Steps to Release a Nielsen-enabled Application ==
The procedure to deploy a Nielsen-enabled player application into production comprises of five steps, as mentioned below.
The procedure to deploy a Nielsen-enabled player application into production comprises of five steps, as mentioned below.


=== 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.


Line 18: 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
Line 24: 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>.
* Nielsen will perform post-launch data validations and inform clients of any discrepancies.
* Submit the production-ready application to Nielsen TAM for data validation.
* 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]].
 
=== 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.
|}

Latest revision as of 18:40, 4 April 2023

Engineering Portal / Digital/ US DCR & DTVR / Digital Measurement Onboarding

Steps to Release a Nielsen-enabled Application

The procedure to deploy a Nielsen-enabled player application into production comprises of five steps, as mentioned below.

Step 1: Client Onboarding

  • 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 provides the pre-requisites for the integration and the downloads needed.

Step 2: Submit details and Download SDK

Following are the steps that the client should follow to download the required SDK package.

  • Visit the Downloads section of this site.
  • Click the Download SDK button.
  • Fill-in the basic user details and select the Nielsen Service that you subscribe to.
  • Submit the details to view the License Agreement for downloading the SDK.
  • The details are submitted to Nielsen Technical Account Manager (Nielsen TAM)
  • Read through the terms of agreement. Click I ACCEPT THE TERMS OF AGREEMENT button to accept the terms.
  • 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.
  • 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 the CMS variable mapping for data is correct / valid

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.
    • Nielsen TAM 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.

Step 4: Certification

The certification process can take anywhere from 4 to 10 business days, depending on the app/website complexity and products being implemented.

  • Nielsen TAM performs sanity testing before submitting the application to Nielsen QA team.
  • Nielsen QA team will perform the required testing.
  • 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

  • Nielsen will perform post-launch data validations and inform clients of any discrepancies.
Retrieved from "https://engineeringportal.nielsen.com/w/index.php?title=Digital_Measurement_Onboarding&oldid=6191"