Introduction

The Campaign Analytics page, visible when you open an in-app campaign from the All Campaigns page or when you publish a campaign, can be used to visualize the performance of In-App campaigns.

Campaign Analytics for In-App Nativ Version 3

Below sections will describe the various components of the campaign analytics page of In-App Nativ Version 3. The definition of the metrics will remain the same across Version 2 and Version 3 of In-App Nativ Campaigns.

Aggregate Campaign Stats

This section represents the aggregated campaign metrics for the selected date range, platform, and attribution type.

• Impressions - Number of times a message from this campaign was shown.
• Clicks - Number of times a message from this campaign was clicked.
• CTR - Click through rate, calculated as CTR = Clicks / Impressions
• Close - Number of times a message from this campaign was closed.
• Conversion Events - The total number of conversion goal events executed by all converted users. The number will vary as per the attribution type selected.
• Conversions - Total Number of times the primary conversion goal was performed after an impression/click of this campaign's message. The number will vary as per the attribution type selected.
• CVR - Conversion Rate, calculate as CVR = Conversions / Impressions.
• Attribution Type - To attribute conversions to this campaign, we support three different models as below -
  - View Through : Conversion event was performed after viewing the message.
  - Click Through : Conversion event was performed after clicking the message.
  - In Session : Conversion event was performed within 30 minutes of viewing the message.
• Attribution Window - Time period for which conversions will be tracked after impression or click as per the attribution type.

Campaign Revenue

In your In-App Nativ Version 3 campaigns, you can now define a revenue attribute along with your primary conversion goal as shown below -

Once defined, you will be able to see the below metrics on the campaign analytics page which will tell you the exact revenue that your campaign is driving.

• Total Campaign Revenue - This represents the total revenue generated through this campaign.
• Average Order Value - Average order value represents the average value of conversions through this campaign. Average Order Value = Total Campaign Revenue / Total Conversion Events.
• Average Revenue Per Converted User - This represents the total revenue generated by each user who performed the conversion event. ARPCU = Total Campaign Revenue / Total Conversion

Please note that you need to set the revenue attribute in your conversion events to be able to see these revenue information in campaign analytics.

Campaign Performance

This section helps you visualize the time series data of how the campaign metrics have varied over time.

Impressions, Clicks, Conversions and Conversion Events are similar to the ones mentioned in aggregate campaign stats. The time scale is represented as per your app timezone.

Change the date range selection, attribution type and platform from the top header. You can also switch to the table view from top right corner to see the time series data in a table.

Additionally, you can use segmentation to segment the users who have received or clicked the In-app campaign by filtering on Mobile In-App Shown and Mobile In-App Clicked events respectively.

Conversion Goals Stats

This section helps you visualize the performance of each of your conversion goals. In your in-app nativ version 3 campaigns, you can now add up to 5 conversion goals and view the performance of each conversion goal in this section.

Here, the goal marked as (Primary) is the primary conversion goal. In the previous sections, only aggregates of the primary conversion goal are listed, whereas in this section, you can view the performance of each conversion goal.

The cards in the top left corner of this section also list the performance of the primary conversion goal, which is also considered as the primary indicator of the campaign's performance. Switch to a time series view from the top right corner.

Campaign Delivery

The campaign delivery stats section helps you understand the delivery metrics of your campaign and the number of users that were removed in each funnel stage due to delivery failure. With delivery funnel analysis, you will be able to gauge why your impressions are not as expected or what needs to be changed in order to improve the delivery rate.

The various delivery funnel stages are explained in the table below:

Error Breakdown

This section describes the various campaign delivery failures and their reasons. Errors are categorized under the following heads:

1. Selection Failure - these errors happen when the in-app campaign has not been selected, and they could happen due to one of these reasons:
   
   • • • 1. Higher priority campaign available - the campaign was not selected as a higher priority campaign was available. You can set the priority as critical in the campaign to make sure the campaign is picked over all other campaigns.
         2. Maximum Times Shown - the message was not displayed as the campaign's maximum times shown limit will be breached. For more information, refer to Maximum Times Shown.
            
         3. Minimum Delay Condition - the message was not displayed as the minimum delay between campaigns criteria set in the campaign was not met. For more information, refer to Minimum Delay Between In-App Campaigns.
         4. Global Delay Condition - the message was not displayed as the minimum delay between campaign criteria for in-app campaigns set globally was not met. For more information, refer to Global Delay Between In-App Campaigns.
         5. Screen Mismatch - the message was not displayed because the user was on a different screen than the one specified in the trigger criteria for this campaign.
         6. Context Mismatch - the message was not displayed because the user was in a different app context than what was specified for show in app context for this campaign. For more information, refer to App Context.
         7. Campaign Expired - the message was not displayed as the campaign had expired.
         8. Unsupported Orientation - the message was not displayed as the orientation mode of the user's device was different than the one specified in the template. For example, some in-app templates may have specific orientations set for them, such as Portrait or Landscape alone, and if the user's device orientation is different from the specified orientation, the message will not be shown.
         9. In-App Blocked - the message was not displayed because in-app messages were blocked on the screen by the developer in the app
         10. User not on Android 13 or already opted in - the message was not displayed because the user was not on Android 13 or had already opted-in for the Android 13 push notifications. This is applicable when you use in-app notifications for two-step opt-ins. For more information, refer to Push Opt-ins.
2. Delivery Failure - these errors happen when the in-app message was not shown to the user. This could happen due to any of the following reasons:
   • • • 1. API failure - this happens when there is a failure at the API end.
         2. Personalization failure - this happens when the attribute used in personalization is not available for a specific user.
         3. Campaign Paused - this happens when the in-app campaign a running in-app campaign is paused.
         4. Campaign Under Review - this happens when the in-app campaign is moved to the under-review state by an approver. Campaigns can be reviewed, approved, and rejected only when campaign approval flow (CAF) is enabled. For more information, refer to CAF.
         5. Campaign Rejected - this happens when the in-app campaign is moved to the under-review state by an approver. Campaigns can be reviewed, approved, and rejected only when campaign approval flow (CAF) is enabled. For more information, refer to CAF.
         6. Missing parameters - this happens when some of the parameters used in the campaign are missing.
         7. Campaign archived - this happens when a running campaign is archived.
         8. Campaign control group - this happens when a user qualifies for an in-app campaign but is removed from the target audience as they fall into the campaign control group.
         9. Global control group - this happens when a user qualifies for an in-app campaign but is removed from the target audience as they fall into the global control group.
3. Display Failure - these errors happen when the in-app message was not displayed, and they could happen due to one of these reasons:
   • • • 1. Another campaign visible - the message was not displayed as another campaign was already displayed at the same time.
         2. Image failure - the message was not displayed as the image failed to be downloaded.
         3. GIF failure - the message was not displayed as the required GIF library has not been integrated with the app.
         4. Height exceeded - the message was not displayed as the message height exceeded the height of the device.
         5. Internal server error - the message was not displayed as there were some internal errors.
         6. File download failure - the message was not displayed as the file was not downloaded.

Click Performance

To know where users are exactly clicking on your in-app message, you can refer the click performance section where you will know the clicks on each widget of the in-app message.