In-App Message Impressions Appear Lower Than Expected
If your impressions are lower than you’d like them to be, we recommend you…
It’s important to ensure that your Segment size in the Campaign reflects your intended audience. Perhaps there are filters applied limiting your audience and causing your campaign to have fewer impressions.
If the impression count is low compared to where it once was, make sure no one unintentionally altered the Segment or Campaign since launch. Our Segment and Campaign changelogs will give you insight into changes that have been made, who made the change, and when it happened.
A quick way to identify any obvious issues is to clone the Campaign and target your own userid/email and launch the Campaign. Once you perform the message trigger (Session Start, Custom Event, etc.), verify that you receive the message correctly. Then, navigate to the dashboard and refresh the page to see if your impression is logged correctly. If it is not, then the problem is likely within your implementation.
If the campaign is triggered by a Session Start or a Custom Event, you will want to ensure that this event or session is happening frequently enough to actually trigger the message. You can check this data on the App Usage (for session data) or Custom Events pages:
Customization of the In-App Message UI or delivery mechanisms within the SDK may require your developers to utilize our methods to manually log In-App message impressions. Check with your developers to see if you use In-App message customization.
You can read more about this:
Still need help? Open a support ticket.