Engineering Client Portal - User contributions [en]

SEI Ad Audit Ping

2026-04-27T17:47:01Z

SurabhiGupta:

{{Breadcrumb|}} {{Breadcrumb|Digital}} {{Breadcrumb|Digital Ad Ratings}} {{CurrentBreadcrumb}}
[[Category:Digital]]

= Introduction =

The Nielsen Server-to-Server (S2S) solution needs audit pings for audience validation. The audit pings are https requests that are fired at least once per session. It primarily contains URL parameters with a randomly generated Session Identifier, Integration Identifier, and a timestamp that is matched to the server-side traffic.

The end user device makes a request to Nielsen Collections servers at least once per Session. Sessions are defined as continuous interaction with the application, as defined by the Publisher. The Audit pings are executed ideally at the beginning of the Session or upon first ad exposure. Audit Pings may optionally fire more often, for example: fired upon each ad exposure if preferred.

Audit Pings are intended to be as light-weight, generic as possible, and contain no personal identifiers, campaign information, or advertisement metadata.

== Ping Structure ==
Requests should be executed with the following convention structure:
<nowiki>https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&+</nowiki>'''[query parameters]'''
(Please note that this URL may require updates in response to changes in the market.)

The Audit Ping will carry all parameters in the matrix later in this document. Under normal operating circumstances, the Nielsen collection system will return the following response codes:

* 302: A redirect to another Nielsen domain, used for the purpose of generating a URL compatible with Nielsen streaming meters
* 200: The ping was successfully received, inspect traffic to ensure no CORS error

== Audit Ping Implementation Details ==

* SessionID is ideally generated when the application is initiated, optionally upon first ad exposure
* Audit Pings should be executed at least every time a SessionID is created
* It is permissible for Audit Pings to fire more frequently than once per session (for example, upon each ad exposure, or page change, etc.)
* It is permissible for SessionIDs to change within a session, so long as the Audit Ping is fired again ensuring that the ImpID parameter reflects the same new SessionID
* For security reasons, downstream servers reject cross-origin HTTP requests with preflight. To ensure that audit ping requests are accepted, allowable Content-Types like "text/plain" in simple GET requests ensure that preflight requests are not invoked, which is the preferred behavior.

== Relay Audit Ping (Server to Server) ==
The relay audit ping is an alternative to the standard audit ping, which is more privacy friendly, since it does not require direct calls from the user client device to the Nielsen backend. It also allows partners to mask XFF (X-Forwarded-For) /24 (IPv4) or /48 (IPv6) as well as control HTTP Client Hints. This can however limit Nielsen’s ability to enrich the collected data using geo resolution, device classification and GIVT, if the partner chooses to severely limit or filter completely the original client IP and User Agent. As a result the implementation of relay audit ping may require additional characteristics to be sent via the exposure logs in order to compensate for the loss of signal. For more details please refer to the Viewing Spec.
The relay audit ping is implemented using a two legged approach described below. The additional pairing ping becomes necessary, since relayed audit ping cannot be used to redirect the user client for panel matching purposes.

# Pairing Ping. This is an end-user-device-initiated ping with partner-owned root domain and SessionID included in subdomain. It is used for panel matching. Nielsen meters will be trained to recognize the unique domain format. Example: <nowiki>https://2576459933726989.darnuid</nowiki>.[publisher-domain].com
# Relay Audit Ping. This is an end-user-device-initiated audit ping relayed by the partner's backend (via proxy server) with furnished URL parameters outlined below. Example: <nowiki>https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&intid=fgrclqou0dzb1u4jq2jecoyvza&apid=FCGG4EC1-E0f4-B465-Ef40-070AAD3173A1&sessionid=2576459933726989&product=dtvr&createtm=1643858542</nowiki>

[[File:Audit Ping.png|center]]

== Query Parameters ==
{| class="wikitable"
!Parameter
!Description
!Mandatory?
!Specified By
!Format Example
|-
|intid
|Single ID assigned per integration for all audit pings across platforms
|Yes
|Nielsen
|a9ddf15ea054ea415718767ea6
|-
|apid
|Server App ID assigned by Nielsen
|Only required for content measurement
|Nielsen
|Alphanumeric application identifier assigned by Nielsen by platform
|-
|sessionid
|Unique id generated when video player is instantiated
|Yes
|Client
|Format: alphanumeric, Example: 16 char guid
|-
|product
|Indicates which product audit ping content corresponds to
|Yes
|Client
|Format: alphanumeric, Example: “dar”, “dcr”, “dtvr”
|-
|createtm
|Time the ping was fired
|Yes
|Client
|Format: UnixTime “1643858542”
|}
'''Generic Ping Format:'''
<nowiki>https://audit.imrworldwide.com/cgi-bin/gn?prd=audit</nowiki>&intid=<Integration id>&apid=<App id>&sessionid=<Session Id>&product=<dar>&createtm=<>

