Overview

The Portfolio feature enables you to manage multiple applications (apps) and websites as individual Projects within a single, unified MoEngage workspace. This feature is designed for enterprises that manage multiple digital properties (for example, different brands or operations in multiple countries) and wish to consolidate their user data and marketing efforts. By bringing all your apps and websites into one workspace, you can create a unified view of your customers, unlocking powerful capabilities for analysis, segmentation, and engagement.

Use Cases

Adopting a Portfolio structure helps marketers solve several critical business challenges:

• Unified customer view: Consolidate user data from all your apps and websites into a single, comprehensive profile for each user, allowing you to understand the complete customer journey.
• Cross-brand segmentation: Build powerful audience segments based on user behavior across different projects. For example, you can identify customers active in multiple sub-brands and send a single loyalty campaign rewarding their cross-brand engagement.
• Cross-project trigger campaigns: Trigger a campaign from one brand to suggest a similar product when a user abandons their cart on another. For example, you can target buyers from one product line with complementary offers from another (cross-sell), or trigger a reactivation offer when a user becomes inactive in one app but remains active in another (churn prevention).
• Centralized campaign management: Manage and deploy Push Notification campaigns to any of your projects from a single dashboard, streamlining your operations.
• Holistic analytics: Gain a portfolio-level understanding of user engagement, conversion, and campaign performance across all your digital properties.
• Controlled user communication: Manage communication frequency (Frequency Capping) and Do Not Disturb (DND) hours for users across your entire brand portfolio to prevent message fatigue. For example, you can ensure you send only the single most relevant breaking news push from the most appropriate app, avoiding redundant notifications.

Manage Your Portfolio

A Project is a single app or website in your portfolio. Your workspace can support approximately 20 projects.

Add Project

1. On the left navigation menu in the MoEngage UI, click Settings > Account > Portfolio.
   
2. On the Portfolio page, click + Add Project.
   
3. On the Add a new Project window, enter the following values:
   

   Field	Description
   Project Name	This field specifies the name for the new project. It is mandatory. The name must contain 5 to 25 characters and can only include letters, numbers, and the underscore symbol (_).
   Project Icon	This field specifies the icon to represent the project. It is optional. For correct visibility on MoEngage, ensure to upload an image with a minimum resolution of 72x72 pixels. Supported file types are: PNG GIF WebP ICO CUR BMP
   Type of Business	This field specifies the business model for the configured project. It is mandatory. The available options are: Offline / Storefront Online
   Platform(s)	This field specifies the platform(s) for the configured project. It is mandatory and is visible only when the Type of Business field value is set to Online. Supported platforms are: Android iOS Web Note: The initial platform selection is for representation and initial setup. It does not lock the project to that platform; you can add and configure settings for other platforms later.

4. Click Save.
   You can now see the project details on the Portfolio page.
   

Analyze Project

The Portfolio page offers a comprehensive overview of all configured projects, enabling detailed analysis of project-related information. You can view the following details:

• Project Icon: Specifies the icon associated with this project. A default icon is shown if no custom one is uploaded.
• Project Name: Specifies the unique name assigned to this project.
• Project ID: Specifies the unique ID automatically generated for the project, used to direct incoming data.
• Platform(s): Specifies the target platform(s) for the project (for example, iOS, web, or Android).
• Last Updated By: Displays the date and the user who last modified the project. Project modification permissions are based on the app configuration level. For more information, see Permission Levels.
• Created By: Specifies the user who originally created the project and the creation date.

Edit Project

To edit a project, perform the following steps:

1. Navigate to the Portfolio page, search for the relevant project row.
2. Click the Ellipsis () icon against the preferred entry, and then click Edit.
3. On the Add a New Project window, make the required changes. 
4. Click Save.

Impact of Portfolio On

The Portfolio feature changes how you interact with key areas of MoEngage.

Data and User Profiles

The Portfolio feature centralizes your data and user profiles, allowing you to manage attributes and events at both the project and portfolio levels. This feature has the following impact on data ingestion and management in MoEngage:

