Overview

With the Portfolio feature, you can create powerful user segments by combining user data and behaviors from all the different apps and websites (called Projects) within your workspace. This allows you to build highly specific audiences for more effective, targeted campaigns.

The primary goal is to enable cross-targeting. For example, you can create a segment of users who are frequent shoppers on your Grocery app and then send them a promotional campaign from your Fashion Retail app.

Build a Multi-Project Segment

When you create a segment in a multi-project workspace, the process for filtering users differs slightly depending on whether you are using User behavior (events) or User property.

1. From the left navigation menu in the MoEngage UI, navigate to Segment > Create segment. The Create segment page appears.
2. Select Filter users by.
3. Click + User property or User behavior.
   

   info	Information Affinity segments are not supported in Portfolio-enabled workspaces.

4. Before selecting an attribute or event, use the Select Project list to choose the specific project you want to filter for.
   
5. Define the rest of your condition as usual. For more information, refer to Create Segments.
6. You can add multiple rules, each targeting a different project, using AND/OR conditions to build a cross-project segment.
   

Filter by User Behavior (Events)

When you filter by user behavior, the project drop-down menu will list all of your individual projects as well as a global Portfolio option.

• Filtering by a specific project: To find users who performed an event in a single project, select the specific project from the drop-down list, and then choose the event.
• Filtering at the portfolio level: Selecting the Portfolio option serves two main purposes:
  
  
  • To create an "OR" condition across all projects: For common events tracked across multiple apps (like Purchase or Added to Cart), selecting Portfolio finds users who performed this action in any of your projects. This is a shortcut that prevents you from having to create a separate rule for each project and combine them with "OR".
  • To access portfolio-only events: The only campaign events at the project level are for Push Notifications. To segment users based on these other campaign events, you must select Portfolio. Certain events are not yet associated with individual projects. Currently, this includes most campaign engagement events (for example, Email Opened, SMS Sent).

Filter by User Property

When you filter by user attributes (user property), you must first select a specific project. There is no Portfolio option in this list. After you select a project, the attribute list will display both global and project-specific attributes.

• Global attributes: These attributes are shared across all projects in your portfolio (for example, First Name). They appear without any special label.
• Project-specific attributes: These are attributes associated with a single project (for example, Last Seen for a particular app). You can identify them by the project name suffix that appears next to the attribute name, for example, Last Seen {Project name}.
  

This distinction exists because while all users are stored in a single database, their attributes can be stored either globally or at an individual project level.

Understanding Reachability

How reachability is calculated depends on where you are in the MoEngage dashboard. Understanding this concept is critical when working with multi-project segments.

Reachability in the Segment Builder

When you are on the Create Segment page, there is no context for a specific campaign project yet. Therefore, the reachability count shown here is a Global Reachability count. A user is considered "globally reachable" if they are reachable on at least one of the projects in your portfolio. For example, if a user has a valid push token for Project A but not for Project B, they are still considered globally reachable for push. The count you see reflects the total potential audience across all your projects that matches your rules and is reachable on at least one project.

Reachability in Campaign Creation

When you use your segment in a campaign, you must select one specific project to send the campaign from. Thus, the reachability count here becomes project-specific.

When you click Show Count in the campaign's Target Audience step, you will see two figures:

1. • Total Users: The total number of users who match your segment's rules, across all the projects you defined in your segment.
   • Reachable Users: The number of users from that total who are specifically reachable for the single project you selected for the campaign.
     
     Example: Your segment might find 10,000 users who match your rules across Project A and Project B. However, when you create a Push campaign and target it only to Project A, the final "Reachable Users" count might show 4,000 because it only includes users from the segment who have a valid push token for Project A.

Custom Segments

When you save a segment, it is stored at the Portfolio (workspace) level. It is not associated with any single project and can be used in campaigns for any of your projects.

Dynamic Attribute Comparison

You can create advanced segments by comparing attributes between different projects.

• User attribute comparison: Compare a user attribute from one project to an attribute from another project.

  Example: Find users where Project A - Loyalty Tier is equal to Project B - Loyalty Tier.

• Event attribute comparison: Compare an event attribute from one project to an event attribute from another project.

  For example, target users who triggered the Add to Cart event in Project B, where the Category attribute matches the Category from their Purchase event in Project A.

How This Affects the User Profile

On the Activity Info tab of a user's profile, you will see a combined feed of all events performed by that user across all projects. There is no filter to view activities for a single project. However, each event will have a Project attribute to show you which app or website the action came from.