---
title: "Portfolio: Conduct cross-project analysis in Amplitude"
description: Create Portfolio views to analyze users across multiple Amplitude projects.
product: general
token_estimate: 1146
---
# Portfolio: Conduct cross-project analysis in Amplitude

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Portfolio merges data from multiple Amplitude projects into a single cross-project view, showing each user's complete journey across every project you connect to it. Use Portfolio when your analysis needs to span more than one project, such as tracking a user across separate iOS and Android projects. If your analysis stays within a single project, use that project instead of Portfolio.

> **Note:** Portfolio project limits
>
> Portfolios support an unlimited number of projects. Amplitude limits User Streams within portfolios to five projects. If your use case requires more, contact your account team to unlock up to 10 projects for User Streams.

## Plan availability

Portfolio (cross-project views) is available on the Growth and Enterprise plans. Go to [Amplitude pricing](https://amplitude.com/pricing) for plan details.

| Plan | Allowance | How to access |
| --- | --- | --- |
| Free | Not included | [Upgrade your plan](https://amplitude.com/pricing) |
| Plus | Not included | [Upgrade your plan](https://amplitude.com/pricing) |
| Growth | Limited 2 projects per portfolio | Included in plan |
| Enterprise | Included | Included in plan |

_Availability reflects the latest Amplitude plans. If your organization is on an older plan, your access may differ. Check your plan under [Plans & Billing in your organization settings](/docs/admin/account-management/account-settings#organizational-settings), or contact your Amplitude account representative._

## How it works

Portfolio uses Views for cross-product analysis. Views are collections of Amplitude Projects or data sources that merge activity from each project into a single display. A View with one or more data sources lets you analyze users across multiple projects at once.

> **Note:**
>
> Views can't ingest data themselves, but you can update them at any point.

Amplitude assumes that the same user ID or device ID in different projects belongs to the same user.

However, Amplitude stores user properties on a per-project basis. User properties on events triggered in a particular project use the user property values for that project only.

For example, you have two projects named `iOS` and `Android`. One user has a user property called `Version`, with a value of `1.0` in the iOS project and a value of `2.0` in the Android project. Events triggered by this user in the iOS project have `Version` set to `1.0`. Events triggered in the Android project have `Version` set to `2.0`.

> **Note:**
>
> If an event type has the same name on two or more projects, Amplitude considers it to be the same event in the dropdown.

Amplitude supports cohort export for portfolio projects for all destinations. When you select Amplitude User Property, the export includes only `device_id` and `user_id`.

## Create a Portfolio view

Admins and managers in an organization can access and create the Portfolio view by clicking the **Settings** icon and navigating to _Organization settings > Projects > Create Portfolio View_. In the modal, name the portfolio view and set user permissions.

To connect multiple projects into this cross-project view, click **Update Source Projects** and select the projects to merge into a single view.

## User mapping (aliasing)

User IDs for the same user can differ across projects within the same organization. The [User Mapping API](https://amplitude.com/docs/apis/analytics/user-mapping) endpoint lets you merge two users that Amplitude would otherwise identify by different user IDs. You can only map users through the API.

In the following example, the User Mapping API merges three user records with different user IDs into the user ID `mike@hooli.com`. This new user ID is the user's "global" user ID in the cross-project view. This mapping provides an accurate count of unique users across your product portfolio.

![Portfolio user mapping merging three user IDs into one global user ID](https://amplitude.com/docs/images/account-management/360003724891.png)

When Amplitude maps users, it doesn't merge user properties. This means the user properties attached to each event are those from the original user who triggered the event in the first place.

Read more about accessing the User Mapping (Aliasing) API, mapping, and unmapping users in [User Mapping (Aliasing) API](https://amplitude.com/docs/apis/analytics/user-mapping#user-mapping).