In order to use Antsomi App Notification to engage your audience, please follow the instructions below:
Last updated
Create Antsomi App Push Destination
Antsomi App Notification destination will later be used in Customer Journeys, where you could configure the content and the targeted audience.
Please follow these step:
You can create only ONE destination with Antsomi App Push catalog
General Information
| Field's name | Description |
|---|---|
Destination Name | Name your destination as you want |
Description | Describe this destination. Usually, it would be the objective of this destination |
Destination Catalog | Choose the catalog "Antsomi App Push" |
Method | It is "Push" automatically |
Configure fields
| Field's name | Description |
|---|---|
User ID |
|
Advanced Push Settings (Optional)
Frequency Capping
Frequency Capping settings allows users to limit the times an audiences receiving a marketing message.
| Option | Description |
|---|---|
Ignore duplicate messages for the scheduled journey | One audience just receive one message in an iteration of journey schedule |
Limit frequency for the journey (3 months duration) | Limit allocation frequency to 1 audience in a journey for 3 months (Ex: 2 times/person) |
Limit frequency for destination | Limit allocation frequency to 1 audience per unit of time (hour, day, etc.) (Ex: 3 times/month, 1 times/day) |
To understand the meaning of these fields, read this article.
Select the templates you want to use to send to audience. By default, all templates are chosen.
The SDK selected here must match with the SDK on Firebase & Apple.
Click on the document linked and follow the instruction to install and test the destination
Follow the link to "Read the documentation" and copy Your App ID as this will be the ID that allows your mobile application to connect to the destination.
Do as the following to create a Blast Campaign using Antsomi App Push
If you want to trigger Journey by Action-based node, choose Journey Orchestration channel instead
STEP 1 - Settings
Campaign Name: Input the name of your campaign
Delivery Destination: Choose the destination you have just created above
Delivery Hours of the Day: Choose the time this notification will reach your audience
STEP 2 - Compose
2.1 - General Settings
| Field's name | Description |
|---|---|
Variant Name | Enter the name of the Variant |
Title | The title of the notification |
Subtitle | Subtitle of the notification (Apply to iOS Mobile Apps only) |
Content | The content of the notification |
Image URL | Image for the notification |
Launch URL | The URL to which the user will be redirected when clicking on the notification. |
2.2 - Platform Settings
Apple IOS
| Field's name | Description |
|---|---|
Badges | It's the circle containing numbers in the app icon. There are 3 options:
|
Sound | The sound that plays when the device receives the notification. If no sound is chosen, the device's default sound will play. |
Content Available |
|
Category | Your app’s registered notification categories. |
Target Content ID | Specify a specific experience in the App Clip or a specific window if the application has multiple screens. |
Notification Interruption Level | Define how and when the notification is displayed. Includes 4 options:
|
Relevance Score | It is the score set for each notification to indicate the order in which notifications will be displayed when grouped. The system uses values from 0 to 1 to sort messages. |
Google Android
| Field's name | Description |
|---|---|
Large Icon URL | The icon on the right side of Content. |
Small Icon URL | The icon displayed in status bar (on the top and left of content) unless Large icon is set (The bell icon is displayed by default) |
Category | When users receive a notification with a category, they can long-press on the notification or go to Notification Settings to change the category's settings. They will be given options to change Importance, Sound, Vibration, Badge, etc. or can opt out of future communications within the category if they so choose. |
Sound | The sound plays when receiving notification. Only apply to Android 7 and below. Android 8+ will take the default sound. |
Lockscreen Visibility | Control how notifications and content are displayed on the lock screen (Android API level 21 or higher and Android 5.0 or higher). Only applies to Android 7 and below with these following mode:
As for Android 8 and above, it will take the default settings |
LED Color | Set the device's LED notification light (if the user's device has one). If no LED Color is specified, the device's default color is displayed. |
Group Key | The key of a notification group (It includes related notifications with the same keyword so they can be collapsed together ) |
Group Message | A brief message for the group above. It will be displayed as a summary. |
Background Data | Choose if you want ro receive data in the background or not |
2.3 - Advanced Settings
| Field's name | Description |
|---|---|
Collapse ID | Enter the ID of the notifications you want it to be collapsed when there are many of them. Notifications with the same id/key will be replaced instead of displaying a completely new notification on the device. |
Priority | Set the priority of these notifications |
Time To Live | Set the time the notification is displayed if the device remains offline. After the set period, the notification will be expired |
Additional Data | Customize any value you want to have in the API |
Action Buttons | Add the button to the notification |
Action ID | The ID of the action which will occur if your audience click on the button |
Button Label | The label of the button |
Action icon path | The icon of the button |
Click Activate to start running the Journey
To understand the details of a trigger node, see here.
To add an attribute, click on button, and choose in the popup.