'''Audit Ping Example:'''
<nowiki>https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&intid=a9ddf15ea054ea415718767ea6&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&product=dar&createtm=1643858542</nowiki>

== Nielsen One Ads Impression Implementation Details ==
A new Impression ID parameter specified as "&impid" that exactly matches the SessionID included in the Audit Pings.

'''Example Nielsen One Ads Ping:'''
<nowiki>https://secure-us.imrworldwide.com/cgi-bin/m?ci=us-201234h&cg=0</nowiki>[...]&impid=2576459933726989&rnd=164403011

Supported IP and UA attributes and their order of precedence:
{| class="wikitable"
|'''IP Address Attributes'''
|'''UA String Attributes'''
|-
|Query String -> &clientip
|HTTP Header -> X-Device-User-Agent
|-
|Query String -> &ip
|HTTP Header -> User-Agent
|-
|HTTP Header -> X-Forwarded-For (left most ip)
|
|-
|TCP connection socket
|
|}

SEI Ad Audit Ping

2026-04-27T17:37:11Z

SurabhiGupta: /* Ping Structure */

Digital Measurement Content Audit Beacon

2026-04-27T17:35:19Z

SurabhiGupta:

{{Breadcrumb|}} {{Breadcrumb|Digital}} {{Breadcrumb|US DCR & DTVR }} {{CurrentBreadcrumb}}

The Nielsen server-to-server solution requires audit pings for the purpose of validating audience reach and video viewing duration; one start and one end for each video stream. Pings originate from the end-user device to Nielsen Collections servers. End pings execute upon cessation of playback.
==Ping Structure==
Ping is executed with following convention:

<code>https://'''[to_be_provided]'''.imrworldwide.com/cgi-bin/gn?prd=audit&+'''[query parameters]'''</code>

The Start Audit Ping carries all parameters in the table below. The End Audit Ping carries a subset of the parameters in the matrix below as denoted in the mandatory column.

Under normal operating circumstances, the audit ping server returns the following codes:
*Audit ping servers reject cross-origin HTTP requests with preflight. To ensure that audit ping requests are accepted, allowable Content-Types like "text/plain" in simple GET requests ensure that preflight requests are not invoked
*200: Ping successfully received, inspect traffic to ensure no CORS errors
*302: A redirect to another Nielsen domain, used for the purpose of generating a URL compatible with Nielsen streaming meters
=Session & Stream=
#Sessions
##Optionally, a new Session ID may be created when a new player is created
##If more than one video player exists within the same App (e.g. picture in picture) a different Session ID is required for each
#Streams
##New Stream ID is generated for each new video stream.
##If stream playback continues after 24 hours, then a new Stream ID should be created and a new Audit ping should be executed (Session ID may remain)
##Stream ID remains the same independent of fast-forward, rewind, pause, events assuming the asset remains the same
##If playback is suspended for greater than 30mins (paused or otherwise suspended), a new Stream ID should be assigned upon return
#Audit Pings
##Audit pings should be fired at the beginning and end of a stream. These will be referred to as the Audit Start Ping and the Audit End Ping

== Relay Audit Ping (Server to Server) ==
The relay audit ping is an alternative to the standard audit ping, which is more privacy friendly, since it does not require direct calls from the user client device to the Nielsen backend. It also allows partners to mask XFF (X-Forwarded-For) /24 (IPv4) or /48 (IPv6) as well as control HTTP Client Hints. This can however limit Nielsen’s ability to enrich the collected data using geo resolution, device classification and GIVT, if the partner chooses to severely limit or filter completely the original client IP and User Agent. As a result the implementation of relay audit ping may require additional characteristics to be sent via the exposure logs in order to compensate for the loss of signal. For more details please refer to the Viewing Spec.
The relay audit ping is implemented using a two legged approach described below. The additional pairing ping becomes necessary, since relayed audit ping cannot be used to redirect the user client for panel matching purposes.

# Pairing Ping. This is an end-user-device-initiated ping with partner-owned root domain and SessionID included in subdomain. It is used for panel matching. Nielsen meters will be trained to recognize the unique domain format. Example: <nowiki>https://2576459933726989.darnuid</nowiki>.[publisher-domain].com
# Relay Audit Ping. This is an end-user-device-initiated audit ping relayed by the partner's backend (via proxy server) with furnished URL parameters outlined below. Example: <nowiki>https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&intid=fgrclqou0dzb1u4jq2jecoyvza&apid=FCGG4EC1-E0f4-B465-Ef40-070AAD3173A1&sessionid=2576459933726989&product=dtvr&createtm=1643858542</nowiki>

