Create Connector Campaign

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.


  1. Navigate to MoEngage Dashboard.
  2. Use any one of the following options:
    1. On the All Campaigns page, click Create Campaign.
      The Create Campaign page is displayed.
    2. Click Create New > Campaign.
      The Create Campaign page is displayed.
  3. Click Custom under Connectors.
  4. 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


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.


Campaign Naming Guidelines

The campaign name contains a minimum of five 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

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 property such as first seen, last seen, city, and so on.

Select the User Properties and do the following:

  1. Select desired user property and filter conditions.
  2. Provide the filter value(s) to create a rule.

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:

  1. Select the execution condition and the desired user activity (event)
  2. Provide event frequency and time duration for the event execution
  3. Add Event attribute with a filter condition
  4. Provide the filter value/s to create a rule.

For more information, refer to Create 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:

  1. In the IF user section, do the following:
    1. 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.
    2. Do one of the following:
      1. Click Add Attribute to add attributes to the filter.
      2. Click ADD AND FILTER to add another filter using along with the primary filter.
  2. In the THEN trigger the message section, do one of the following:
    1. Select Immediately to send the campaign within the next 30 to 60 seconds.
      You can send the campaign with only the If condition.
    2. Select With Delay and provide the following details within which to send the campaign:
      1. Type the number and select the minutes or hours or days.
      2. Select Before or After the time.
      3. Select from the drop-down the IF condition.

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.


Configure Webhook URL or Target Connector URL. You can use the following methods:

  • GET
  • POST


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.


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:

Form JSON Raw Body
Create the body based on the form-encoded serialization for the webhook. Click KV pair to add more form-encoded body.


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

One-time Periodic Event Triggered
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.

  1. Select the campaign time zone
  2. Set the start date 
  3. Set the send time at which the campaign is sent.CreateSMS_SendAtFixedTime.png
  4. Select AM or PM
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.

  1. Select the campaign time zone
  2. Set the start date 
  3. Set the send time at which the campaign is sent.CreateSMS_SendInUserTimeZone.png
  4. Select AM or PM
  5. Select Yes, send it to deliver the campaign in the time zone
    Select No, don't send it to not deliver the campaign in the time zone.
Best time to send (Sherpa)

Follow these steps to send the campaign based on the MoEngage intelligence determined date and time.

  1. Select the campaign time zone
  2. Set the start date 
  3. Set the start time at which the campaign is sent.CreateSMS_BestTimeToSend.png
  4. Select AM or PM
  5. Set the time until which the campaign is sent to users. (Send messages based on best time only till)
  6. Select AM or PM
  7. Click View best time distribution to see how the best time is distributed in a graph.
  8. Select Send message at start time or end time to send the campaign outside of the user best time.
    Select Do not send message to not send the campaign.
  9. Select Yes, send message at 2:28pm to send the campaign in the set time when the user in not available during the best time.
    Select send at the app best time to send the campaign based on the set best time in the app.
    Select Do not send to not send the campaign.

For more information, refer to the Best time to send.

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:

  1. How many users have viewed the product page
  2. How many of them added that product to the cart
  3. How many of them made a successful order

ConversionGoals.pngTracking 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 



Applicable to One-time and Periodic campaigns only.

Select the user attributes using which you can delete the duplicate users.


Delivery Controls

Frequency Capping



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. 




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


Was this article helpful?
6 out of 9 found this helpful