Prerequisites for Adobe Analytics-only implementations
- Topics:
- Media Analytics
- System Requirements
CREATED FOR:
- User
- Admin
- Developer
The prerequisites described in this section are specific to implementing the Streaming Media Collection with Adobe-Analytics-only implementations (when not using Edge).
-
Complete the general prerequisites
Whether you implement the Streaming Media Collection for Adobe Analytics-only implementations or for Edge implementations, ensure that you meet the general prerequisites. -
Confirm that you have an Adobe Analytics implementation
When implementing the Streaming Media Collection with an Analytics-only implementation, an Adobe Analytics basic implementation is also required. See Implement Adobe Analytics for more information. -
Obtain the media tracking server URL
Ask your Adobe Analytics Representative for the media tracking server URL. This is thecollection-api-server
URL for the Mobile SDK, the JavaScript SDK, and the non-collection-api tracking server for Roku. Domain names for API implementation is:[your_namespace].hb-api.omtrdc.net
. -
Download the current Media SDK or implement the required Extensions
Depending on the implementation path, download the current SDK for web, mobile, or over-the-top platforms. The required extensions must be implemented to enable the Streaming Media Collection extensions paths. -
Enable Adobe Analytics Reports
To enable reports in Analytics and to view the content and ad data that you’re collecting, you must enable reports in Analytics. See Media reports enablement.
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