When creating an app campaign, such as a popup survey, you’ll target specific website visitors by implementing events. When an event is triggered, GetFeedback shows the survey to your website visitor. Standard events let you target visitors after common events, such as updating or opening the app, without extra work from your app developers.
Here is a list of standard events you can use:
Standard events don't require any additional setup. This means that you won't need to implement these key events yourself, saving you valuable time so that you can start listening to your customers even faster.
If you need to target users after specific events related to your app, you may need to implement a custom event with the support of your app development team.
Standard events are available on the following SDKs:
If your app uses one of our SDK bridges please check the availability of the Standard Events in the release notes.
For the best results, make sure to follow the implementation guide in Readme of the SDK. Not following certain steps, such as recommended moment to initialize the SDK, might prevent certain standard events from working as expected.
Show your campaign after someone opens the app after it was closed. The App launch event triggers as soon as the GetFeedback SDK is initialized or when your app is launched after it was closed before.
Conditions:
The App Closed Early event triggers when the app is launched after it was closed early. You determine how long someone should spend in the app before we consider the app to close early.
Conditions:
Show your campaign to users who have updated your app to a certain version. The App Updated event triggers as soon as the GetFeedback SDK is initialized or when your app is launched after it was closed before.
Conditions:
Show your campaign to users who haven’t updated their app to a certain version. The App Not Updated event triggers as soon as the GetFeedback SDK is initialized or when your app is launched after it was closed before.
Conditions:
Show your campaign after the app has crashed a certain number of times. The App Crash event triggers as soon as the GetFeedback SDK is initialized or when your App is launched after it has crashed.
Conditions
Choose a date and time to show your campaign. The Specific Date event lets you set the occurrence number and the specific date. The occurrence number lets define how many times your app needs to be launched on the specified date before the event will trigger.
Conditions:
Most standard events show your campaign after the app has been launched. If you've created several campaigns with similar targeting options, you might have more than 1 campaign to show to the user.
When multiple campaigns are triggered, the SDK will make use of a so-called Campaign Trigger Queue. The queue prioritizes campaigns to make sure that only 1 campaign is shown per app launch.
The queue prioritizes campaigns based on a few factors:
It's best to limit the number of campaigns using identical standard events and similar targeting options.