Understand your content’s playback

Orilla VOD analytics are queried per environment and video. Collection must be enabled and the player must receive the environment’s submission configuration.

Enable and query

An administrator enables collection in the environment. The player uses its public submission key to report supported events. This public key cannot query administrative data.

In Analytics, select content and a period to review available data. Library previews do not generate new analytics views.

Choose a task

Period and Video stay together when switching sections. The page shows one workspace at a time:

• Overview: recent presence, selected metrics, and activity by interval.
• Views: session history and playback errors. From an error, you can view affected playbacks.
• Content: watch heatmap and distribution by quality and mode.
• Compare metrics: comparisons, dimensions, and insights.
• Alerts: environment rules and incidents, with their own filters.

Tools contains Annotations, Export views, and Analytics settings. Back to overview restores the initial view. Tools preserve drafts when switching sections within the same environment.

What you can observe

• Views, estimated viewers, and playing time.
• Startup, buffering, failures, and session details.
• Watch heatmaps and more or less watched moments.
• Time by quality and playback mode.
• Annotations, alert rules, incidents, and daily exports.
• Thirteen-metric comparisons and quality/volume insights.
• Grouped series and monitoring histograms.
• Email, Slack, and PagerDuty channels.

Availability depends on collection, permissions, and period coverage. Historical data that was never sent is not reconstructed.

Distinguish missing data from zero

The interface and responses distinguish unavailable coverage, partial data, and a measured zero. Unobserved dimensions remain unknown. Unique viewers are an estimate, rather than exhaustive identification of people.

Heatmaps distinguish intensity, which includes repeats, from reach by range without duplication within the same view. Intensity greater than one can represent rewatching.

SDK integration

const { data: assets } = await orilla.assets.list({ limit: 25 });
const capabilities = await orilla.data.capabilities();

Documented orilla.data SDK resources let you query metrics, dimensions, and sessions with data:read permission. Use capabilities and coverage metadata before interpreting a value as complete.

Privacy and retention

The player respects Do Not Track and does not enable analytics cookies. Without an explicit identifier, anonymous identity remains in page memory. The collector transforms identities per environment and strips query strings from URLs.

History is retained for 30 days and monitoring for 24 hours. Units differ by field: Unix times are seconds and SDK playing time may be expressed in milliseconds. Check each resource’s contract before displaying it.

Preserve a working view

Analytics → Saved views saves the period, video, order and selection of the five summary metrics, sections, and open tools. Saved tools are viewed separately, without stacking their forms on the page. Personal views are private; shared views are visible to environment members and require write permission to create or edit. Any role can manage personal views.

Save changes explicitly. If someone edits the same view, a conflict preserves your draft: load the saved version or keep your draft over the current version before saving again. The active selection is restored on reload; a video opened from Library takes priority. Internal forms, a selected playback, and freely arranged widgets are not saved.

Local time/UTC changes presentation for your user and environment, rather than calculations. Annotations and exports retain their contractual time zones. Presence, alerts, and exports can have independent scope: check each section’s label.

Provider traces

Playback details can show video_cdn_trace and whether the sequence is complete. This represents provider labels observed by the collector, without storing media URLs or header maps. Adjacent repeats collapse; a later revisit is preserved.

const providers = await orilla.data.dimensions.elements("video_cdn_trace", {
  timeframe: ["24:hours"],
  page: 1,
  limit: 25,
});
console.log(providers.data, providers.orilla.coverage);

Each provider counts once per view; partial traces are a lower bound. Without observations, the value is unknown. This instrumentation does not install or operate a CDN. Dimensions and their legacy data.filters aliases expose only collected attributes.

Daily view exports

const catalog = await orilla.data.exports.listVideoViews();
for (const day of catalog.data) {
  for (const file of day.files) {
    // Download with the signed link; do not forward SDK Authorization.
    console.log(day.export_date, file.path, file.revision_id, file.row_count);
  }
}

These are gzip CSVs covering all videos in the environment, grouped by view completion within a full UTC day. Generation covers the previous seven UTC days, with revisions for corrections; each revision is retained for seven days after generation. URLs last up to fifteen minutes: query the catalog again to renew them.

Orilla’s orilla.data.views.v1 schema preserves 55 columns, times in ms, ratios from 0 to 1, bitrate in bps, and blank unknowns. Each file has its own snapshot: the catalog is not one snapshot across all days. Per-file maximums are 100,000 rows, 128 MiB uncompressed, and 64 MiB gzip, reducible by configuration. Exceeding a limit fails without truncation; a previous valid revision may remain available during retries.

These exports do not support video filters or arbitrary periods. For bytes, storage, and ingest, use Usage and CSV. Continuous export to external destinations remains outstanding.