This article explains data ingestion, management, and viewing within a MoEngage workspace where the Portfolio feature is enabled. This feature centralizes your data and user profiles, allowing for seamless management of user attributes and events across all projects. This article covers:

• Data ingestion: How to ingest data using Data APIs and Data Warehouse while specifying the relevant project.
• Data management: How data, events, and user attributes are managed and presented within a Portfolio-enabled workspace, including a breakdown of unique event and user attribute limits.
• User profile view: How user data is displayed at both the portfolio and individual project levels.
• Derived user attributes: How derived user attributes (for example, LTV, First Seen) are calculated and displayed at both the project and portfolio levels.

Data Ingestion

You (or your development team) can ingest data into a Portfolio-enabled workspace using:

• Data APIs
• Data Warehouse

Data APIs

In MoEngage, data ingestion uses a unique ID to update a user attribute or event. For portfolio-enabled workspaces, you (or your development team) can use Data APIs (such as the Track User, Create Event, and Bulk Import APIs) to pass a projectID. This ID identifies which project a user or event belongs to. You can find the Project ID at Settings > Account > Portfolio in your MoEngage dashboard.

Use case
A brand has separate apps for "Brand A" (Project 1) and "Brand B" (Project 2). When a user downloads both apps, the Portfolio feature uses Data APIs or SDKs to ingest all their data. The projectID attribute identifies which brand the data originates from, ensuring all events and user attributes are associated with the correct project while being unified under a single user profile.

The following is a sample cURL request of a Data API with projectID passed in the API endpoint:

curl --location 'https://api-0X.moengage.com/v1/customer/{{APP_ID}}&{{projectID}}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic {{Authorization_Key}}'\
--data-raw '{
        "type": "customer",
        "customer_id": "{{customer_id}}",
        "attributes": {
        "name": "John Doe",
        "first_name": "John",
        "last_name": "Doe",
        "age": "67",
        "email": "2uV4@xyz.com",
        "gender": "male",
        "mobile": "{{mobile}}",
        "geo": "88.90 89.00",
        "birthday": "02-12-2001",
        "created_time": "1756198118474",
        "last_seen": "1756198118474",
        "userdata": "insert",
        "revenue": 100,
        "transaction": "100",
              "platforms": [
              { "platform": "iOS",
                 "active": "true"          
                     }         
                    ] 
                  }
        }'

Data Warehouse

The Portfolio feature enhances your data warehouse integration, giving you the flexibility to manage data correctly within your multi-project portfolio. This allows you to leverage your existing backend data for both brand-specific analysis and holistic customer understanding.

MoEngage handles different data types as follows:

• Event attributes are ingested at the project level, allowing you to attribute specific actions to the correct brand.
• User attributes are ingested at the portfolio level, and updates are applied to the user's global profile across all your brands.

Event Attributes (Project-Level)

For accurate analysis and segmentation in a portfolio, it is crucial to associate every event with a specific project. To achieve this, you must map a column from your data source to the dedicated MoEngage attribute: moe_project_name.

Example Scenario:

Let's assume you manage two brands: Project A (a sports app) and Project B (a shopping app). Your data table contains a column named `brand` with values like "Project A" or "Project B" for each event.

During data warehouse setup, you would map your brand column to the MoEngage event attribute moe_project_name. This directs MoEngage to automatically assign each event to the correct project based on the value in that column.

Ingest User Attributes (Portfolio-Level)

Conversely, any user attributes you import are always applied at the portfolio level. This updates the user's single, global profile and is not tied to a specific project. The process is the same as for non-portfolio accounts, requiring you to map standard columns like `User ID` and `Updated at`.

For a complete step-by-step guide on the import configuration, please refer to our Data Warehouse import guides.

Data Management

A Portfolio-enabled workspace has the following details at Settings > Data > Data Management:

• The Overview tab displays the total number of unique events and user attributes for the entire portfolio. While you can pass events and user attributes between projects, the portfolio-level limits remain fixed by default: 1024 unique events and 1024 unique user attributes. Ensure the total sum of unique events and user attributes across all projects does not exceed these limits. This simplifies the process of tracking total unique events and attributes across your entire business, ensuring you stay within the fixed limits.
• The Events and User attributes tabs provide a holistic view of events and user attributes across all projects. You can use the Select project list to filter the list and view data for specific projects.
  
  
  
• For standard and custom events: MoEngage automatically adds the moe_project_name event attribute to all ingested events, specifying the project they originate from. For instance, a Purchase event from Project1 includes the attribute moe_project_name with a value of Project1.
  
  
  
• For standard user attributes: MoEngage adds the project name as a suffix to both the Display name and Key name of the user attribute. For instance, the display and key name for the custom_attr_2 user attribute from newproject is custom_attr_2_newproject.
  
  
  
• For custom user attributes: MoEngage adds the project name as a suffix to the Key name, and the Display name remains the same as passed by the user without any suffixing. For instance, the key name for the custom_attr_2 user attribute from newproject is custom_attr_2_newproject, and the display name is custom_attr_2.

User Profile

When Portfolio is enabled, the User Info tab in a user profile displays information at both the portfolio and project levels. For example, a user who interacts with both "Brand A" and "Brand B" will have a single profile where you can view their total LTV Portfolio, which is the sum of their LTVs from both projects.

In a user profile, you can view the following details at the portfolio level:

• First Name
• Last Name
• Email (Standard)
• Mobile Number (Standard)
• MoEngage ID
• ID
• Lifecycle
• Conversion
• Acquisition
• Reachability
  

You can view User Properties for a specific project by selecting the project from the drop-down menu.

Derived User Attributes Behaviour

The following table lists the derived user attributes tracked at the project and portfolio level:

FAQs