Analytics

Ooyala Pulse Analytics consists of two reporting tools, Insight and Custom Reporting. 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.

Insight

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.

Typical use cases:

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

For more information, refer to Insight.

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 that can only be handled with Custom Reporting,
  • and retrieve reports, previously created through Custom Reporting.
When should I 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.
When should I not use Custom Reporting?
  • When the same report is available through Insight, because through Custom Reporting the report needs to be completely recreated and data needs to get aggregated, which may take a long time.
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.
Note:

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 2.1.16.23.1 or higher
  • iOS Pulse SDK version 2.3.17.1.0 or higher
  • Android Pulse SDK version 2.3.16.25.0 or higher

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

Was this article helpful?