Campaign Reports
View Comprehensive reports for your Campaigns.
Overview
Campaign reports provide you with campaign performance at a glance. Using these reports, you can compare campaigns' performance and understand engagement trends. You can email or export the summary report of all campaigns sent out for a specific period or even for a specific day. This report includes metrics such as campaign deliveries, engagements, conversions, and errors. To optimize dashboard performance, the data in the report is cached, and you can receive data that has been generated up to 4 hours earlier. The report may take up to 6 hours, depending on the other activities happening when requesting the report.
Generate Reports
You can view the campaigns from the campaigns list page. You can either email a report or export the reports to Amazon S3 or Google Cloud Platform bucket.
To view a report:
- Navigate to the Campaigns page from the main menu. The Campaign List page opens.
- Select the campaigns or select the filter criteria to export the reports for the required campaigns.
-
Click the icon or the link. The Campaign Report window opens on the right side.
-
Configure the following settings:
Field | Description |
---|---|
Report name | Enter the name to identify your report uniquely. |
Create a report for | Select from the following options for which you want to create a report:
|
Data to include | Select the data from the following options that you want to include in the report:
|
Split all data by | Select the option to split your data. The following are the available options:
Note: Split data by day is unavailable if the date range is more than 60 days on the campaigns page. |
Frequency | Select the export frequency for your report. The following are the available options:
|
Delivery Method | Select from the following delivery options:
The reports are always exported in CSV format. |
- Click Send Report to send the report immediately or click Subscribe to send the reports at defined intervals.
You can include Campaign stats and Campaign overview in the campaign report for a maximum of 2500 campaigns. Also, you can include Campaign detailed stats in the campaign report for a maximum of 2000 campaigns.
You can view your campaign reports by navigating to FileDir:<accountID>/reports/
from your partner bucket. The report file name will be in the following format: reportName_Timestamp.csv
, where Timestamp indicates the time when the report is delivered.
Subscribe to Reports
You may want to subscribe to a report in various scenarios. For example, select and subscribe to 4 campaigns on a monthly recurrence, or only subscribe to push campaigns that you created with a label for a monthly/daily recurrence.
The subscriptions are displayed on the Subscriptions tab of the Campaign Report window. To create a new report or create a new report subscription, refer to Generate Reports.
Edit/Delete Reports
The existing schedule for the reports is displayed on the Subscribe tab. To edit or delete a subscription to a report,
- Click Subscribe to Reports on the campaign list page. The Campaign Summary Emails pane appears.
- Select the Subscriptions tab
- Click the ellipsis icon to edit or delete a report subscription.
Reports API
You can use the Get Campaign Report API to programmatically generate campaign reports for your consumption.
Campaign Report Data
The following table provides all the report columns based on the selected data group. For example, the first column, Campaign ID, will be part of each report, irrespective of the data group.
However, the Campaign Name appears as a column in your report only if you select Campaign overview when requesting the report.
Report Enhancements
We have introduced new metrics for your Email, SMS, and WhatsApp campaigns, enhancing your campaign reporting capabilities. These additional metrics are designed to provide you with deeper insights into your campaigns.
Key Highlights:
Metrics Expansion: The Campaign Report now includes new columns to accommodate these metrics, ensuring you have access to comprehensive data for your campaigns.
Availability Date: These enhancements will be available starting from September 27, 2023.
Action Required:
To ensure a seamless transition and prevent any disruptions or issues in your reporting, please incorporate these changes into your report automation setup by September 27, 2023.Resource for Reference:
For a detailed overview of the new columns and metrics, refer to our Sample Campaign Report.
Report Column | Campaign overview | Campaign stats | Campaign detailed stats | Campaign errors | Description |
---|---|---|---|---|---|
Campaign ID | Yes | Yes | Yes | Yes | The unique ID for the campaign. |
Campaign Name | Yes | The name provided for the campaign during its creation. | |||
Channel | Yes | The channel such as Email, Mobile Push, and so on that is used for the campaign. | |||
Delivery | Yes | The campaign delivery such as Action, Inaction, One time, and so on. | |||
Type | Yes | The type of campaign such as single message, message on user property, or A/B test. | |||
Variant | Yes | The message variant. Applicable only to A/B test messages and message on user property. | |||
OS | Yes | The device operating system, such as iOS and Android.Not applicable to WhatsApp. | |||
Device | Yes | Devices such as mobile, TV, or a Tablet. | |||
DND / set campaign frequency | Yes | DND or campaign frequency setting configured at the time of campaign creation. | |||
timezone | Yes | Configuration for the delivery in the user timezone. | |||
cutoff | Yes | Configuration of the cutoff period after which the campaign is not delivered. | |||
fcap (global campaign limits) | Yes | Configuration for the maximum number of messages that a user can receive in a day, taking into account all active devices and across different communication channels. | |||
throttle | Yes | Configuration for the throttle limits applied to the campaigns. | |||
Safety check limit | Yes | The campaign is not sent to any user if the number of qualified users exceed the limit. | |||
Campaign per day limit | Yes | Number of maximum messages sent per day for the campaign. | |||
Campaign overall limit | Yes | Number of maximum messages sent overall for the campaign. | |||
estimated reach | Yes | Estimated qualification of users. | |||
Reach (Send to all / last active) | Yes | Send to all devices or the last active device. Not applicable to WhatsApp | |||
WHO query | Yes | The who query defined in the campaign. | |||
Constant event property | Yes | Shows whether the Constant event property is applicable or not. | |||
Title | Yes | The title of the notification. Values must be added for the WhatsApp header. | |||
Message | Yes | Message of the notification. Values must be added for the WhatsApp body. | |||
iOS Rich Media type | Yes | Media type such as, Single or Carousel for iOS push notifications | |||
IOS Rich media URL | Yes | Image URL for iOS push notifications | |||
IOS sound file | Yes | iOS sound or the file URL if custom. | |||
IOS Badge Count | Yes | Badge count on IOS notification | |||
IOS Category | Yes | Category for iOS push notifications (if applicable). | |||
IOS Deep link / External URL | Yes | Deep link for iOS push notifications. | |||
IOS Mutable content | Yes | Shows whether the content is mutable. The values are Yes/No. Not applicable to WhatsApp. | |||
Android Subtitle | Yes | Subtitle of the Android push notifications. | |||
Android Image URL | Yes | Image URL for Android push notifications. | |||
Android Summary | Yes | Summary text for Android push notifications. | |||
Android large Icon URL | Yes | Large icon for Android push notifications. | |||
Android Small App Icon colour | Yes | Small app icon for Android push notifications. | |||
Android Deep link / External URL | Yes | Deep link for Android push notifications. | |||
Android Sound File | Yes | The values are:
| |||
Android Notification tray priority | Yes | Shows the priority of display in tray of android device | |||
Android Notification delivery priority | Yes | Server priority for Android push notifications | |||
Collapse notification | Yes | Shows whether the notification is collapsible or not | |||
Notification channels | Yes | Communication channel, for which the user consent is received. | |||
Badge ID | Yes | Badge ID for Android push notifications. | |||
Badge Icon | Yes | Badge count Android push notifications. | |||
Send to App Inbox as well | Yes | Applicable only for push. Sent to app inbox as well or not. | |||
Time to live | Yes | Time for the notification to live in the user device. | |||
SMS/ Email/ WA service provider | Yes | The service provider. | |||
Start Date | Yes | Start date of the campaign. | |||
Start Time | Yes | Displays the start time of the campaign. Displays the time value if the campaign is set to best time. | |||
Conversion Event | Yes | The conversion is tracked for this event in the campaign. | |||
Conversion Time (in minutes) | Yes | Time period within which conversion is tracked for the campaign. | |||
Campaign URL | Yes | The URL of the campaign to access it on Clevertap dashboard. | |||
Status | Yes | Current status of the campaign. | |||
Created By | Yes | The creator of the campaign. | |||
Created time | Yes | Time of creating the campaign. | |||
Labels | Yes | The Labels / tags used to identify and organize campaigns. | |||
AmplifiedByInbox | Yes | Shows whether the campaign was amplified by sending it to inbox as well or not. | |||
AmplifiedByPush | Yes | If Enhanced Push Delivery is applied or not. | |||
Web Priority | Yes | Priority of web notifications. It can be High, Medium or low. | |||
Run Date | Yes | Applicable for Day-wise reports only. Displays the run date. | |||
Total Sent (users) | Yes | Displays the total count for the sent users. Shows as N/A for channels that are not supported, such as In-app. | |||
Total Viewed (users) | Yes | Displays the total count for the users who viewed the notification. | |||
Total Clicked (users) | Yes | Displays the total count for the users who clicked the notification. | |||
Total Sent (events) | Yes | Total events. Total devices (if 'Send to all' is applied) | |||
Total Viewed (events) | Yes | Total events. Total devices (in case of 'Send to all' is applied) | |||
Total Clicked (events) | Yes | Total events. Total devices (in case of 'Send to all' is applied). | |||
Total HTML Viewed (events) | Yes | Displays the total count of HTML emails viewed. | |||
Total AMP Viewed (events) | Yes | Displays the total count of AMP emails viewed. | |||
Total HTML Clicked (events) | Yes | Displays the total count of clicks in the fallback HTML version when using the AMP feature. | |||
Total AMP Clicked (events) | Yes | Displays the total count of clicks in the AMP version when using the AMP version. | |||
Total AMP Unsubscribe (events) | Yes | Displays the count of unsubscribes through the AMP version when using the AMP feature. | |||
Total HTML Unsubscribe (events) | Yes | Displays the count of unsubscribes through the HTML version when using the AMP feature. | |||
Errors | Yes | Errors | |||
Click through conversions | Yes | Total converting users ( as per funnel, including clicked step). For non-CT BSP, it would be counted as view-through conversions. | |||
Click through conversions % | Yes | Total converting users / Total sent users. For non-CT BSP, it would be counted as view-through conversions. | |||
Click through conversion revenue | Yes | Revenue as per the revenue property related to Total conversions. For non-CT BSP, it would be counted as view-through conversions. | |||
Total control group count | Yes | Total number of users in control group. | |||
Total control group conversions | Yes | Total number of control group users converting. | |||
Total control group conversions % | Yes | Total number of control group users converting / Total number of users in control group. | |||
Total control group revenue | Yes | Revenue as per revenue property related to conversion. | |||
Total Delivered(users) | Yes | Total number of unique users who receive WhatsApp or SMS notifications. | |||
Total Delivered(Events) | Total number of SMS or WhatsApp notifications delivered to the end users. | ||||
Template Name | Represents the Template name used in the WhatsApp campaign. | ||||
Provider Name | Represents the nickname of the WhatsApp and/or Email service provider. | ||||
WABA number | Represents the source phone number. | ||||
Unique Sent (users) | Yes | Unique users who were sent notifications. | |||
Unique Viewed Within Conversion Time | Yes | Unique users who viewed the notifications within the set conversion time. | |||
Unique Clicked Within Conversion Time | Yes | Unique users who clicked the notifications within the set conversion time. Not available for WhatsApp campaigns. | |||
Unique Converted Within Conversion Time | Yes | Unique users who converted within the set conversion time. | |||
Revenue Within Conversion Time | Yes | Revenue as per the revenue property related to conversion. | |||
Influenced Conversions | Numbers populated from the sent > converted funnel. If the Push Impression is enabled for the account, the numbers are populated from the View > Converted funnel. | ||||
Influenced Conversions % | Percentage of users converted in sent > converted funnel. If the Push Impression is enabled for the account, it indicates the percentage of users who converted in the View > Converted funnel. | ||||
Influenced Revenue | Revenue from users shown as converted in sent > converted funnel. If the Push Impression is enabled for the account, it indicates the revenue from the user shown as converted in the View > Converted funnel. | ||||
System Control Group Conversions | Yes | Total number of system control group users converting. | |||
System Control Group Conversions % | Yes | Total number of system control group users converting / Total number of users in system control group. | |||
System Control Group Revenue | Yes | Revenue as per the revenue property related to conversion. | |||
Campaign Control Group Conversions | Yes | Total number of campaign control group users converting | |||
Campaign Control Group Conversions % | Yes | Total number of campaign control group users converting / Total number of users in campaign control group. | |||
Campaign Control Group Revenue | Yes | Revenue as per the revenue property related to conversion | |||
Custom Control Group Conversions | Yes | Total number of custom control group users converting. | |||
Custom Control Group Conversions % | Yes | Total number of custom control group users converting / Total number of users in custom control group. | |||
Custom Control Group Revenue | Yes | Revenue as per the revenue property related to conversion. | |||
Custom Control Group Name | Yes | Name of the custom control group. | |||
System Control Group Count | Yes | Total number of users in system control group. | |||
Custom Control Group count | Yes | Total number of users in custom control group. | |||
Campaign Control Group count | Yes | Total number of users in campaign control group. | |||
Invalid FCM key | Yes | Campaign error description. | |||
App uninstalled(Android) | Yes | Campaign error description. | |||
Wrong FCM API key | Yes | Campaign error description. | |||
Invalid APNS certificate | Yes | Campaign error description. | |||
APNS error | Yes | Campaign error description. | |||
APNS Format error | Yes | Campaign error description. | |||
APNS Account Temporarily Blacklisted | Yes | Campaign error description. | |||
App Uninstalled(iOS) | Yes | Campaign error description. | |||
Invalid Profiles | Yes | Campaign error description. | |||
Duplicate APNS Token | Yes | Campaign error description. | |||
Invalid token - FCM | Yes | Campaign error description. | |||
Unknown error - FCM | Yes | Campaign error description. | |||
Dispatch error | Yes | Campaign error description. | |||
Internal error due to amplification | Yes | Campaign error description. | |||
Global frequency cap exceeded | Yes | Campaign error description. | |||
Campaign frequency cap exceeded | Yes | Campaign error description. | |||
Campaign limit reached for day | Yes | Campaign error description. | |||
Campaign limit reach for run | Yes | Campaign error description. | |||
Profile not reachable | Yes | Campaign error description. | |||
Campaign stopped | Yes | Campaign error description. | |||
User DND | Yes | Campaign error description. | |||
Duplicate profile for channel | Yes | Campaign error description. | |||
APNS bad topic error | Yes | Campaign error description. | |||
APNS disallowed topic | Yes | Campaign error description. | |||
APNS bad device token | Yes | Campaign error description. | |||
APNS device token and topic mismatch | Yes | Campaign error description. | |||
APNS inactive device token for topic | Yes | Campaign error description. | |||
APNS wrong environment certificate | Yes | Campaign error description. | |||
APNS bad certificate | Yes | Campaign error description. | |||
APNS idle timeout | Yes | Campaign error description. | |||
APNS missing certificate topic | Yes | Campaign error description. | |||
APNS Bad Priority | Yes | Campaign error description. | |||
FCM payload too large | Yes | Campaign error description. | |||
User not reachable | Yes | Campaign error description. | |||
User not qualified | Yes | Campaign error description. | |||
Notification during campaign DND | Yes | Campaign error description. | |||
Campaign cut-off time reached | Yes | Campaign error description. |
Send Copy of Push Campaign to App Inbox
When you choose to send a copy of a Push campaign to the App Inbox, it appears as a single campaign on the All Campaigns page on the dashboard. However, you will see two separate entries for the campaign in the campaign reports.
Conversion Tracking Rules
To understand how CleverTap tracks conversions, it is essential to note the following rules:
User is considered converted if they complete a conversion event within the conversion timeline.
User is only counted as converted once for a particular conversion event within a campaign. For example, if a user completes the same conversion event multiple times within the same conversion timeline, it will only be counted once.
If a user completes a conversion event within the same timeline for multiple campaigns, it is attributed to all the campaigns.
A user is considered converted even if they do not open or click the message as long as they complete the conversion event within the conversion timeline. This is known as an influenced conversion.
Updated 1 day ago