Connector campaign is a versatile solution from MoEngage enabling you to execute a variety of use cases such as:
- Using for retrieving real-time data from MoEngage.
- Passing data to other owned or third-party analytics systems
In the scheme of things, MoEngage acts like a central hub for your data, to which you can plug and connect any system for the duration of your choice. Connectors give you the liberty to target users across all communication channels.
Navigation
- Navigate to MoEngage Dashboard.
- Use any one of the following options:
- On the All Campaigns page, click Create Campaign.
The Create Campaign page is displayed. - Click Create New > Campaign.
The Create Campaign page is displayed.
- On the All Campaigns page, click Create Campaign.
- Click Custom under Connectors.
- Click on any one of the following campaign delivery types:
- One Time
- Periodic
- Event-Triggered
For more information about delivery types, refer to Delivery Types.
Target Users
Teams
Organizations can have different teams as part of the organizational structure. Select the team that you belong to. For more information, refer to Teams in MoEngage.
Name of the campaign
Type the name of the campaign to manage and identify the campaign.
info |
Campaign Naming Guidelines The campaign name contains a minimum of five characters and a maximum of 256 characters. |
Campaign Tags
Select any five campaign tags from the drop-down list.
For more information, refer to Campaign Tags.
Select Audience
Select the Target Audience or the target segment for the campaign. You can use multiple filters to create the target audience.
All Users
This filter option allows you to send the campaign to all the users of the app. When you use this option, you cannot add multiple filters.
Use User Properties
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.
Use User Behavior
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
- Add Event attribute with a filter condition
- Provide the filter value/s to create a rule.
For more information, refer to Create Segments.
Use User Affinity
Affinity Segments are 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
- 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 time duration for the event execution.
- Click the Attribute button to add more attributes to the filter.
Use Custom Segment
Select the Custom Segment section then select the desired custom segment to create a rule.
For more information, refer to Custom Segments.
Trigger Criteria for Event-Triggered Campaign
When you select Event-Triggered Connector Campaign, you need to provide the user event conditions using which the campaign is delivered. The condition is based on the If-Then logic.
To define a condition, do the following:
- In the IF user section, do the following:
- From the Select User Actions drop-down, select the user action to filter and send the campaign based on the condition.
The filter is the primary filter condition. - Do one of the following:
- Click Add Attribute to add attributes to the filter.
- Click ADD AND FILTER to add another filter using along with the primary filter.
- From the Select User Actions drop-down, select the user action to filter and send the campaign based on the condition.
- In the THEN trigger the message section, do one of the following:
- 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 within which to send the campaign:
- Type the number and select the minutes or hours or days.
- Select Before or After the time.
- Select from the drop-down the IF condition.
- Select Immediately to send the campaign within the next 30 to 60 seconds.
Control Group
You can enable the control groups to which you want to send the campaign.
In the Enable Control Group section, click Global control to not send the campaign to all the users in the control group.
For more information about control groups, refer to Control Group.
Content
Configure Webhook URL or Target Connector URL. You can use the following methods:
- GET
- POST
- DELETE
Common for GET, POST and DELETE
Field | Description |
---|---|
Webhook URL | Provide the URL for the webhook to which you want to send the data. |
URL Parameters |
Provide the parameters for the API or if the URL has the parameters then the parameters are autofilled in the URL parameters field. Click KV pair to add another URL parameters. |
Headers |
Add the Headers for the webhook. Click KV pair to add another header. |
POST and DELETE Body Type
Configure the Body for your requests using the following options:



Personalization
You can also use personalized parameters using the @ symbol. You can use the tracked user attributes to personalize your connector requests. Use personalization to send an SMS to a user-specific Mobile Number or send user-specific data to a third-party system using MoEngage connectors.
(Optional) Running Test Campaigns
Test campaigns enable previewing the campaign on a test device to make sure your intended message is being conveyed in your desired way. You can test the campaign you have just created by selecting a custom attribute and providing the value for a test user.
Schedule and Goals
Delivery Schedule
Field | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
As soon as possible |
Sends the campaign immediately to the target users. |
||||||||
At a particular date and time |
Send the campaign at the specified time, time zone, or predicted time. Select one of the following:
|
Field | Description |
---|---|
At fixed time |
Follow these steps to send the campaign on a specific date and time.
|
Send in user time zone |
Follow these steps to send the campaign on a specific date and time within the time zone of the user.
|
Best time to send (Sherpa) |
Follow these steps to send the campaign based on the MoEngage intelligence determined date and time.
For more information, refer to the Best time to send. |
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 |
|
Supported formats for Date and Time Attributes
- Date/Time Format sent using MoEngage SDK
- Date/Time values sent in String formats as under:
- “EEE MMM dd HH:mm:ss Z yyyy”
- “EEE MMM dd HH:mm:ss yyyy zzz”
- “EEE, MMM dd HH:mm:ss yyyy zzz”
- “EEE, dd MMM yyyy HH:mm:ss zzz”
- “EEE,dd MMM yyyy HH:mm:ss zzz”
- “EEE, dd MMM yyyy HH:mm:sszzz”
- “EEE, dd MMM yyyy HH:mm:ss”
- “EEE, dd-MMM-yy HH:mm:ss zzz”
- “yyyy/MM/dd HH:mm:ss.SSS zzz”
- “yyyy/MM/dd HH:mm:ss.SSS”
- “yyyy/MM/dd HH:mm:ss zzz”
- “yyyy.MM.dd HH:mm:ss”
- “yyyy-MM-dd HH:mm”
- “MMM dd yyyy HH:mm:ss. zzz”
- “MMM dd yyyy HH:mm:ss zzz”
- “dd.MM.yyyy HH:mm:ss zzz”
- “dd MM yyyy HH:mm:ss zzz”
- “dd.MM.yyyy; HH:mm:ss”
- “dd.MM.yyyy HH:mm:ss”
- “dd.MM.yyyy zzz”
ZZZ - Represents the reported timezone
EEE - Represents Day of the Week e.g. Tue
MMM - Represents Month of the Year e.g. Jun
HH:MM:SS - Time that represents the hour of the day, minutes of the hours and seconds of the minute
DD:MM:yyyy and DD:MM:YY are the date formats as most commonly used
warning |
We do not support MM/DD/YYYY formats. In case if time-zone is not mentioned in your event property, it will be considered as UTC and notification will be sent accordingly. |
To sum up, Event-Triggered campaign is a great way to engage the right users (through segmentation) at the right time (through event triggering).
The campaign will be sent only when:
- The event property/attribute which is being used to create these types of triggers (like 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
Conversion Goals
Conversion goals help you to track your business metrics in relation to a campaign and help you measure how your campaign helped you achieve your business metrics.
You can choose any of the app events as a conversion goal activity and can 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 have made the Purchase event for Product iPhone. Your conversion goal set-up will look something like this. Here iPhonePurchase is the Goal Name; Made Purchase is the App Event that you want to track; product is event attribute/property which has value as iPhone
With multiple conversion goals, you can now track more than one business metric or can visualize a funnel for your user actions.
For example,
You to want to check:
- 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
Tracking Revenue Performance
With MoEngage, you can very easily track revenue for your campaigns. The Revenue and RoI of the campaigns are available to you. For example, you can answer the question of how much revenue my product made after sending a communication.
While setting the conversion goal, you can choose for which goal do you want to track the Revenue by enabling the 'Revenue performance' toggle. In the example below, to track the revenue for orderSuccessful events, enable the 'Revenue performance' toggle.
Revenue Tracking is optional and non-mandatory.
After you choose the goal, you can choose the numeric attribute which captures the total monetary value of the order. In the example below cartValue contains the total order value. You can also choose the currency in which your monetary value is being reported.
Set Attribution window
We also allow you to set an attribution window i.e. duration, calculated from the time at which the user 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.
Remove duplicate users
info |
Information Applicable to One-time and Periodic campaigns only. |
Select the user attributes using which you can delete the duplicate users.
Delivery Controls
Frequency Capping
library_add_check |
Prerequisites Ensure that you set the Frequency Capping. |
Frequency capping allows you to limit how many times connector data be sent for a user during a particular time period.
To enable Frequency Capping go to Settings-> SMS & Connectors and click FC & DND
Set the value to desired number. You can also choose to reset the Frequency Cap at 00:00 GMT daily. It is useful when you send your campaign late on a day and want to send an early morning campaign the other day. Do not forget to click on Save Button to save your changes.
How it works?
Say a marketer has set Frequency Cap as 2 in one day. In that case, connector data will be sent to a user a maximum of 2 times (combined total for scheduled as well as triggered deliveries) in a period of 1 day.
This value will be applicable to all the sent connector campaigns (with send type as Scheduled and Triggered).
You can choose to ignore the capping for your connector campaign by using Ignore Frequency Cap (toggling it to right). There might be a few cases where you might want to ignore the capping but want this campaign to be counted.
For example, assume you have a capping value of 3. You have already sent 3 campaigns today to a group of users. Now you realize that the SMS that is being triggered by this Connector campaign is urgent and should go on high priority even if some customers have already received 3 campaigns. If you will use Ignore Frequency Cap, people who have already received 3 campaigns will receive this one as well. If you use Count for Frequency capping, people who would have received 2 communications already and sent this as well, their receipt count will become 3 after this campaign is sent.
Event-Triggered Campaign Delivery Control
You can also decide the minimum delay between two requests made for a specific user fulfilling the trigger criteria.
The connectors can be triggered at any point of time. But we might want to restrict them in Sleeping hours or Do Not Disturb Hours. When you create an event-triggered campaign, then you set the do not disturb settings. For example, you want to trigger a connector request to SMS Provider when the user has done an App Open event but has not made a purchase within two hours of opening the App.
By default, these settings will be applicable to your Connector campaigns. You can choose to Ignore DND Settings for the campaign by clicking.
Request Limit
If you create a connector to send data for a segment of users at once (or at a scheduled time), we hit the request URL with a minimum of 100 requests per minute.
info |
Information If the estimated time to send the campaign exceeds 4 hours, we will automatically increase the requests per minute to finish sending in 4 hours. |
Next Steps