• Portfolio and project-specific attributes: MoEngage enables project-level tracking of custom, standard user attributes, and events.
  • Standard attributes such as basic details, including First name, Last name, Mobile number, and other such standard attributes, are tracked as portfolio-level standard attributes.
  • Custom user attributes can be tracked at both the project and portfolio levels.
  • Standard and custom events are tracked at the project level.
    To understand user attributes tracked at the project and portfolio level, refer to Derived User Attributes Behaviour.
    
• User profile view: For users who exist in more than one project, a drop-down menu appears on their profile page, allowing you to view their attributes and activity for each specific project.
• Data management: The Data Management section provides a portfolio-level overview of unique events and user attributes. This allows you to manage data across projects, with a default limit of 1024 unique events and 1024 unique user attributes for the entire portfolio.
• Data ingestion: You can ingest data into the portfolio using Data APIs and SDKs.

For more information, refer to Portfolio: Data Ingestion and Management

Segmentation

The segmentation tool allows you to build rules that span multiple projects. You can combine behaviors from different apps and websites to create highly specific audiences for cross-targeting.

• Cross-project rules: When building a segment, a Project drop-down list appears for each rule, allowing you to filter users based on behavior in one project and attributes in another.
• Portfolio-level filtering: For user events, you can select Portfolio to find users who performed an action (like Purchase) in any of your projects, creating a broad "OR" condition.
• Reachability calculation: It is important to understand that the reachability count shown in the segment builder is a global count (users reachable on at least one project). When you use that segment in a campaign, the count becomes project-specific, showing only users reachable for the single project you are sending the campaign to.

For more information, refer to Segmentation in a Multi-Project Portfolio.

Push Settings

The Portfolio feature centralizes key configurations to ensure your Push campaigns are always brand-consistent and contextually relevant through the following capabilities:

• Project-specific configurations: Apply unique settings for Mobile App Push, Web Push, and Push Previews to each project individually within your portfolio.
• Contextual personalization: Maintain brand consistency by automatically filtering available user attributes during campaign creation to only show data relevant to the sending project.

For more information, refer to Portfolio for Push Campaigns.

Campaigns

The Portfolio feature unifies customer data across multiple projects to enhance how you segment, personalize, and analyze campaigns through the following key capabilities:

• Project-specific targeting: Control which project sends a campaign to ensure all branding and deep links are contextually correct for that specific brand. This is only supported for the Push channel. 
• Cross-project segmentation: Create precise audiences by building rules that combine user behaviors and attributes from any of your associated projects.
• Cross-project trigger campaigns: Trigger a campaign from one project based on a user's real-time actions in another, enabling automated cross-promotional strategies.
• Individual project analytics: Analyze and compare push notification opt-in rates for each project separately using unique reachability attributes. This is only supported for the Push channel. 
• Aggregated reachability: Determine a user’s overall reachability based on their status across all projects. A user is considered reachable if they are opted-in to notifications from at least one project.

For more information on the channel-specific support matrix of the Portfolio feature, refer to Supported Features by Channel.

Global Frequency Capping

The Portfolio feature enables you to manage communication frequency across your entire brand portfolio. This prevents message fatigue by setting a Global Frequency Capping that limits the total number of communications a user receives from all your projects.

• You can set a master frequency capping at the portfolio level. This limit is enforced on a per-user basis and applies to the total number of communications sent from all projects within the workspace.
  For example, if a global capping is set to five communications, a user in three different projects will receive a maximum of five communications combined across all three brands.
• While the global capping controls the overall volume, tag-based frequency capping allows for more granular, project-specific control.
  For example, to limit messages from a specific project to three, you can:
  • Add a unique tag to all campaigns running for that specific Project.
  • Set a frequency capping rule that limits communications with that specific tag to three.

For more information, refer to Frequency Capping.

Supported Features by Channel

The availability of key Portfolio features, such as reachability and cross-project triggers, varies by communication channel. The following table lists the features supported for each channel.
*Not Supported: Portfolio user interface elements are unavailable for these channels on the workspace.

FAQs

Related Articles

• Portfolio: Data Ingestion and Management
• Segmentation in a Multi-Project Portfolio
• Portfolio for Push Campaigns
• Create an Event-Triggered Campaign