Portfolio: Conduct cross-project analysis in Amplitude
With Portfolio, you can build a holistic view of how your users interact with your entire product portfolio. If you've instrumented multiple platforms or product lines, Portfolio can show your users' complete journey across projects.
Portfolio project limits
Portfolios support an unlimited number of projects. User Streams within portfolios are limited to five projects. If your use case requires more, contact your account team to unlock up to 10 projects for User Streams.
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.
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.
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 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, three user records with different user IDs are merged 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.
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.
Was this helpful?