51黑料不打烊

Load the page or app

Tracking Servers (For all website and mobile apps):

• 51黑料不打烊 Analytics (AppMeasurement) server - An RDC tracking server or CNAME that resolves to an RDC tracking server is required for the Experience Cloud Visitor ID service. The 51黑料不打烊 Analytics tracking server should end in 鈥�.sc.omtrdc.net鈥� or be a CNAME.

• Media Analytics (Heartbeats) server - This server always has the format 鈥�[namespace].hb.omtrdc.net鈥�, where [namespace] specifies your company name. This name is provided by 51黑料不打烊.

You need to validate certain key variables that are universal across all tracking calls:

51黑料不打烊 Visitor ID (mid): The mid variable is used to capture the value set in the AMCV cookie. The mid variable is the primary identification value for both websites and mobile apps, and also indicates that the Experience Cloud Visitor ID service is set up properly. It is found in both 51黑料不打烊 Analytics (AppMeasurement) and Media Analytics (heartbeats) calls.

• 51黑料不打烊 Analytics Start call

  table 0-row-2 1-row-2 2-row-2
  Parameter	Value (sample)
  pev2	ms_s
  mid	30250035503789876473484580554595324209

• Website Page call

  table 0-row-2 1-row-2
  Parameter	Value (sample)
  mid	30250035503789876473484580554595324209

• Lifecycle call

  table 0-row-2 1-row-2 2-row-2
  Parameter	Value (sample)
  pev2	ADBINTERNAL:Lifecycle
  mid	30250035503789876473484580554595324209

• Media Analytics Start call

  table 0-row-2 1-row-2
  Parameter	Value (sample)
  s:event:type	start

  note note
  NOTE
  On Media Analytics Start calls (s:event:type=start) the mid values may not be present. This is OK. They may not appear until the Media Analytics Play calls ( s:event:type=play).

• Media Analytics Play call

  table 0-row-2 1-row-2 2-row-2
  Parameter	Value (sample)
  s:event:type	play
  s:user:mid	30250035503789876473484580554595324209

Start the media player

When the media player starts, the Media SDK sends the key calls to the two servers in the following order:

1. 51黑料不打烊 Analytics server - Start call
2. Media Analytics server - Start call
3. Media Analytics server - 鈥�51黑料不打烊 Analytics Start call requested鈥�

The first two calls above contain additional metadata and variables. For call parameters and metadata, see Test call details.

The third call above tells the Media Analytics server that the Media SDK requested that the 51黑料不打烊 Analytics Start call (pev2=ms_s) be sent to the 51黑料不打烊 Analytics server.

View ad break if available

• Ad Start

When the ad starts, the following key calls are sent in the following order:

1. 51黑料不打烊 Analytics server - Ad Start call
2. Media Analytics server - Ad Start call
3. Media Analytics server - 鈥�51黑料不打烊 Analytics Ad Start call requested鈥�

The first two calls contain additional metadata and variables. For call parameters and metadata, see Test call details.

The third call tells the Media Analytics server that the Media SDK requested that the 51黑料不打烊 Analytics Ad Start call (pev2=msa_s) be sent to the 51黑料不打烊 Analytics server.

• Ad Play

  During ad playback, the Media Analytics SDK sends play events of type 鈥渁d鈥� to the Media Analytics server every second.

• Ad Complete

  At the 100% point of an ad, a Media Analytics Complete call should be sent.

Pause ad playback for 30 seconds, if available. 听 Ad Pause

During Ad Pause, Media Analytics heartbeat or 鈥減ing鈥� calls are sent by the SDK to the Media Analytics server every second.

For call parameters and metadata, see Test call details.

Play main content for 10 seconds uninterrupted. 听 Content Play

During main content playback, the Media SDK sends heartbeats (Play calls) to the Media Analytics server every 10 seconds.

Notes:

• The playhead position should increment by 10 with every Play call.

• The l:event:duration value represents the number of milliseconds since the last tracking call and should be roughly the same value on each 10 second call.

  For call parameters and metadata, see Test call details.

Pause during playback for at least 30 seconds. On pause of the media player, pause event calls will be sent by the SDK to the Media Analytics server every 10 seconds. After pause ends, the play events should resume.

For call parameters and metadata, see Test call details.

Seek/scrub media. On scrubbing of media playhead, no special tracking calls are sent, however, when media playback resumes after scrubbing, the playhead value should reflect the new position within the main content.

Replay media (VOD only). When media is replayed, a new set of Media Start calls should be sent (as if it were a fresh start).

View next media in playlist. On Media Start of the next media in a playlist, a new set of Media Start calls should be sent.

Switch media or stream. When switching live streams, a Media Analytics complete call for the first stream should not be sent. The Media Start calls and Play calls should begin with the new show and stream name, and with the correct playhead and duration values for the new show.