To create a push campaign:
- Navigate to the MoEngage Dashboard and select Engage -> Campaigns from the left navigation.
- Click at the top right corner of the All Campaigns Page.
- Select Push from the Outbound channels listed.
- Select one of the following campaign delivery types:
- One Time
- Periodic
- Event Triggered
- Business Event Triggered
- Device Triggered
- Location Triggered
For more information about delivery types, refer to Delivery Types.
Steps to Create a Push Campaign
There are three steps to creating a push campaign, and they are:
- Target users: Define the target audience for the campaign
- Content: Define the content of the push notification to be sent
- Schedule and Goals: Define the campaign's delivery schedule and goals
Step 1: Target Users
This section contains the following:
Campaign details
The campaign details section contains the following fields:
|
This section contains the event criteria that (when satisfied) will trigger the push notification. To define the trigger condition, do the following:
- In the IF user section,
- Select the user action that needs to be performed to trigger the campaign in the User Actions drop-down. This is the primary filter condition.
- Click + Attribute to add attributes to the filter. (This is optional)
- Click + ADD FILTER to add another filter with the primary filter. (This is optional)
- In the THEN trigger the message section,
- Select Immediately to send the campaign within the next 30 to 60 seconds.
You can send the campaign with only the If condition. - Select With Delay and provide the following details to define the timeframe and the event criteria to be satisfied to send the campaign:
- Type the number and select the minutes or hours, or days.
- Select Before or After the time.
- Select the action to be performed by the user in the drop-down for the if condition. The user has to perform the actions added within the time specified in the Delay criteria after performing the first action.
- Click Use Intelligent Delay Optimization to optimize the delay in real-time for the campaign to be sent after the user event conditions are satisfied. For more information, refer to Trigger delay optimization.
- Select Immediately to send the campaign within the next 30 to 60 seconds.
When to use event-triggered push campaigns?
-
Configuration without an event property
Set an Event-Triggered campaign to target users who have not purchased in the past 30 days; when the users abandon the cart and do not complete the purchase within the next 45 mins. The trigger condition for this scenario would be:
IF the user has executed the event 'Added to Cart' AND has not executed the event 'Purchase'.
Select the user/derived event in the IF condition and enter the event attributes. You can enter additional event attributes as well.
-
Configuration with an event property
With event triggers, you can trigger the push notification for specified values of the event attribute in your IF event. For instance, if you want to remind users who have booked a flight two hours before the flight time, you can create a trigger on the Flight Booked event using the event property Flight Time and set the notification to be sent two hours before the flight time.
-
Other examples
- Send discounts/reminders to your subscribers before the subscription expiry.
- Send communication minutes before a flash sale to shoppers who have registered for it.
- Send a reminder before customer travel date and time, cross-sell hotels/experiences/local transport or restaurant bookings.
- Remind customers to refill consumables.
For business event-triggered campaigns, you can select the business event to be mapped to the campaign using the Select business event dropdown. The dropdown contains all the business events created in your MoEngage account. |
Once the business event is selected, the event attributes associated with the business event are available in the segmentation filters. Business event attributes are available in the following segmentation filters:
- segment by user property - you can map the user property to the business event attribute
- segment by user behavior - you can map the attribute of an event executed by the user to that of the business event attribute
- segment by user affinity- you can map the attribute of an event executed by the user to that of the business event attribute
info |
Note
|
- Add the Geofence name.
- Select the trigger criteria from the user action drop-down to trigger the push message on entry/exit/stay inside the geo-fence. The following options are available:
-
- User enters the Geofence - A message will be triggered when the user enters the defined perimeter.
- User exits the Geofence - A message will be triggered when the user exits the defined perimeter
- Dwell based (user stays in Geofence) - A message will be triggered when a user enters and stays inside the defined perimeter for X mins. Please note that this type of trigger is supported only for Android. If your customers receive many alerts when driving briefly past your geofences, dwell-based fences are very effective in reducing this spam.
-
- Specify the Geofence by searching for the location. The Latitude and Longitude are auto-populated in this case. Alternatively, you can provide the following information to specify the geofence:
- Latitude
- Longitude
- Radius (in meters) - Enter an appropriate radius parameter for the geo-fence to be triggered. For example, if a geofence of 7 km is set around Foley Sq in New York, the push notification will be triggered based on the criteria chosen (entry/exit/dwell).
- Click the Done button to add the geofence. You can add multiple geo-fences with separate messages and locations for each. Remove a geofence by clicking the "x" sign in the geo-fence list.
Target audience
This section contains segmentation filters that help you choose the target audience for your campaign. The following options are available:
This filter option allows you to send the campaign to all the app users. When you use this option, you cannot add multiple filters.
This filter option allows you to target the users based on user properties such as first seen, last seen, city, and so on. Select the User property tab and do the following:
- Select the desired attribute in the dropdown. This will enable the filters based on the attributes chosen. For example, attributes that are numbers can have filter conditions such as 'is equal to', 'is not equal to', 'is between', and so on, while String attributes will have different filters.
- Provide the filter value(s) to create the desired user segment.
For more information, refer to Create Segments.
This filter option allows you to target the users based on the behavior of the user or event, such as app/site opened, viewed product, and so on. Select the User Behavior and do the following:
- Select the execution condition and the desired user activity (event).
- Provide event frequency and time duration for the event execution.
- Click +Attributes and add an Event attribute with a filter condition.
- Provide the filter value/s to create a rule.
For more information, refer to Create Segments.
This filter option allows you to target groups of users created based on the user performing an action with a specific attribute value. For more information, refer to User Affinity. Select User Affinity and do the following:
- Select the desired user event or attribute.
- Select the user affinity parameter from the following:
- Predominantly Select affinity attribute with a filter condition and provide the affinity values
- Minimum of Select affinity attribute with a filter condition and provide the affinity values
- Most no. of times Type or use the arrows to provide the top or bottom percentage of users
- Least no. of times
- Type or use the arrows to provide the top or bottom percentage of users Type or use the arrows to provide the time duration for the event execution.
- Click the Attribute button to add more attributes to the filter.
This filter option allows you to select a Custom Segment as the target audience from the list of custom segments available. For more information, refer to Custom Segments.
If teams are enabled for your account, the segmentation criteria specified for the team for which you are creating will get appended to the campaign with an AND condition. For more information, refer to Teams in MoEngage.
After choosing the filter criteria, you can do the following as well:
- Create and combine multiple user property rules, user activity rules, and custom Segment rules to create a complex user segment using this option.
-
- Click + Filter.
- Click AND or OR.
- Select the attribute or event and define the filter conditions.
-
- Exclude Users - Check the Exclude Users checkbox to define the filter criteria for users to be excluded from the campaign.
- Send campaign to the users opted out in preference management - Check this option to include users opted out in preference management for the campaign. For more information, refer to Preference Management.
- Reset Filters - Click this option to reset the segmentation filters.
- Show Count - Click Show Count to display the total number of users who are currently in the configured segment.
Target Platforms
This section lets you choose the target platforms for your campaign. The following options are available:
|
Control Groups
This section contains information about control groups for the campaign. To exclude users in the control groups, do the following:
|
Click Next or use the tabs on the top of the create campaign navigation to move to Step 2.
Step 2: Define Content
This section contains various templates that you can choose from to define the content of the push notification. Select one of the templates and follow the steps described in Push Templates.
MoEngage recommends that you verify your push message displayed in the preview and then click next to set the schedule and goals of the campaign.
Test campaigns enable previewing the campaign on a test device to ensure that your notification is conveyed in the manner that you desire.
You can test the campaign you created by selecting any of the following options and providing the value for the attribute chosen for your test user.
- Unique ID
- Email ID
- Mobile Number
- Google Advertising identifier
- iOS Identifier for advertising
- Device Push Token
- Custom Segment
Step 3: Scheduling and Goals
This section contains the following:
-
-
- Delivery Schedule - Choose when the campaign should be delivered to your users and the periodicity of delivery.
- Pre-compute audience - this is an optional configuration for time-sensitive campaigns.
- Conversion Goals - Choose the conversion goals and revenue metrics to be tracked for the campaign.
- Delivery Controls - Choose the advanced delivery control options such as throttling, frequency capping, and expiration settings for the notification.
-
Delivery Schedule
Send the campaign immediately to the target users.
Send the campaign at the specified time, time zone, or predicted time.
Select one of the following:
Field | Description |
---|---|
At fixed time |
This section helps you send the campaign on a specific date and time and contains the following fields:
|
Send in user time zone |
This section helps you send the campaign on a specific date and time within the time zone of the user and contains the following fields:
|
Best time to send (Sherpa) |
This section helps you send the campaign based on the MoEngage intelligence-determined date and time and contains the following fields:
For more information, refer to the Best time to send(BTS). |
- Campaign timezone - the timezone in which the campaign should be sent.
- Start Date - the date on which the campaign should be sent.
- Send Time - the time at which the campaign should be sent. Select am or pm depending on when the time of day at which the campaign should be sent.
-
Periodic - the periodicity of the campaign. You can choose from three options: Daily, Weekly, and Monthly, from the radio buttons available to the left of the screen.
Periodicity Description Daily Repeat every - This option lets you specify the number of days after which the campaign should be repeated. Weekly Repeat every - This option lets you specify the number of weeks for which the campaign should be repeated.
Repeat on - This option lets you specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
Monthly Repeat every - This option lets you specify the number of months for which the campaign should be repeated.
Repeat on - This option lets you do the following:
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
Note: If the selected date(s) doesn't exist in the month specified (as it is a shorter month), a campaign will be sent on the last date. (For example, if the 30th and 31st are selected and the month is February, one campaign would be sent on the 28th). - Days of week - Choose this option to specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
-
Ends - the date on which the campaign will end. The following options are available:
-
- Never - the campaign will be scheduled to run daily.
- On - the campaign will end on the end date specified in the End Date field.
- After - the campaign will end after the number of occurrences specified in the occurrences field.
-
- Campaign timezone - the timezone in which the campaign should be sent.
- Start Date - the date on which the campaign should be sent.
- Send Time - the time at which the campaign should be sent. Select am or pm depending on when the time of day at which the campaign should be sent.
-
Periodic - the periodicity of the campaign. You can choose from three options: Daily, Weekly, and Monthly, from the radio buttons available to the left of the screen.
Periodicity Description Daily Repeat every - This option lets you specify the number of days after which the campaign should be repeated. Weekly Repeat every - This option lets you specify the number of weeks for which the campaign should be repeated.
Repeat on - This option lets you specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
Monthly Repeat every - This option lets you specify the number of months for which the campaign should be repeated.
Repeat on - This option lets you do the following:
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
Note: If the selected date(s) doesn't exist in the month specified (as it is a shorter month), a campaign will be sent on the last date. (For example, if the 30th and 31st are selected and the month is February, one campaign would be sent on the 28th). - Days of week - Choose this option to specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
-
Ends - the date on which the campaign will end. The following options are available:
-
- Never - the campaign will be scheduled to run daily.
- On - the campaign will end on the end date specified in the End Date field.
- After - the campaign will end after the number of occurrences specified in the occurrences field.
-
-
Send if the user time zone has passed - if the campaign's start time has passed in the user's timezone, you have the option to do the following:
-
- Yes, send it - send the campaign to the user even if the specified start time has passed in their timezone.
- No, don't send it - do not send the campaign to the user as the specified start time has passed in their timezone.
-
Choose this option to send the campaign on a specified date and time. The following fields are available in this section:
- Campaign timezone - the timezone in which the campaign should be sent.
- Start Date - the date on which the campaign should be sent.
- Send Time - the time at which the campaign should be sent. Select am or pm depending on when the time of day at which the campaign should be sent.
- Send messages based on best time only till - the time until which the campaign should be sent based on the best time to send (BTS). Select am or pm depending on when the time of day at which the campaign should be sent. Click View best time distribution to see the best time for sending push notifications represented in a graphical manner.
-
If user's best time is outside this time window - lets you choose when the campaign is to be sent when the user's BTS is outside the time window selected. You can do the following:
-
- Send the campaign to the user either at the start or end time by selecting Send message at start time or end time.
- Avoid sending the campaign to the user by selecting Do not send message.
-
-
If user's best time is not available - lets you choose when the campaign is to be sent when the user does not have BTS. You can do the following:
-
- Send the campaign to the user at the start time by selecting Yes, send at start time.
- Send the campaign to the user at the app's best time by selecting Yes, send at the app's best time.
- Avoid sending the campaign to the user by selecting Do not send message.
-
-
Periodic - the periodicity of the campaign. You can choose from three options: Daily, Weekly, and Monthly, from the radio buttons available to the left of the screen.
Periodicity Description Daily Repeat every - This option lets you specify the number of days after which the campaign should be repeated. Weekly Repeat every - This option lets you specify the number of weeks for which the campaign should be repeated.
Repeat on - This option lets you specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
Monthly Repeat every - This option lets you specify the number of months for which the campaign should be repeated.
Repeat on - This option lets you do the following:
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
Note: If the selected date(s) doesn't exist in the month specified (as it is a shorter month), a campaign will be sent on the last date. (For example, if the 30th and 31st are selected and the month is February, one campaign would be sent on the 28th). - Days of week - Choose this option to specify the day(s) of the week on which the campaign is to be sent (For example, if you wish to send the campaign every Monday, Wednesday, and Friday, select these days in this option).
- Days of month - Choose this option for repeating campaigns that are date specific. Select the date(s) of the month the campaign is to be sent(For example, to send the campaign on the 5th and the 25th of a month, select the 5th and 25th in the calendar widget.).
-
Ends - the date on which the campaign will end. The following options are available:
-
- Never - the campaign will be scheduled to run daily.
- On - the campaign will end on the end date specified in the End Date field.
- After - the campaign will end after the number of occurrences specified in the occurrences field.
-
Field | Description |
---|---|
Campaign Time Zone |
Select the campaign time zone in which the campaign is sent |
Start Date |
Set the start date at which the campaign is sent. |
Send Time |
|
End Date | Set the end date at which the campaign is stopped. |
End Time |
|
When will event triggered campaigns be sent?
The campaign will be sent only when:
- The event property/attribute which is being used to create these types of triggers (like the flight_time example), is in a valid date-time format. If it is not in date-time format, the string should have data in one of the supported formats. If the selected attributes do not contain data in any of these formats, the campaign won't be sent to your users.
- The date/time value from the attribute is greater than the time at which the trigger condition is fulfilled
- The date/time value from the attribute is less than 30 Days + the time at which the trigger condition is fulfilled e.g. If your trigger condition is fulfilled at date D, your notification will be sent only when the attribute value is less than D+30
- The Intelligent Delay Optimization does not work for campaigns sent on the relative timing.
Field | Description |
---|---|
Campaign Time Zone |
Select the campaign time zone in which the campaign should be sent. |
Start Date |
Set the start date at which the campaign should be sent. |
Send Time |
Set the send time at which the campaign should be sent. Select AM or PM |
End Date | Set the end date at which the campaign should be stopped. |
End Time |
Set the end time at which the campaign should be stopped. Select AM or PM |
When will business event-triggered campaigns be sent?
The campaign will be sent only when:
- The data type(s) of the user attribute(s) or event attribute(s) mapped to data type(s)the business event's attribute(s) match.
- The attribute(s) used in segmentation is passed in the trigger request for the business event.
- The Intelligent Delay Optimization does not work for campaigns sent on the relative timing.
Field | Description |
---|---|
Campaign Time Zone |
Select the campaign time zone in which the campaign is sent |
Start Date |
Set the start date at which the campaign is sent. |
Send Time |
|
End Date | Set the end date at which the campaign is stopped. |
End Time |
|
Location campaigns are started as soon as the campaign is created and are triggered when a user satisfies the location/radius criteria. The campaign's frequency can be limited by setting an upper cap on the number of times to display the message in a defined time interval.
Location triggered campaigns have the option to include time-bounds. The following options are available for Time bound for Geofences:
- Limited -The user will get a notification only between specified time intervals for a time zone. Multiple time bounds can be entered here (for example, cover both evening and morning times).
- Always - This
Pre compute Audience
This option lets you pre-compute the target audience for time-sensitive campaigns with complex segments and unusually high volumes and ensure that campaigns are sent faster and at exactly the scheduled time to the target users, without even a few seconds of delay. For more information, refer to Pre-Compute Segments and send Push at the right time.
Conversion Goals
You can add conversion goals to track the business metrics for your campaigns. You can track up to five conversion goals. You can choose any app event as a conversion goal activity and set more than one conversion goal. The first goal will be treated as a primary goal.
For example, if you want to track the number of customers who've purchased an iPhone after your campaign was sent. (Event - purchase event, Product - iPhone). Your conversion goal set-up might look similar to the image shown below with the following details:
-
-
- Goal Name - iPhonePurchase
- App Event you wish to track- Made Purchase
- Event Attribute/Property - product is event attribute/property
- Value of Event Attribute/Property - iPhone
-
With multiple conversion goals, you can track more than one business metric or visualize a funnel for your user actions. For example, if you want to check the following, you can do so with multiple conversion goals.
- How many users have viewed the product page?
- How many of them added that product to the cart?
- How many of them made a successful order?
With MoEngage, you can track the revenue generated by your campaigns. For example, you can track the revenue generated by your product after sending a communication. To track revenue performance, enable the Revenue Performance toggle for the conversion goal for which you want to track the revenue.
In the example here, to track revenue for orderSuccessfulevents, the Revenue performance toggle needs to be enabled. After choosing the goal, you can select the numeric attribute that captures the order's total monetary value. In the example below, cartValue contains the total order value. You can also choose the currency in which your monetary value is being reported. |
After you choose the goal, you can choose the numeric attribute which captures the total monetary value of the order. In the example, cartValue contains the total order value. You can also choose the currency in which your monetary value is being reported. |
Set Attribution window - You can set an attribution window ( a time period or window that is calculated from the time at which the user has received the campaign, for which you want to attribute the conversion goals to a specific campaign.) As a default, it is set for 36 hours. Say, for the example above, we set it to 5 hrs. |
Delivery Controls
This section contains the following options:
- Ignore frequency capping - Enable this toggle to ignore the frequency capping settings. For more information, refer to Frequency Capping.
- Ignore global minimum delay - Enable this toggle to ignore the settings for the minimum delay set for Push notifications.
-
Throttle -Set the throttling for Push notifications. For more information, refer to Push Throttling.
info Information
With the reduction in the default FCM API rate limits to 600,000 RPM, we are changing the maximum allowed throttle speed for Push notifications to 500,000 RPM to ensure a single campaign does not breach the project limit. This change will apply to new and existing campaigns. You may still see drops because of multiple campaigns being triggered together. For more information, refer to Changes in Sending Speed with Private Key Configuration.
This section contains the following options:
|
|
Advanced Settings
The following options are available in this section:
Expiration Settings - let you specify an expiry value for the push notification. This section contains information about when to stop sending push notifications (after a specific time duration mentioned) for the iOS and Android platforms. |
To set the push expiry value, the following options are available here:
- Expire notifications after - set the expiration duration in this field.
-
Remove notifications from inbox after - If you use the Notification Center (Inbox) feature of the MoEngage SDK, you can specify the duration after which the notification should be removed from the Inbox. The duration can be set in days or hours. By default, the value will be set to 30 days.
info Note
The Inbox Expiry feature is available in the following SDK versions:
-
- iOS - version 3.6.0 and above
- Android- version 7.7.13. For SDK versions below 7.7.13, inbox expiry can be set using the gcm_msgttl key(set the value in this format: yyyy/MM/dd HH:mm:ss).
In Android, use both the Inbox Expiry setting and the gcm_msgttl key if you have a user base in SDK version below 7.7.13 as well as at SDK version 7.7.13 or above.
-
Priority - choose this option for time-critical notifications. The following options are available:
|
|
Your campaign is now ready to be sent. Click Publish and confirm in the dialog box that opens up to create the campaign.
The Campaign Info page will be displayed once the campaign has been created successfully.