Skip to main content

​
Overview

The Portfolio feature centralizes all your projects in MoEngage, providing a unified view of your customers. This enhances how you segment, personalize, deploy, and analyze In-app campaigns across multiple applications. This article describes the impact of the Portfolio feature on the following key areas:
  • Target Specific Projects and Platforms
  • Cross-Project Segmentation
  • Personalization
  • Test Campaigns
  • Campaign Analytics and User Profile
To illustrate these concepts, we will follow a campaign for a company with two distinct brands: Project Alpha and Project Beta. The goal is to cross-promote the premium brand (Project Beta) to the loyal customers of the primary app (Project Alpha).
  • Before creating a In-app campaign, ensure that all necessary channel configurations are complete.
  • To leverage the Portfolio feature, you must add at least one project to your account. For more information, refer here.
  • If your portfolio contains multiple projects, a Project drop-down list appears on the campaign creation pages, enabling you to select and configure unique settings for each.

​
Target Specific Projects and Platforms

With the Portfolio feature, you can tailor messaging and offers to fit the unique context of each project. In this example, the goal is to encourage valuable customers from Project Alpha to try the Project Beta offer.
  1. In the Target Users step of campaign creation, locate the Target platforms section.
  2. In the Select Project list, select your target project (for example, Project Alpha).
  3. Select the Platforms checkbox(s), such as iOS and Android, to send the invitation to all potential devices for that brand. inapp portfolio target.png
For a complete walkthrough of the campaign creation steps, refer to our guide on Creating a In-app Campaign.

​
Cross-Project Segmentation

You can segment users based on their complete journey across your projects. This is essential for effective cross-promotion and lifecycle marketing. Example: Find high-value customers of Project Alpha who have not yet engaged with Project Beta. In the Target audience section, we will target users who have made a purchase from Project Alpha and have not yet opened the app for Project Beta. By following the steps mentioned below, you can configure this logic:
  1. In the Target audience section, select Filter users by and choose the User behavior tab.
  2. For the first rule, select Project A from the drop-down list and set the condition “Has Executed Made Purchase.” inapp audience portfolio 1.png
  3. Click + Filter to add a second rule. Select Project B and set the condition “Has NOT Executed App Opened.” inapp audience portfolio 2.png
  • Unlike Push notifications, cross-project triggers are not supported for In-app and OSM campaigns.For example, you cannot trigger an In-app message in Project Alpha based on an “Add to Cart” event occurring in Project Beta.
  • For these channels, the project selected for sending the campaign is automatically applied to the trigger condition, and cross-project trigger selection is unavailable.

​
Personalization

Personalization tailors messaging to the project you target, ensuring relevance. When you create a campaign for a specific project, MoEngage automatically filters the user attribute list to display only those from the target project and any global attributes. Example: For a campaign promoting Project Beta to Project Alpha customers, personalization uses data from Project Alpha. Even if a user has different profile details in Project Beta (such as a different “First Name” or “Loyalty Status”), the campaign correctly uses their Project Alpha information to maintain the brand context the user is currently experiencing.
  1. In the campaign’s Content step, type @ to open the list of personalization attributes.
  2. Select an attribute (for example, First Name) from the available Project Alpha or global attributes.

​
Test Campaigns

Test campaigns for In-app are context-specific and will only execute within the environment of the selected project.
  • When you initiate a test, the In-app message is triggered exclusively on the app and platforms (iOS/Android) associated with the project configured in the campaign settings.
  • This segregation ensures that a test for Project Alpha will not inadvertently display on the Project Beta app, maintaining the integrity of the user experience across your portfolio.

​
FAQs

MoEngage currently doesn’t support real-time cross-project triggers. This means an event in App A cannot immediately “pop” a message in App B.MoEngage suggests you use Cross-Project Segmentation as a workaround. You can build a segment in the Target Audience section where you filter for users who executed “First Purchase” in Project Basic within the last hour. Your Project Premium campaign will then be waiting for them the next time they launch that app.
No. Even though the Portfolio feature provides a unified view of the customer, Campaign Analytics are project-specific. If you run a cross-promotion, the impressions and clicks are tracked within the project where the campaign was deployed. This allows you to accurately measure which “Host App” is driving the most conversions for your “Target App.”
To keep your data clean and brand-specific, the personalization menu (@) only surfaces attributes belonging to the target project you selected. If you need to use data from Project Beta while drafting a campaign for Project Alpha, that specific attribute must be configured as a Global Attribute in your MoEngage settings.
No. Test campaigns for In-app are strictly context-specific. When you initiate a test, the message is triggered exclusively within the app and platforms (iOS/Android) associated with the project you configured in the campaign settings. Your test for Project Alpha will never interfere with the user experience in Project Beta.

​
Related Articles