The card campaign provides inbox notifications in the App Inbox or News Feed. Using this feed, your users can access the Card anytime and as many times as they want - over a period of time.
MoEngage provides a fully customizable App Inbox, which is integrative. The delivery, display, and management of the Card in the Inbox are taken care of by MoEngage. For more information, refer to the Android, iOS, and Web integration.
info |
Information If you are already using the MoEngage Inbox along with Push campaigns, please note that you will not be able to use that Inbox if you decide to use the Card campaign with the MoEngage provided Inbox. |
To create a Card campaign:
- Navigate to the MoEngage Dashboard and select Engage > Campaigns from the left navigation. The All campaigns page is displayed.
- At the top right corner, click + Create campaign.
- Under Inbound, click Cards.
Steps to Create a Card Campaign
The following are the steps to create a card campaign:
- Segmentation: Define the target audience for the campaign.
- Create view: Define the content of the card campaign to be sent.
- Scheduling: Define the campaign's delivery schedule and goals.
Step 1: Segmentation
This section contains the following:
Campaign details
The campaign details section contains the following fields:
|
Choose Platforms
Select the platform that you want to target: Android, iOS, and Web.
Trigger Criteria
Based on how you want the campaign to be triggered, select one of the following criteria:
Choose this option if you want to trigger a message to your target audience now or at scheduled time.
Allow Future Qualifiers
Select the checkbox to include future users who qualify the segment criteria at any time in the future. The following table shows the difference between a one-time campaign when the Allow Future Qualifiers checkbox is selected or not selected.
Allow Future Qualifiers is not selected | Allow Future Qualifiers is selected | |
---|---|---|
Use case | One-time campaigns that are aimed towards time based use cases targeted to a specific audience. | One-time campaigns that are long running where future eligible users can be added to the campaigns. |
Audience |
Cards are sent only to those users who have an active device tracked in MoEngage and are part of the segment at the time of sending the campaign. If a user who qualifies for the segment adds a device later, they will not see the card. |
Cards are sent to users who qualify the segment condition at the time of sending or who qualify the segment condition at any time in the future. For "All users" campaigns, the cards are sent even to anonymous users in their first session. Note: For such campaigns, if a user receives a card as an anonymous user, but is part of the exclusion criteria after logging in to the app, the user will still see the card that was shown when they were anonymous. For segmented campaigns, future users who qualify the segment criteria—even though they were not part of the segment at the time of sending the campaign—will see the card from the second session onwards. |
Analytics |
MoEngage considers the sent count based on the number of users with active device targeted at the time of sending the campaign. | MoEngage considers the sent count based on the number of unique users receiving the card campaign when it is delivered to them. |
Response time | Because there is no evaluation at the time of delivery, these campaigns are delivered to the app quickly on app open/fetch. | Because there is an eligibility evaluation at the time of delivery, it may take additional 1 second to fetch cards if the user has any card with the Allow Future Qualifiers flag set to True. |
Campaign expiry | The campaign expiry time starts from the time campaign is delivered to the logged-in user. |
If a user receives the card as anonymous, the campaign expiry time starts from anonymous delivery time. If a user receives the card after logging in to the app, the campaign expiry time starts from the time campaign is delivered to the logged-in user. |
Note: If you select this checkbox, the Global control group toggle will be disabled. Because these cards are visible to anonymous users, you cannot assign control groups to anonymous users.
Choose this option if you want to trigger a message to your target audience when an event is triggered. For example, when a user with a particular attribute views a product, a targeted Card message is triggered. The user’s action event can be tracked on the app or the server.
Event Triggered Campaigns
This section contains the event criteria that (when satisfied) will trigger the card campaign notification. To define the trigger condition, do the following under Select Trigger Condition:
- In the IF section,
- In the Select an event drop-down list, select the user action that needs to be performed to trigger the campaign. 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 section,
- Select Immediately to send the campaign within the next 30 to 60 seconds.
- Select With Delay and provide the following details to define the timeframe and the event criteria to be fulfilled to send the campaign:
- Enter the number and select the minutes, hours, or days.
- Select Before or After the time.
- Select the action to be performed by the user in the drop-down list for the if condition. The user must perform the actions added within the time specified in the delay criteria after performing the first action.
Choose this option if you want to trigger a message to your target audience on a recurring basis.
Select Audience
info |
Note This is applicable for "One-time" campaigns when the Allow Future Qualifiers checkbox is selected.
|
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. Click the User property tab and do the following:
- Select the desired attribute in the drop-down list. This enables 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 have different filters.
- Enter the filter value(s) to create the desired user segment.
- Click + Nested Filter to add a filter to create nested AND or OR conditions. (This is optional)
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. Click User Behavior and do the following:
- Select the execution condition and the desired user activity (event).
- Enter the event frequency and time duration for the event execution.
- Click + Attributes and add an event attribute with a filter condition.
- Enter the filter value(s) to create a rule.
-
Use the + Aggregation button to add the aggregation functionality. For more information, refer to Aggregation Operations.
-
Click + Nested Filter to add a filter to create nested AND or OR conditions. (This is optional)
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. Click 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.
- For a minimum of: Select affinity attribute with a filter condition and provide the affinity values.
- Most no. of times: Enter a value or use the arrows to provide the top percentage of users.
- Least no. of times: Enter a value or use the arrows to provide the bottom percentage of users.
- Enter or use the arrows to provide the time duration for the event execution.
- Click + Attribute to add more attributes to the filter.
- Click + Nested Filter to add a filter to create nested AND or OR conditions. (This is optional)
For more information, refer to Create Segments.
This filter option allows you to select a custom segment as the target audience.
- Select a custom segment as the target audience from the list of custom segments available.
- Click + Nested Filter to add a filter to create nested AND or OR conditions. (This is optional)
For more information, refer to Custom Segments.
After choosing the filter criteria, you can do the following as well:
-
Create Multiple Filters: You can 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: Select this checkbox to define the filter criteria for users to be excluded from the campaign.
Note: For one-time campaigns, if the Allow Future Qualifiers checkbox is selected, if a user receives a card as an anonymous user, but is part of the exclusion criteria after logging in to the app, the user will still see the card that was shown when they were anonymous. - Reset Filters: Click this option to reset the segmentation filters.
- Show Count: Click this button to display the total number of users who are currently in the configured segment.
Enable Control Group
This section contains information about enabling control groups for the campaign. To exclude users in the control groups, do the following:
In the Enable control groups section, enable the Global control group toggle to exclude the users in the control group from the campaign's target segment. For more information about control groups, refer to Control Group. Note: If you select the Allow Future Qualifiers checkbox for the "One time" trigger criteria, the Global control group toggle is disabled. Allocation of control group happens when the user is no longer anonymous. Because these cards are visible to anonymous users, you cannot assign control groups to anonymous users. |
Click Next to move to Step 2.
Step2: Create View
Before you enter your Card notification content, select Card Category and Template:
Card Category
If you have configured multiple tabs during the SDK integration process for setting up the Inbox, then you will see this field and all those tabs will be listed in this dropdown here. We are supporting a maximum of five tabs or Card Categories as of now, including the "All" tab.
Select an option or tab in which the Card should be delivered.
If you have also set up an "All" tab that contains all Card in an aggregated format, then all your Cards will also be visible in this tab by default. You need not select this option in the Category dropdown.
Template Type
You can choose from the two templates - Basic or Illustration, based on your use cases. If you want to send a simple message with more focus on text such as reminding your users about an offer starting next weekend with details such as "50% off on the summer apparel" along with your logo for quick brand recall, you can use the Basic template.
Whereas if you want your message to be richer - with more focus on an image or gif, such as an image that explains more details about the upcoming offer along with a brief text, you can use the Illustration template.
Configure Message
Configure this as per the message text that you want to communicate. You can also use emojis in all the message fields.
info |
Note
|
The various components of the message are:
i. Background Color
To make your message more appealing, you might want to add a background color to your notification. You can either choose a color from the color picker or add a hex code.
On the left-hand side, you will get a preview of the notification as you keep on adding content.
Please note that the actual notification might slightly vary from the Preview shown.
ii. Header
Represents the title or heading of the message that you want to send across. Only one line of Header text would be shown on the device depending on the device width, so please be careful with the character limit.
iii. Message
Represents the main message that you want to deliver to your audience. You can add up to three lines of text, which will be visible as per the device's width. More text will be visible on bigger devices whereas lesser text on smaller devices.
Note: You can apply some basic formatting to your Header and Title as well as change the text color. You can also use emojis in all the message fields. Use websites like Getemoji to copy and directly paste the emoji, anywhere in your header or message.
iv. Image
This enables an image to be shown on the Card. The image can be uploaded either via a) an URL or via b) uploading an image from the system. Supported formats are JPEG, PNG, and GIF. The maximum allowed size is 10 MB for both images and animated images.
- In the Basic template, you can upload an image as an icon or thumbnail.
- In the Illustration template, you can upload an image or gif in landscape mode (full-width image).
v. Card Action (Tap on the Card would)
It is the action that has to be performed when the user clicks anywhere on the Card except the CTA button. More details on CTA will be shared below.
Actions supported for Android and iOS
The supported actions are:
a) Navigate to a screen: Takes the user to a specified screen (selected from the drop-down or put screen name) on the click of the notification. Optionally, multiple Key-Value pairs can be added to take the user to specific parts of the page with relevant results. For iOS, you will have to enter the screen name manually
For example. you wish to offer discounts on Apple iPhone 11 Yellow, you need to specify the screen name as <product purchase screen> and send the key-value pairs (brand, Apple), (Model, iPhone 11), (Color, Yellow) so that you can display results relevant to the campaign
b) Deep-link: Takes the user to a deep-linked URL inside the app.
c) Rich landing: Takes the user to a mobile-optimized rich landing page (Web or Mobile Web)
info |
Note You can use key-value pairs to add additional information to the deep linking or Rich landing URLs. |
Actions Supported for Web
The supported actions are:
This option takes the user to the URL when they tap on the card.
vi. CTA
You can also add a CTA button that will take the user to a specific product page. To add a CTA, toggle ON the CTA option. Add the CTA text that will appear on the Card notification on the bottom right.
CTA Action
After adding CTA text, configure the CTA action which would take the user to the specific page or link once they click on the CTA link in the Card.
Supported actions for Android and iOS
CTA actions are the same as the Card Actions for Android and iOS explained above.
Supported actions for Web
CTA actions are the same as the Card Actions for Web explained above.
Note: You can use either one of the Card Action and CTA or both of them in a single campaign.
Test Campaign
The test campaign enables you to check the campaign on a test device to make sure that 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 its value for a test user.
Preview
The preview of how the cards will get rendered on the various platforms is available on the left side on the content creation page as shown below.
Basic Card Template
Illustration Card Template
Android Preview
Basic Card Illustration Card
iOS Preview
Basic Card Illustration Card
Web Preview
Basic Card Illustration Card
Click on 'See in web browser' to preview the card in the browser as shown below.
Step3: Scheduling
This section contains the following:
- Delivery Schedule: Choose when the campaign should be delivered to your users and the periodicity of delivery.
- Display Controls: Choose how or when the cards should be displayed in the Inbox.
- Conversation Goals: Set up the user event you want to track as the conversion goal.
Delivery Schedule
Choose this option to send the campaign immediately to the target users and end it on a specific date and time.
Note: The following fields are available in this section only if you have selected the Allow Future Qualifiers checkbox:
- Campaign time zone: the timezone in which the campaign should be sent.
-
Ends: the date on which the campaign should end. The following option is selected by default:
-
- On: the campaign ends on the end date specified in the End Date field.
-
- End date: the date on which the campaign should be stopped.
- End time: the time at which the campaign should be stopped. Select am or pm depending on when the time of day at which the campaign should be stopped.
Choose this option to send the campaign at the specified time, time zone, or predicted time.
This section helps you send the campaign on a specific date and time and end it on a specific date and time. The following fields are available in this section:
- Campaign time zone: 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.
Note: The following fields are available in this section only if you have selected the Allow Future Qualifiers checkbox:
-
Ends: the date on which the campaign should end. The following option is selected by default:
-
- On: the campaign ends on the end date specified in the End Date field.
-
- End date: the date on which the campaign should be stopped.
- End time: the time at which the campaign should be stopped. Select am or pm depending on when the time of day at which the campaign should be stopped.
- Campaign time zone: 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 the following options available on the left of the screen:
Periodicity | Description |
---|---|
Daily | Repeat every: This option allows you to specify the number of days after which the campaign should be repeated. |
-
Ends: the date on which the campaign should end. The following option is selected by default:
-
- On: the campaign ends on the end date specified in the End Date field.
-
- End date: the date on which the campaign should be stopped.
- Campaign time zone: 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.
- End date: the date on which the campaign should be stopped.
- End time: the time at which the campaign should be stopped. Select am or pm depending on when the time of day at which the campaign should be stopped.
Display Controls
Here, you set the Card expiry and other controls. Since Card is a persistent message and it will be visible to the user only when they open the app Inbox, you might want the Card to stay in the Inbox for a longer period.
1. Card expiry
This is a mandatory field. There are 3 ways you can set the Card expiry:
1. At a date and time: All the Cards will expire on this specific date irrespective of when different users received the Cards. After Card is sent, if a user has not opened the Inbox even once till this expiry date, then that user will never see this Card.
2. Days after the user has seen the card: You can define the number of days for which the Card would remain active in the Inbox after the user has seen a particular Card i.e. after the impression happened. The maximum limit for this field is 180 days.
3. Days after the card has been delivered to Inbox: You can define the number of days for which the Card would remain active in the Inbox after the Card has been delivered to the App Inbox. The maximum limit for this field is 180 days.
For example: As per the scheduling criteria set above, the Card campaign runs between 6th July and 30th September. And, the card expiry is set as 60 days after the card is delivered to the user's Inbox. Now, consider the scenario:
- The card is delivered to User 1 on 6th July. So, for User 1 this card will remain active for 60 days from 6th July i.e. till 7th September, and expire on 8th September
- The card is delivered to User 2 on 15th August. So, for User 2 this card will remain active for 60 days from 15th August i.e. till 15th October, and expire on 16th October.
Note: The default value for Card expiry is 30 days after the card is delivered to the user's Inbox.
2. The time window to show the Card
This option gives you the flexibility to decide whether, during the time the Card is active, should the user be able to see the card 24X7 or only during certain hours on the active days. By default, it will be set to "Throughout the day"
For eg. If you want to run an online lucky draw every weekend at 5 PM for 1 hour and give out coupons to the winners then you might want to show the card notification for this lucky draw between 4.55 PM and 6 PM.
3. Maximum times to show the card
This allows you to limit the maximum number of times a Card will be visible to the user. Let's assume that when a user clicks on a particular card, it takes them to a product page with a 10% discount auto-applied. As a marketer, you want to limit each user to avail of this discount only 3 times. So, you can set up the value of maximum times to show the card as 3. The card will expire once the user has seen the Card 3 times.
Note: This is an optional field. If no value is set, the card will remain active until the expiry time.
4. Pin the card to the top
If you want a particular card to get maximum user attention, then you can use the pin card option. Just select the Pin card to the top like this
A pinned card will appear at the top of the Inbox with a pin icon as shown in the image below. Also, at any time only one Card be shown as pinned. So, if there are 2 Cards with the pin option enabled, then the latest card will be shown as pinned.
Conversion Goals
Conversion goals help you to track your business metrics about 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.
E.g. Let us say, you want to track how many customers made the Purchase event for Product iPhone after you sent the campaign. Your conversion goal set-up will look something like this. Here iPhonepurchase is the Goal Name; Product Purchased is the app event that you want to track; prod_name is the event attribute/property with value as iPhone
Multiple Conversion Goals
You can add up to five conversion goals using the button. With multiple conversion goals, you can now track more than one business metric or can 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?
Attribution Window
We also allow you to set an attribution window which is the duration for which you want to attribute the conversion goals to a specific campaign. This duration is calculated from the time at which the user received the campaign. By default, it is set for 36 hours but you can set it to any duration lesser than 36 hours.
Note: The conversion goals and its attribution window are optional fields. You can disable them anytime by switching off the toggle button next to conversion goals.
Your campaign is now ready to be created. Click to confirm in the confirmation dialog and your campaign will be launched.
Upon successful campaign creation, you will be taken to the campaign info page where you can view the campaign performance stats and a brief campaign summary.
Next, you can know about the edit options for your campaign
Note: When the card campaign is sent, it means the Card is ready to be delivered to the user. The card will be delivered only when the user opens their app Inbox.