Kumulos provides three ways to target who you are sending notifications to.
You can build audience segments to target specific users of your app by applying filters to data captured from the install, such as location (e.g. country and city), operating system (e.g. iOS or Android) and the version of the app (e.g. to encourage users to update).
You can use channels to categorize the content you send and let users subscribe to content relevant to them.
You can also define Geofences to target installs within a certain radius of a fixed point on a map (e.g. within 1000m of a retail outlet that is running a promotion).
Target specific users of your app by applying filters to data automatically captured from the install, such as location (e.g. country and city), operating system (e.g. iOS or Android) and the version of the app (e.g. to encourage users to update). By defining segments, you can easily send your users content that will be relevant and meaningful to them.
To add, edit and delete audience segments for an app, click on the app and then from the app dashboard for that app, expand push from the left menu, select "Targeting" and then select the "Segments" tab.
To define a new audience segment, click the primary action button. This will open the add segment dialog. Give the segment a descriptive name (as this is what your team and your client will see when sending targeted push notifications).
Next, select the filters that will be used to define your audience segment. From the Filter by drop down, you can choose to filer your audience by:
Coming soon, you will also be able to filter by the last time/date the app was active (in the foreground) and the number of sessions (time app was active in foreground) within a given date range.
Add multiple filters to define your audience segment. Filters are applied via a boolean and (i.e. an install must match all filters to be in an audience segment). As you add your filters you will be able to see how many installs your audience segment will currently target.
When done, click
Save to save your audience segment. Your segment will now be listed, showing how many filters define it and how many installs it is currently targeting.
Note that the number of installs targeted by a segments is dynamic and always updated when sending a push notification to a segment. In other words, when new users install your app, they are automatically included in the all audience segments whose filters apply to them.
Your clients can define audience segments from their client portal in exactly the same way.
Channels allow your users to subscribe to content based on their preferences. By defining either portal visible marketing groups or allowing your app to create private or public groups, channels allow you to target content at a receptive audience.
Defining channels via the agency console¶
To add, edit and delete channels for an app click on the app and then from the dashboard, expand push on the left menu, select "Targeting" and then select the "Channels" tab.
To create a new channel, click the primary action button. This will open the add channel form. Give the channel a descriptive name and a unique identifier.
You can optionally define a JSON object of meta data which will be returned to your app when requested from the API. This field can be used to provide additional filtering or information when rendering the channel within your app.
Note that channels must be subscribed to by an install, they will initially target no installs.
Notes on the visibility of channels¶
Channels created in the agency console are considered publicly available. They will be visible in the agency console / client portal and returned to any app requesting a list of channels from the SDK.
In order for a channel created via an SDK or the Push API to be visible in the agency dashboard for targeting notifications via the UI, it must be created with the
showInPortal flag set to true and will require a friendly name.
Any channel which has a friendly name is considered publicly available and so will be returned to an app requesting a list of channels, finer control of what channels are rendered can be achieved with metadata.
Channels with no friendly name are considered private and will not be returned to apps requesting a list of channels unless the requesting install is subscribed to it.
You can optionally provide a dictionary of meta data to be associated with the channel which will be returned to your app as part of the read request. This metadata can be used for any additional contextual information used by your app, such as any business rules regarding categorization or access control. For example: if you want to add a channel for a special offer or promotion ahead of time, you could add a start date in the JSON object that your app could use to determine when to present the channel to users of the app.
You can define Geofences to target installs within a certain radius of a fixed point on a map (e.g. within 1000m of a retail outlet that is running a promotion).
To add, edit and delete Geofences for an app, click on the app and then from the app dashboard for that app, expand push from the left menu, select "Targeting" and then select the "Geofences" tab. The map will automatically zoom to show all existing Geofences.
To add a geofence, click the primary action button. Type an address in the Search box. All matching results will be shown. Click on a result to drop a pin in the map at that location.
You can click the back arrow next to 'Add Geofence' to return to the search results. Once you have found the closest result, you can drag-and-drop the pin to fine tune the exact location.
Now, give the Geofence a meaningful name (this will default to the address) and enter a radius in meters. Radius must be within the minimum of 1 meter and maximum of 10000 meters (i.e. 10 kilometers).
Click "Save" when ready to add the geofence.
You can edit and delete a geofence by clicking on the context menu next to that geofence and selecting "Edit" or "Delete" as appropriate.
If you want to temporarily disable a Geofence, then clicking context menu next to that geofence and select "Edit", toggle the "Enabled" switch and click "Save".
This provides a very quick way to control which geofences can trigger automation rules.
Read on for more details of how to use Geofences with automation rules to target subscribers when they enter or exit a Geofence...