We are excited to announce a new feature that brings standardized report naming conventions to our platform. We have defined a specific format for each report, which includes all of the critical information users need to identify and access the report they require.

We believe this improved naming convention will significantly enhance the user experience and make it easier for users to access the data they need.

Here's an example: If you schedule a daily recurring Email Detailed report for campaign ID 244, You will receive 35690-Scheduled_Campaign_ID-244_Email_Detailed_Daily_T-1_20230321-cG9kMl9lbWFpbF9yYXNobWlfMTY3NTgzNDM4MQ==.zip

Standard format

One-time download: <Jobid>-<Mode of communication>_<ID>_<Channel>_<Report type>_<Date of request>-<Random string>.zip

Recurring download: <Jobid>-Scheduled_<Mode of communication>_<ID>_<Channel>_<Report type>_<Frequency>_<Date of request>-<Random string>.zip

Legend

Job ID - Unique ID created for every request Mode of communication - Campaign or Journey ID - Unique ID for the campaign/journey that the report is requested for (Applicable for single campaign/journey downloads only). In case of multiple campaigns/journeys download - this will be replaced with Multi as a keyword Channel - Email/SMS/App push/Web push Report type - Summary/Detailed for campaigns, Detailed summary/Custom detailed/Nodewise/Datewise for journeys Frequency - Daily/Weekly/Monthly appended with the data requested (T-1, T-3, etc.) Date of request - Date of requesting the report Random string - an internal string to ensure data security

Note

• Changes apply only to IA2.0 panels
• Naming conventions are not applicable for In-app, Web message & WhatsApp channels.
• In case you are on IA2.0 and you do not see the changes, please contact your account manager.

Documentation