Sending ping events
Last update: December 13, 2024
- Topics:
- Media Analytics
CREATED FOR:
- User
- Admin
- Developer
You must fire ping events every 10 seconds, beginning after 10 seconds of playback, regardless of other API events that you have sent. This applies for both main content and ad tracking.
The ping events are the “heartbeat” of the Streaming Media Collection. The only required parameters for a ping call are eventType: ping
along with the playerTime
object (playhead position and timestamp).
The following code snippet shows one way to implement a timed pinging mechanism for main content (10 second interval):
...
Pinger.init(10000);
...
Pinger.kill();
var Pinger = {
init: function(interval) {
this._timer = window.setInterval(function() {
$.event.trigger({type: "onPing", _data: ""});
}, interval);
},
kill: function() {
window.clearInterval(this._timer);
}
}
Previous pageValidating Event Requests
Next pageSending QoE Data
Analytics
- Streaming Media Collection Guide
- Release Notes
- Get started
- Implementation
- Implementation overview
- Edge implementations (recommended)
- Adobe Analytics-only implementations
- Prerequisites
- Media SDKs / Extension
- Media Collection APIs - Implementation
- Media Collection
- API Quick Start
- Sessions Request
- Events Request
- Request Parameters
- Event Types and Descriptions
- Implementing the API
- Setting the HTTP Request Type in Your Player
- Obtaining a Session ID
- Implementing an Events Request
- JSON Validation Schemas
- Validating Event Requests
- Sending Ping Events
- Sending QoE Data
- Custom Metadata Support
- Timeout Conditions
- Controlling the Order of Events
- Queueing Events When Sessions Response is Slow
- Variables
- Reporting
- Use Cases
- Tracking
- Privacy and Security
- Legacy Implementations
- Legacy - Overview
- Legacy — Download SDKs
- Legacy - Media SDKs
- About Heartbeat Measurement
- Adobe Primetime
- Adobe Audience Management Enablement
- Custom Link Implementation
- Legacy Milestone Tracking
- Validation
- Legacy Migration: VHL 1.x to VHL 2.x
- Code Comparison v1.x to v2.x
- Tracking APIs 1x to 2x
- Legacy - Intro to AVA
- Client Side Path
- Legacy Tracking
- Track Core Playback on Android
- Track Core Playback on iOS
- Track Core Playback on JavaScript
- Track Core Playback on JavaScript 2.x
- Track Buffering on Android
- Track Buffering on iOS
- Track Buffering on JavaScript
- Track Seeking on Android
- Track Seeking on iOS
- Track Seeking on JavaScript
- Implement standard metadata on Android
- Implement standard metadata on iOS
- iOS Metadata Keys
- Implement Standard Metadata on JavaScript
- Track Ads
- Track Chapters and Segments
- Track Errors
- Tracking Scenarios
- VOD playback with no ads
- VOD playback with pre-roll ads
- VOD playback with skipped ads
- VOD playback with one chapter
- VOD playback with a skipped chapter
- VOD playback with seeking in the main content
- VOD playback with buffering
- VOD multiple trackers in parallel
- VOD one tracker for multiple sessions
- Live main content
- Live main content with sequential tracking