Note: The Insight Reporting UI and Insight Reporting REST API have now been deprecated and Ooyala will no longer provide any support from 30 March 2018. Reports requiring data prior to 1 March 2016 should be pulled in Insight and stored elsewhere before end of life (30 March 2018). If you are still using Insight Reporting UI or Insight Reporting REST API, you need to migrate to Custom Reporting and Custom Reporting API as soon as possible. Contact your Ooyala representative for details.
Ooyala Pulse Analytics consists of three reporting tools, Custom Reporting, Insight, and Metamarkets. The reporting tools break down your data into the following parts:
  • Filters: define what part of the data in the data engine is of interest,
  • Dimensions: define how to break down the data in the report output,
  • Metrics: define the data points that you want to display in the report. Each metric is displayed in a separate column in the final report.

Custom Reporting

Pulse Custom Reporting utilises a new framework to allow for much more complex reporting than Insight. Instead of pre-aggregating data, reports are scheduled and created on the fly. The result is a big increase in flexibility and range of data with the tradeoff of time to produce the report.

Custom Reporting is used to:
  • define reports on unaggregated data and pull the report,
  • define complex reports over multiple dimensions and metrics,
  • share static or refreshable reports directly with third parties,
  • and retrieve and export reports.
When should you use Custom reporting?
  • For advanced invoicing and reconciliation reporting.
  • For monthly financial revenue reports.
  • For reports that are too complex to be created within Insight.
  • For historical reporting, not already defined in Insight.
  • For reports with dimensions and filters not supported by Insight.
  • For sharing static or refreshable reports with third parties, for example for billing or progress monitoring purposes.
When should you not use Custom Reporting?
  • When analysing and troubleshooting programmatic activity, since bid level granularity from SSP deals and marketplaces is only available in Metamarkets.
Typical use cases:
  • Getting advanced reports across all sales channels.
  • Reporting on error related events.
  • Combining many dimensions and filters.
  • Reporting where no predefined report definitions exist.
  • Sharing a refreshable report on specific campaigns with relevant advertiser, so they can monitor on their own without needing access to your Pulse account or time from one of your operators.

Error tracking reports only work if error tracking is enabled for your account, and you have an integration with at least one of the following SDKs:

  • HTML5 SDK (Core and Pulse) or any of its derivatives (HTML5 Ad Player and Plugins) for version or higher
  • iOS Pulse SDK version or higher
  • Android Pulse SDK version or higher

No error tracking information is available for direct VAST or VMAP integrations.

For more information, refer to Custom Reporting.


The Insight reporting tool is designed to provide fast, reliable access to standard, every day reporting needs. To do this, Pulse pre-aggregates typical combinations of filters, dimensions, and metrics and makes them available to report against directly within the Insight UI or through the Insight API. Insight also allows some additional combinations of filters, dimensions, and metrics to be configured by the publisher as custom templates. Once configured, these combinations also become available directly in the Pulse UI.

Insight is used to:
  • define and pull reports for data that has already been aggregated,
  • define reports on unaggregated data to pull the reports at a later date, and
  • share reports with third parties.

When should you use Insight?

  • When you require quick access to performance reports at campaign or category level, for example to provide feedback to clients on their campaigns and to monitor fill rate across inventory segments.

When should you not use Insight?

  • When you require highly complex data combinations, which are not suitable for this tool. When attempting to create such a template, the user is informed if complexity limit has been exceeded and an alternative option is provided.
  • When analysing and troubleshooting programmatic activity, since bid level granularity from SSP deals and marketplaces is only available in Metamarkets.

Typical use cases:

  • Getting basic campaign reports.
  • Sharing reporting data with media buyers.

For more information, refer to (Deprecated) Insight.


Metamarkets is a real-time analytics platform for buyers and sellers of programmatic advertising, with the main focus on auction and post bid level analytics. Metamarkets' technology is based on ingesting real-time or batch feeds of your auction records with nested bid respones, impression records, and clicks. The data is then aggregated and presented to you in form of a dashboard to help you visualize programmatic trends and opportunities and understand what is happening right now and why it is happening.

Programmatic businesses rely on real-time reporting and continuously updated data, where you can quickly and easily get answers, whether you are interested in buyer performance or troubleshooting. Using Metamarkets, you can customise your dashboards according to your own needs, and watch as auctions and bids get executed. Metamarkets provides reports on all programmatic events, complemented with direct impressions to give a better context. You can also:
  • Set alerts to notify you if a metric passes a specific threshold that you define.
  • Schedule reports for yourself or others to be delivered by email on a recurring basis; daily, weekly, or monthly.
  • Download reports.
  • Bookmark reports that you access frequently.

When should you use Metamarkets?

  • To analyse programmatic buyer behaviour.
  • To analyse deal health and performance.
  • To monitor buyer bid rates and prices, to inform holistic sales strategy.

When should you not use Metamarkets?

  • For granular analytics on direct campaigns.
  • For any invoicing and reconciliation reporting.

Typical use cases:

  • Understand the performance of programmatic buyers.
  • Troubleshoot programmatic problems.

For more information, refer to Metamarkets.

해당 내용이 도움 되었습니까?