Events and Metrics for In-Browser Messages

This guide describes events and metrics relevant to web in-browser messages (in-app messages that target a website).

# In this article

# Events

To send an in-browser message campaign, set up and send an in-app message campaign that targets your website. Since in-browser messages are just in-app message campaigns that target a website, Iterable creates in-app events as it sends these campaigns and users interact with them.

These are the system events that can result from an in-app message campaign that targets your website (in other words, an in-browser message campaign):

• In-App Send — Created when you send an in-app message campaign to a user, no matter whether you target mobile apps or websites (must be a real campaign, not a test message/proof).

• In-App Delivery — Created when a mobile app or website downloads an in-app message from Iterable's API. However, this doesn't mean that the message has been displayed.

• In-App Open — Created when an in-app message is displayed on a website or in a mobile app.

• In-App Click — Created when a user clicks a link or a button in an in-app message.

• In-App Close — Created when a user clicks a link that explicitly closes an in-app message or clicks off of the message body to close it.

• In-App Delete — Created when you delete an in-app message. Note that Iterable's web SDK does not yet support In-App Delete events.

# Viewing events

To view events related to an in-browser messaging campaign:

1. In Iterable, in the project you used to send the in-browser messages, navigate to Audience > Contact lookup.

2. On this page, enter the email address for the user whose events you'd like to see, and click Search Users.

3. On the user profile, navigate to the Event history tab.

4. To see the fields included on an event, click the Show link on the far-right side of its row in the table. Here's an In-App Delivery event:

   

   A few things to note:

   • This event has a platform value of Web, which means that it was sent to a web browser (in other words, it's associated with an in-browser message).

   • deviceId is set to the user agent string of the browser associated with the event.

   • appPackageName is the unique identifier associated with the website integration you created in Iterable.

# Metrics

There no events or metrics that are specific to in-browser messages. In-browser messages are just in-app messages that target a website, and their s system events have:

• platform set to Web
• deviceId set to a browser user agent
• appPackageName set to a website's unique identifier.

To analyze the performance of an in-browser messaging campaign, use the same metrics that you'd use for any in-app message campaign.

In Messaging Insights and Campaign Analytics, you can hover some metrics (for example, Click Rate, Total Clicks, Total Opens, and Total Deliveries) to view an app-by-app breakdown.

Messaging Insights:

Campaign Anaytics: