Show Menu
TOPICS×

Optimizing report creation

Data volume

To guarantee optimal performances, the volume of manipulated data mustn't be too large.
Namely:
  • Calculation time for a report must never exceed 5 minutes.
    Likewise, during the design phase, with a small volume of data, if report calculation exceeds 60 seconds, the calculation methods needs to be changed.
  • When using Marketing Analytics, the manipulated data must not exceed 10 million lines.
We also recommend calculating aggregates at night and using this aggregated data directly in the reports. These aggregates must be created via dedicated Data Management workflows (SQL queries).
You can also calculate reports during the night and automatically create a history that can be viewed at any time without overloading the database.

Queries

We recommend using SQL queries whenever possible and avoiding JavaScript post-processing. If necessary, use a Script activity in a workflow and delete the data used for calculation. You can also use archived data to accelerate the processing time.
In this case, the following syntax should be used:
if(string(ctx@_historyId)!==""))

Queries that enable you to collect the data displayed in the reports must not be too complex, especially if applied to all the data in the database. To improve performances, it can be useful to filter the data before executing these queries: this means the calculation will only concern part of the data.

Performances

The recommendations above enable you to optimize report calculation.
In addition to this, Adobe Campaign recommends the following improvements:
  • Study the datamodel: indexed fields must be used mainly to improve calculation formulas.
    To find an indexed field quickly, look at the name of the column in the Adobe Campaign interface: the sorting arrow is underlined in red if the field is indexed.
  • Make sure the report is valid in the long run: data volume may increase significantly over time.
    Likewise, the volume of data manipulated during the test phases may differ from the actual data volume in production. This is why test phases are important.
    Finally, data purge delays need to be known and adapted when necessary for easy data manipulation.

Exporting reports

Recommendations specific to exporting reports are detailed in this section .