[[File:Audit Ping.png|center]]

=Query Parameters=
{| class="wikitable"
!'''Parameter'''
!'''Description'''
!'''Required'''
!'''Specified'''
!'''Format / Example'''
|-
|apid
|Server App ID assigned by Nielsen
|Yes
|Nielsen
|Example: <code>A487421B-XXXX-YYYY-8343-E3BBB66E44F2</code>
|-
|sessionid
|Unique, client generated value that represents the start of a user session. “Session” is defined as continuous (flexible) interaction with an application that may span multiple streams.
|Yes
|Client
|Format: alphanumeric Example: Random GUID: <code>ce6c1c95-de3e-431e-b11e-77…</code>
|-
|streamid
|ID for every new instance of exposure to a different asset
|Yes
|Client
|Example: Random GUID: <code>ce6c1c95-de3e-431e-b11e-77…</code>
|-
|pingtype
|Indicator for ping type: "start" or "end" audit ping
|Yes
|Client
|Format: integer,
*<code>1</code> = Start Stream
*<code>0</code> = Start Session
*<code>3</code> = End Stream
*<code>2</code> = End Session
|-
|product
|Indicates which product audit ping corresponds to
|Yes
|Client
|Format: alphanumeric, Example: <code>dcr</code>, <code>dtvr</code>, <code>dar</code>
|-
|uoo
|User opt out flag for demographic measurement
|Yes, if devid/HHID provided
|Client
|Format: integer
*<code>0</code> = not opt-out
*<code>1</code> = opt-out
|-
|devid
|Mobile Ad ID (IDFA, ADID), Connected Device ID
|Optional, or in S2S file
|Client
|Only for Start Mobile Ping. User for demo assignment. Required, if no other interoperable id match exists for the integration
Example:<code>A487421B-XXXX-YYYY-8343-E3BBB66E44F2</code>
|-
|<s>hhid</s>
|<s>House Hold ID. Used as a primary match key to external data sources.</s>
|<s>Optional, or in S2S file.</s>
|<s>Client</s>
|<code><s>B0EOFEDgD</s></code>
|-
|createtm
|Time ping is initiated
|Yes
|Client
|Format: Unix timestamp in 32-bit unsigned int in seconds Example: <code>1577858505</code>
|-
|intid
|Single ID assigned per integration for all audit pings across platforms
|Yes
|Nielsen
|Example:
xpgclqou0dzb1ugjq2jgcoyvza
|}'''Audit Ping Start Example:'''

<code>[https://secure-audit.imrworldwide.com/cgi-bin/gn?prd=audit&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&streamid=3679422587354472&pingtype=0&product=ctv&uoo=1&createtm=1577858505&devid=4AB6FCE2-2848-4FA8-9BE3-46E206206AB https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&intid=fgrclqou0dzb1u4jq2jecoyvza&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&streamid=3679422587354472&pingtype=0&product=ctv&uoo=1&createtm=1577858505&devid=4AB6FCE2-2848-4FA8-9BE3-46E206206AB]</code>

'''Audit Ping End Example:'''

<code>[https://secure-audit.imrworldwide.com/cgi-bin/gn?prd=audit&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&streamid=3679422587354472&pingtype=2&product=ctv&uoo=1&createtm=1577859637 https://audit.imrworldwide.com/cgi-bin/gn?prd=audit&intid=fgrclqou0dzb1u4jq2jecoyvza'''intid=fgrclqou0dzb1u4jq2jecoyvza'''&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&streamid=3679422587354472&pingtype=2&produ]</code>

<code>[https://secure-audit.imrworldwide.com/cgi-bin/gn?prd=audit&apid=FC984EC1-E044-B465-E040-070AAD3173A1&sessionid=2576459933726989&streamid=3679422587354472&pingtype=2&product=ctv&uoo=1&createtm=1577859637 ct=ctv&uoo=1&createtm=1577859637]</code>

File:Audit Ping.png

2026-04-27T14:46:02Z

SurabhiGupta:

Architecture of relayed audit ping

Digital Measurement Content Audit Beacon

2026-02-05T15:11:53Z

SurabhiGupta: striked hhid as it is not present in code

Digital Measurement Content Audit Beacon

2026-02-05T15:07:56Z

SurabhiGupta: