When creating an app campaign, such as a popup survey, you’ll target specific app visitors by implementing events. When an event is triggered, GetFeedback shows the survey to your app visitor. Event targeting lets you ask for targeted feedback at specific points in the customer journey.
An event signifies that an action occurred in your app. This action can be anything, from making a purchase to opening or closing the app menu. The event can be initiated by the user (ex: clicking a button) or by the app (ex: the user's flight has just arrived).
You can use two types of events for app campaigns:
You can create custom events based on the actions or moments you want to target in your app. It's best to speak to your technical team to learn which events can help you to target the right users.
Custom events are the most flexible targeting option for your campaigns. Your team defines custom events so you can target any event or action in the app. Custom events can have a positive effect on your campaign's conversion rate.
However, your development team will need to program your app to use custom events. For more common use cases, such as showing the campaign after someone closes the app early, consider using our pre-implemented standard events instead. Standard events are already programmed in the GetFeedback SDK and don’t require additional work from your development team.
Custom events are highly customizable and closely follow the behavior of your users in your app. Some examples of possible events are:
Learning more about your users
Measure specific metrics
To help you define the custom events to use your campaigns, consider the following 4 questions. These questions can help you create events and campaigns that are relevant to you and guide your developers when they create events.
Before thinking of any event, consider the goal you have in mind for your campaign. Do you want to set up a campaign to measure the KPIs that are set, or do you want to notify users about a new feature in your app? By having a clear goal, you'll also be able to think about what type of campaign to use and what type of question elements to use. For example, is a shorter or longer survey best for your campaign?
Once you have your goal and know what you want to ask in your Campaign, consider where the campaign should be triggered. Consider mapping the customer journeys in your app. By having a clear overview of the different routes users can take to achieve their goal, you'll know exactly when to show your campaign.
Once you have a clear picture of what you would like to achieve with your Campaigns and what the best place is to display your Campaign, the next step is combining these two things with the Events you would like to use. Consider these questions to help you define the events:
Consider creating an Event Library with the result of each of the previous steps. This document can be the reference point for everyone in your team that will be creating campaigns or events. A completed Event Library contains at least 3 columns with the following information:
The image below shows an example of a completed event library:
In most cases the app developers will create the custom events for your app. It's best to meet with your developers and share the outcome of the previous three steps by sharing the Event Library. Since there is a chance your app is already using events from a different SDK certain events may already be defined.
Your meeting with developers can also help you estimate how long it will take to implement the custom events and when you start using them.
To clarify each of these steps, let's set up a test scenario where we can apply each of these steps.
After your developers have implemented the event, go to GetFeedback for Apps and create your campaign. In the User Targeting section, you can enter the event and set additional targeting conditions, such as device language. You can show a campaign to your users as soon as an event is fired, or only after an event has been fired a number of times. Learn more about creating app campaigns
Make sure that the targeted event is identical to the event that your developer specified in your app. Custom event names are case sensitive.
After specifying the event in your campaign targeting, activate and test your campaign. As soon as the GetFeedback Digital SDK has been implemented in your app and your events have been added, you can activate and deactivate new campaigns without making any code changes. Your campaign will be live as soon as it's activated.