Portfolio for Push Campaigns

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 Push campaigns across multiple applications and websites.

This article describes the impact of the Portfolio feature on the following key areas:

Target Specific Projects and Platforms
Cross-Project Segmentation
Cross-Project Triggered Campaigns
Personalization
Analyze Opt-In Rates by Project
Portfolio and Project-level Reachability
Reachability in the User Profile

To illustrate these concepts, we will follow a single campaign from a company with two distinct brands: Project A and Project B. The campaign's goal is to cross-promote the premium brand to the loyal customers of the primary app.

library_add_check

Prerequisites

Before creating a Push 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 on how to add projects, refer here.
The following push settings pages support project-specific configurations:

If your portfolio contains multiple projects, a Project drop-down list appears on the above-mentioned pages, enabling you to select and configure unique settings for each. This drop-down list is not displayed for single-project portfolios.

Target Specific Projects and Platforms

With the Portfolio feature, you can now tailor messaging, deep links, and offers to fit the unique context of each project, ensuring a consistent user experience.

In the following example, the goal is to encourage valuable customers from Project A to try out our new offer.

In the Target Users step of campaign creation, locate the Target Projects/websites section.
In the Project list, select your target Project (for example, Project A).
Select the target platform(s) checkbox(s), such as iOS and Android, to send the invitation to all potential devices for that brand.

For a complete walkthrough of the campaign creation steps, refer to our guide on Creating a Push Campaign.

Cross-Project Segmentation

You can segment users based on their complete journey across your projects, not just their behavior within a single one. This capability is essential for effective cross-promotion and for understanding the complete customer lifecycle.

In the following example, the goal is to find high-value customers of project A who have not yet engaged with project B.

In the Target audience section, select Filter users by and choose the User behavior tab.
For the first rule, use the project drop-down list to select project A and set the condition "Has Executed Made Purchase." This finds your valuable customers.
Click + Filter to add a second rule. Select project B and set the condition "Has NOT Executed App/Site Opened."

Cross-Project Triggered Campaigns

You can use customer behavior in one project to trigger campaigns in another. This allows you to create sophisticated, automated cross-promotional strategies that respond to user actions in real-time. By connecting user actions across your entire portfolio, you can guide customers toward discovery and increase overall conversions.

In the following example, a user adds an item to their cart in Project A but doesn't complete the purchase. This inaction can trigger a campaign from Project B, suggesting a similar or alternative product.

In the Target Projects & Platforms section, select Project A as the project that sends the campaign.
Under Trigger Criteria, set the IF user condition to an event from Project B, such as "Has executed AddtoCart atleast 1 time in the last 3 days".
Add an AND condition to further qualify the user, such as "For Project B Has not executed Purchased".
In the THEN trigger the message section, set the timing. This configuration sends the message from Project A two days after the user adds an item to the cart in Project B, but does not complete the purchase.

The following image illustrates this trigger configuration:

For more information on how to create an Event-Triggered Campaign, refer here.

Personalization

Personalization tailors messaging to the project you target, ensuring relevance and accuracy. 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. This approach prevents using data from one brand context in another, maintaining a consistent user experience.

Example: For the campaign promoting Project B to Project A customers, personalization uses data from Project A. Even if a user has different profile details in Project B, the campaign correctly uses their Project A information, maintaining brand context.

In the campaign's Content step, type @ to open the list of personalization attributes.
Select the First Name attribute from the available Project A or global attributes.
The message, "Hi @User Attributes.First Name! An exclusive offer awaits," now correctly uses the name the user provided for Project A.

For more information on Personalizing Push Campaign, refer here.

Analyze Opt-In Rates by Project

The Portfolio feature stores reachability as a project-specific attribute. This allows you to analyze and compare push notification opt-in rates for each project individually, helping you understand user sentiment and the effectiveness of your permission prompts on a per-project basis.

For iOS, Android, and Web, you can now analyze platform-specific opt-in rates by filtering users based on new project-level user properties.
In the Filter users by section of Analytics, select the user property corresponding to the project and platform you wish to analyze.
These attributes follow the format [Attribute Name] [Platform] [Project Name], allowing you to create precise segments and visualize each project's opt-in performance. For example: Reachability Push Android Project A.

Portfolio and Project-level Reachability

A user's portfolio reachability is an aggregated status that determines if they can receive communications.

A user is considered reachable at the portfolio level if they are reachable in at least one associated project. This requires that at least one of their devices is reachable for communications within that project.
MoEngage first evaluates reachability at the project level and then aggregates those results to determine the final portfolio status.

Example Scenarios

Consider two users, each with multiple devices and associated with two different projects. The following table outlines their device statuses.

User	Project ID	Device	Device Status	Project-Level Reachability	Portfolio-Level Reachability
User 1	A	Device A	Reachable and opted in	Reachable and opted-in for Project A	Reachable and Opted-In
	A	Device B	Not reachable due to Opt-out	Reachable and opted-in for Project A
	B	Device A	Not reachable due to Opt-out	Not Reachable due to Opt-out for Project B
	B	Device B	Not reachable due to Opt-out	Not Reachable due to Opt-out for Project B
User 2	A	Device C	Not reachable due to Opt-out	Reachable and opt-in status unknown for Project A	Reachable and Opt-in status unknown
	A	Device D	Reachable and opt-in status unknown (for old SDK versions)	Reachable and opt-in status unknown for Project A
	B	Device C	Not reachable due to Opt-out	Not Reachable due to Opt-out for Project B
	B	Device D	Not reachable due to Opt-out	Not Reachable due to Opt-out for Project B

Analysis and Final Portfolio Status

User 1: This user is considered Reachable at the portfolio level.
Reasoning: Although the user is not reachable in Project B, their Device A is opted-in for Project A. This single instance of reachability in one project makes their overall portfolio status "Reachable."

User 2: This user is considered Reachable at the portfolio level.
Reasoning: Although the user is not reachable on three of the devices, their Device D is reachable, with an opt-in status unknown for project A. Therefore, the overall portfolio status for user 2 is "Reachable."

For a comprehensive explanation of how all reachability statuses are calculated, refer to the following guides:

Reachability in the User Profile

The Reachability section within a user's profile now provides a consolidated view of their status. Alongside the overall portfolio status, you can also see the specific reachability status for each individual project the user is associated with. This includes:

Portfolio-level reachability: The user's aggregated reachability status across all projects.
Project-level reachability: The user's specific reachability status for each individual project.

User info reachability.png

FAQs

arrow_drop_down Which user attributes are available for personalization in a project-specific Push campaign?

You can use all user attributes associated with the project you are sending from, as well as any global attributes that apply to the user across your portfolio. MoEngage automatically filters out attributes from other projects to ensure brand consistency and data accuracy.

arrow_drop_down If a user has different attribute values (like 'First Name') across multiple projects, which value will be used in my Push notification?

The Push notification will always use the attribute value from the project you are sending the campaign from. This ensures the message is always in the correct brand context.

arrow_drop_down What happens if I send a Push campaign to a segment of users who have never used the app or website of the sending project?

No one in that segment will receive the campaign. To receive a Push notification from a specific project, a user must have installed the app or visited the website for that project and opted-in to receive notifications, thereby generating a push token.

arrow_drop_down Can I use a cross-project segment as an entry trigger for a Flow that sends Push notifications?

No. Currently, cross-project segmentation and triggers are designed for direct campaign creation. Advanced features like Flows do not support cross-project data for audience entry.