A report may take a long time to process or may even fail if:
- There are lots of objects (i.e. keywords, creatives, etc.) within the report. This can result in a large amount of data rows to be processed.
- Calculated columns and/or custom columns are included in the report. The system will need to recalculate the values for each object. Including non-standard metrics in the custom column definition (ie. specific conversion types or other custom columns) can increase processing time.
- Many filters on metric columns, dimension columns, custom columns. The system will need to recalculate the values for each filter, which can increase processing time.
- Selecting a large date range and viewing data by day. This can result in a large amount of data rows to be processed.
- There are many columns within the report. This can result in a large amount of data columns to be processed.
Having any combination of the above will cause this reporting issue, and is expected behavior.
How To Avoid Processing Failure Or Reduce Run Time
If the report processing time is slow, cancel the running report and start a new one. When running large reports, you can take these steps to avoid report processing failure and reduce the run time:
- Include only necessary columns in the report. Note: Do not include more than 20 columns in your report. You can eliminate unnecessary columns using View Builder.
- Reduce the number of rows. Use filters to exclude any items (Keyword, Group, Campaign, etc.) that are not needed in the report.
- Use the Email Report feature. The report will be sent out when completed or scheduled to run on a recurring basis.
- Run the report in batches (by specific criteria, i.e., publisher).
- If you include a custom column in your report, please be sure the custom column is based on standard metrics. If you have a custom column based on another custom column, it will slow down processing.