3. Under **Inbound**, click **In-app**. The In-App campaign creation page appears. 
# Create an In-App Message Campaign
To create an In-App message campaign, follow these steps:
1. [Target users](#step-1-target-users): Define the audience for your campaign.
2. [Content](#step-2-content): Design the message content.
3. [Schedule and goals](#step-3-schedule-and-goals): Set the delivery schedule and track campaign performance.
## Step 1: Target Users
### Campaign Details
The **Campaign Details** section includes:
* **Campaign name**: Enter a name to easily identify and manage your campaign. The campaign name must be between 5 and 256 characters.
* **Campaign tags**: Select up to five tags from the drop-down list. Tags help you organize and filter campaigns. For more information, refer to [Campaign Tags](/user-guide/campaigns-and-channels/getting-started/introduction/campaign-tags).
### Select Platform
In the **Target platforms** section, select the required platforms where your In-App message should display.
Under **Select trigger time**, select **Immediately** to send the message as soon as the campaign is published, or select **After Delay** to send the message after a specified time.
Under **Select screen/In app context**, you have the following options:
* **Any screen (Earlier on app open)**: The message appears as soon as the app opens on any screen where *showInApp()* or *showNudge()* is explicitly called. If these methods are not present on the initially opened screen, the message does not display until the user navigates to a screen where these methods are called. For instance, if your app has ten screens and you have added the methods to five screens, the message displays on every screen where these methods are added. Add relevant delivery controls to your campaign to prevent the message from appearing on all screens where the methods are present. For more information on delivery controls, refer [here](#delivery-controls).
* **Specific screens**: After selecting **Specific screens**, configure the screens or app context based on the platforms you selected. For your In-App message, you can configure either the screen, the app context, or both.
* **Screen**: An application can contain multiple screens, such as login, home, product, and checkout screens. Under the **Android** and **iOS** tabs, choose where the In-App campaign should display. Select screens from the **Screen is any of** list. You can select a maximum of five screens. This is an OR condition, so the message displays on any one of the selected screens.
* **App context**: A context is a section or part of a screen where you can display messages. For example, a podcast screen can have two contexts: *For you* and *All episodes*. To display the In-App campaign on the desired app context, add the context name in the **App context is any of** field. This is an OR condition, so the message displays on any one of the app contexts. For more information on context, refer to [Android](/developer-guide/android-sdk/in-app-messages/in-app-nativ) and [iOS](/developer-guide/ios-sdk/in-app-messages/in-app-nativ).
Under **Select trigger time**, select **Immediately** to send the message as soon as the campaign is published, or select **After Delay** to send the message after a specified delay.
#### **IF user**
In this section, select the event condition for your In-App campaign. MoEngage sends the In-App campaign if a user performs this event. You can add multiple events and attributes.
1. From the **Select an event** list, select the event.
2. Beginning with In-App Android SDK version 8.1.0 and In-App iOS SDK version 5.0.1.1, you can add multiple OR conditions within events by clicking **+ Trigger**. For example, display the In-App message to users who have clicked in-app on mobile at least one time.
You can also refine the custom event:
1. Click **+ Attributes** to add attributes to the filter.
2. From the **Select attribute** drop-down list, select the attributes and the logical drop-downs for the selected attribute.
3. To add more attributes:
4. Click **+ Attribute**.
5. Click **AND** or **OR**.
6. From the **Select attribute** list, select the attributes and the logical drop-downs for the selected attribute.
For instance, if you select the event *User installs the app*, you can add the attribute *App Version* to filter for users who installed a specific version of the app.
#### **AND then**
You can add more customization with the **AND then** feature. In addition to the **+ Trigger** option, the **+ Filter** button enables you to string multiple events together.
For instance, you can select the *In-App Clicked Android* event and then use the **AND then** option to add the *Added to Cart* event.
By doing this, the In-App campaign displays to users who have clicked an In-App campaign on their mobile device at least once AND then proceeded to add an item to their cart at least once.
You can also define the time to wait before the event in the **Filter** condition evaluates. Setting this limit to 15 minutes implies that the user must perform the **Filter** event within 15 minutes of performing the first trigger event. In this example, the first event is *In-App Clicked Android*. You can set a maximum delay of 24 hours and a minimum delay of 1 minute here.
If you click **+ Filter** again, you can add another event to the trigger criteria. You get the option to choose *AND* or \*OR.\*Combine the two filter conditions by choosing *AND,* or use the \_OR\_to filter users if they perform any of the events within the time limit.
#### **THEN**
In the **THEN** section, under **Trigger the message**, select an option to define when to display the message. The available options are:
* **Immediately**: The message displays immediately after the trigger criteria are met.
* **After Delay**: The message displays after the defined delay.
**Trigger criteria summary**: This section summarizes the trigger based on the events and attributes you select, making it easier to understand the trigger criteria.
* **Reset filters**: Click this option to clear all segmentation filters.
* **Show count**: Click this button to display the total number of users currently in the configured segment.
## In-session Attributes
In-session attributes enable you to group and target users based on their actions within the current app session. For example, use in-session attributes to display onboarding flows exclusively to new users visiting your app for the first time. This method ensures that these users receive a customized experience immediately during their initial session.
To add an in-session attribute:
1. Click the **+ In-session attributes** button and select the required attribute from the list. 
2. Use **And**/**Or** to combine multiple in-session attributes. 
3. Select the **Exclude Users** check box to exclude users based on their in-session activity.
You can use the following in-session attributes with your In-App campaign:
* **Query Parameter**: This attribute segments users based on query parameters in the Uniform Resource Locator (URL). Typically, users land on your personalized URL by clicking an advertisement on any social media platform.
* You can use UTM parameters to segment users based on their source or the campaign that led them to the URL.
* UTM parameters like *utm\_source* identify campaigns driving users to websites. You can use UTM and custom parameters to segment users and personalize their experience.
* **User Type**: This attribute segments users based on whether they are new or returning. The SDK stores user details (*unique\_id*) for each user in the app storage. A user is considered a *Returning User* if the associated user details exist in the SDK data storage. Otherwise, the user is considered *New*. If the user clears the app cache, they are considered new.
* Note: If two users (User 1 and User 2) use the same device and User 2 logs in after User 1, User 2 is considered a returning user.
* **Day of the Week**: This attribute segments users based on the day of the week they visit your app.
* **Time of the Day**: This attribute segments users based on the hour of the day they visit your app. You can choose from any of the one-hour slots available in the list.
* **GeoLocation**: This attribute segments users based on their geolocation when they visit your app. You can choose the country, state/region, and city where the user is located or exclude a specific country.
### Control Group
This section provides information about control groups for the campaign. Control Groups are enabled only for promotional campaigns. They are not applicable for transactional campaigns. Enable control groups to which you want to send the promotional campaign.
| | |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| In the **Control group** section: 
|
Click **Next** or use the tabs at the top of the campaign creation navigation to proceed to Step 2: **Content**.
## Step 2: Content
The following options are available to add content for your campaign:
* [**Prebuilt and saved templates**](#prebuilt-and-saved-templates)
* [**Start from scratch**](#start-from-scratch)
### Prebuilt and Saved Templates
This option enables you to choose a template from the following categories: **All** (chosen by default), **Pre-built**, **Saved templates**, and **API templates**.
In this section, you can perform the following actions:
1. Search templates: Enter the template name in the **Search templates** bar.
2. Filter templates: Use the following options to filter templates:
* * **Filter By Type**: Filter templates based on pre-built types (e.g., Nudges, Carousel, Pop-up).
* **Filter By Use Case**: Filter templates based on their purpose (e.g., Promotional, Feedback, Survey).
* **Filter By Content**: Filter templates based on their content (e.g., text-only, buttons).
* **Filter By Editor**: Filter based on the editor that supports the template (Native, HTML, or Self Handled).
Pre-built Templates
#### Template Settings
| Field | Description and action |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Background color | Select the **Background color** option and define the background color of the message. |
| Phone background color | Select and define the background color of the phone or device. |
| Image | Do one of the following:
For more information about testing campaigns, refer to [Testing In-App Campaign](/user-guide/campaigns-and-channels/in-app-message/create/preview-in-app-template-in-your-phone).
With multiple conversion goals, you can track more than one business metric or visualize a funnel for your user actions. For example, use multiple conversion goals to check:
* How many users viewed the product page?
* How many added that product to the cart?
* How many made a successful order?
|
| | |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| After choosing the goal, select the numeric attribute that captures the order's total monetary value. In this example, *cartValue* contains the total order value. You can choose the currency in which your monetary value is reported. | 
|
| | |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Set Attribution window**: Set an attribution window (a time period or window calculated from when the user receives/clicks the campaign, for which you want to attribute conversion goals to a specific campaign). By default, it is set for 36 hours, while the maximum attribution window can be set up to 10 days. In the example below, the attribution window is set to 5 hours. | 
|
### Campaign Priority
Set a priority for your In-App campaign as **Critical**, **High**, **Medium**, **Normal**, or **Low**.
### Delivery Controls
You can select the following options for your In-App Campaign:
* **Limit the maximum number of times a user can see messages from this campaign to**: Control campaign frequency by entering how many times to display the message. **Note**: Frequency capping works at the device level, not the user level. This means if your user logs on to two devices at once, they receive the campaign on both devices even if the frequency setting is set to 1.
* **Add a minimum delay between two messages of this campaign**: Add a minimum delay between two messages to control the frequency and timing of displaying In-App messages to the user. This setting is disabled for Nudge Templates.
* **Ignore frequency capping**: Enable this toggle to ignore the frequency capping limit for this In-App campaign. For more information, refer to [Frequency Capping](/user-guide/settings/channels/delivery-controls/frequency-capping). **Note**: Support for frequency capping is available from In-App Android SDK version 9.8.0 and In-App iOS SDK version 7.04.0.
* **Count for frequency capping**: Enable this toggle if you want the In-App message to be included in the overall frequency capping, allowing you to monitor the total number of messages delivered to the user. 
* **Ignore global minimum delay**: Enable or disable global minimum delay settings for this particular campaign.
* **Auto Dismiss message after**: This option dismisses the In-App message after a specified duration (in seconds). After the specified time, the In-App message is dismissed even if the user does not perform any action on it.
