Custom Reporting

Note: The Custom Reporting functionality in Pulse must be enabled for your account before you can access it. Contact your Account Manager to find out how Custom Reporting may benefit you and to enable it.
Custom Reporting is a reporting tool which can 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 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 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.
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.
  • 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.

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.

Limitations for Custom Reporting

  • Reports return maximum 100000 rows. To make sure your report is not incomplete due to reaching the maximum number of rows, refer to these tips.
  • You can store at most 200 reports. If another report is created after the allocation is filled, then the report with the oldest creation date is removed.
  • You can define maximum eight grouping dimensions for a report.
  • You can filter on maximum ten tags in a report.
  • You cannot combine breaking down the data based on audience segments and tags in the same report, because the report result cardinality could be too high.
  • You can run maximum two reports at the same time. If there are two reports waiting to complete in Custom Reporting, you can still create new reports but their status is set to "Queued".
    • When one of the currently running reports is done (ready, failed, or cancelled), the first report in queue is run.
    • Queued reports are ordered based on creation date and time, so the report with the oldest creation date and time is the first one in queue, and this order cannot be changed.
    • You can queue maximum 10 reports.
    • You can delete queued reports.
  • The query for a report runs for maximum 5 hours. Queries that take longer are cancelled, and the report's status is set to 'Failed'.
  • Data for Custom Reporting is only available for the past 25 months. Reports where at least a part of the selected time span falls outside the data retention period, fail to run.
    Note: In addition, audience data in Custom Reporting is only available from 1 December, 2017.
  • The time span of a report can be maximum twelve months. Reports requested over a longer period fail to run.
  • Only the described dimensions, metrics, and filters in this document set are available in Custom Reporting.
  • Revenue metrics are visible to all users of your Pulse account when using Custom Reporting, even if a particular user cannot see revenue metrics in the Pulse User Interface.
  • The Custom Reporting tool calculates the approximate count of unique inventory and unique impressions metrics by using the HyperLogLog algorithm, which provides deterministic results when running reports for the same time range, filters, and dimensions. This way your reports run faster, and finish, which cannot be guaranteed when using distinct counts. The expected difference from distinct counts is only 2 to 3%.
  • Lookup values for audience segments have no history. As a result, a Custom Report may break, when the segment mapping in Ooyala's backend is updated or is missing segments. Updated segment mappings only make the segment IDs resolve to a different name. Missing segment mappings resolve to 'undefined' in the reports.

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