Trigger the right Interactions, at the right place and time, by leveraging Events.
Events are markers of in-app activity that customers trigger throughout their lifecycle. They are flexible and most commonly triggered when specific pages are viewed, important buttons are tapped, or menu selections are made. Events are the core of Apptentive targeting, and having a robust list of 20 – 50 meaningful Events is essential in ensuring that you can make the most of your Apptentive integration.
Every app is different, and as such, Events should always be tailored to your specific goals.
For example, imagine that you have a retail app and you’d like to use the Love Dialog to measure the sentiment of new customers that have completed a purchase. How are those customers feeling about your app? To do this, you’d need two Events: “signup_complete” and “purchase_confirmation_close”. Then, you target the Love Dialog to anyone that has triggered signup_complete within the last 15 days the next time they trigger a purchase_confirmation_close event:
Events are foundational to Apptentive targeting, and having a meaningful list at your disposal will allow you to engage as broad or as narrow segments of your audience as you desire.
In this doc, you’ll learn about the two kinds of Events, how those Events are set up within your integration, and best practices for making the most of them.
There are two ways in which Events can be used for targeting: as “WHO” Events and as “WHERE” Events. WHO Events determine which customers are eligible to see specific Interactions, and WHERE Events define the screen on which those Interactions are actually displayed.
- WHO Events: This is segmentation targeting. If you’re setting up a Love Dialog or Survey, always ask yourself, “WHO should be able to see this Interaction?” Examples of great WHO Events could be signup_complete, purchase_complete, favorites_viewed, or video_complete.
- WHERE Events: Ask yourself, “WHERE should this Interaction be displayed?” Be sure that you do not interrupt customers when they are in the middle of completing an action. Here, back buttons or pages that show completion will be your best friend. Suggestions include purchase_confirmation_close, search_back_button, or money_transfer_back_button.
WHO and WHERE Events do not need to be mutually exclusive. In some cases, it can make sense to tag an event to a single action that both measures engagement (WHO) and that is a good time to show a dialog (WHERE).
From a technical perspective, both WHO and WHERE Events are tagged in the same manner regardless of how you intend to use them.
Do not worry about coding counts or times into the Events themselves. Just create the Event, then further targeting details can be added directly on your Dashboard at any time — no code changes necessary. By default, you can add segmentation details like count, count in installed version, and time since last seen. Here’s an example where you can see those options for a sample Event, homescreen_opened:
Every app is different, and even apps within the same category may have different Events.
Events need to be called within the SDK by your developers in order for you to utilize them. To allow yourself flexibility in your interactions with customers, we recommend identifying at least 20 – 50 Events that encompass all of the main page views and button taps within the app before releasing it to an app store. This will give you the flexibility you need to engage customers throughout their lifecycle in a variety of ways, as well as future-proof your integration as much as possible.
Be sure that you use a consistent naming convention, such as word_word, for all of your Events. Additionally, the naming convention should be descriptive and easy to understand for all team members. Even if you intend to use Apptentive for something like a Survey, do not call it “survey_event”. Rather, make the Event name descriptive, like “viewed_photos_back_button”. Share the naming conventions and locations of your Events between developers and product managers so everyone is clear on where each location is within your app. We created an Excel document you can use to get started.
Once Events have been called, Apptentive will automatically track each instance of the Event being triggered within the app. These counts can be viewed by visiting Interactions > Events on your Apptentive Dashboard for each app you have added to your Organization. Let’s take a look at this within the dashboard:
The default timeframe for Event count is 30-days; however, this can be changed simply by selecting different beginning and end dates on the upper right hand corner of the screen.
Video: Using Events
Example Events by Category
The perfect mobile moment to communicate with your customers varies from app to app. Below are some Event examples organized by app category.
Retail & Shopping
- item_details_ closed
Food & Drink
Media, News, & Entertainment
Looking for More Assistance?
Now it’s your turn to get started with Events! If you’d like more guidance, please don’t hesitate to reach out. Our team is here to help answer any questions and assist you along the way. Please contact your Customer Success Manager or email@example.com.