---
title: "Keep consented and non-consented data in separate projects"
description: "Route consented and non-consented data to separate Amplitude projects, restrict user-level access on the non-consented project, and report across both with Portfolio."
product: data
lang: en
last_updated: 2026-11-20
token_estimate: 1823
---
# Keep consented and non-consented data in separate projects

If you collect both consented analytics data and a limited non-consented measurement stream, always keep them in separate Amplitude projects. This page supports [Collect limited anonymous measurement](https://amplitude.com/docs/data/privacy-and-consent-implementation/limited-anonymous-measurement), one of the three methods in the [privacy and consent overview](https://amplitude.com/docs/data/privacy-and-consent-implementation).

> 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`.

Mixing the two streams into a single project creates problems that are difficult to untangle later. Three reasons to be strict about this from the start:

- **Reporting integrity**: non-consented data uses minimized or rotating identifiers, so user-level metrics like uniques, funnels, and cohorts behave very differently from your consented data. Keeping them separate makes it clear which numbers mean what.
- **Risk of unintended user stitching**: Amplitude resolves identity at the organization level, not the project level. If the same user ID or device ID appears in both projects, Amplitude treats them as the same user. If you didn't design your non-consented project with this in mind, you may inadvertently link anonymous data to identified users across projects.
- **Access control**: the non-consented project should have tighter controls. Disabling individual user-level event lookup keeps analysis at the aggregate level, and that's much easier to enforce when the data is already in its own project.

## Set up the two projects

[Separate projects](https://amplitude.com/docs/admin/account-management/manage-orgs-projects) let you configure the non-consented stream differently from the start. A common setup looks like this:

- One project for consented users, where full analytics begins after consent.
- One project for non-consented users, where you send only the limited anonymous measurement events your policy allows.

Use the stricter setup in the non-consented project: no cookies, no persistent storage, no stable user ID, and a minimal event set.

When a visitor hasn't consented, route the allowed events to the non-consented project. If the visitor later gives consent, initialize Amplitude with the consented project and begin normal tracking there.

Make your identity strategy intentional in both projects. Across projects in the same organization, Amplitude assumes that the same user ID or device ID refers to the same user. That's useful for legitimate cross-project analysis, but it also means you should avoid reusing identifiers across consent states unless that matches your legal and implementation model.

> **Note:** When a non-consented user gives consent mid-session
>
> If a visitor arrives without consenting and later grants consent on the same visit, handle the transition explicitly:
>
> 1. Stop sending to the non-consented project. After the user grants consent, stop routing events to the anonymous measurement project.
> 2. Initialize Amplitude with the consented project key. Call `amplitude.init()` with your consented project's API key and, if the user is now identified, set their `userId` at this point.
> 3. Don't attempt to retroactively link pre-consent activity to the now-identified user, unless your legal model explicitly allows it. The anonymous events from before consent should stay anonymous.
>
> This keeps a clean boundary: pre-consent activity stays in the anonymous project with no stable identity, and post-consent activity begins fresh in the consented project under the user's real identity.

## Restrict user-level access where appropriate

For some teams, separating projects isn't enough on its own. They also want the project that contains non-consented data to have tighter access to user-level views.

In those cases, review whether features such as [User Lookup](https://amplitude.com/docs/analytics/user-data-lookup), user profiles, user streams, or similar user-level surfaces should remain available for that project. This matters most when the project contains anonymous or non-consented data and your privacy posture is meant to avoid individual-level exploration.

As a practical rule, many teams want a stricter setup for the non-consented project and a more standard setup for the consented one. If you need that kind of project-specific restriction, discuss it with your Amplitude team as part of the implementation design so they apply the right controls for your organization.

### Disable User Lookup at the project level

Alongside Data Access Control and RBAC, Amplitude supports disabling the User Lookup feature at the project level. When your Amplitude team enables this setting, team members can't access individual user event streams from contextual menus in charts and dashboards, such as the microscope icon that opens a user's event stream.

This control matters most when your privacy posture requires analysis to happen at the aggregate level only, and you want to prevent access to raw individual-level user events. For example, the CNIL exemption for analytics without consent in France applies only to aggregate statistical measurement.

Your Amplitude team manages this setting at the project level. To apply it, contact your Amplitude team so they can enable it as part of your project configuration. You can also control broader user-level access using [RBAC](https://amplitude.com/docs/admin/account-management/user-roles-permissions), but the User Lookup control is separate and more targeted, specifically for disabling individual event stream access.

## Report across both projects with Portfolio

To analyze consented and non-consented projects together, use a Portfolio view. [Portfolio](https://amplitude.com/docs/admin/account-management/portfolio) combines multiple projects into one cross-project view so you can build charts across them. This helps when you want a broader picture of traffic or activity across consent states without collapsing the underlying implementations into one project.

A good pattern is to:

- Keep the data collection separate.
- Use a Portfolio to report across both projects where that makes sense.
- Set expectations clearly about what you can and can't combine.

For example, top-line event counts may be useful across both projects, while user-level metrics require more caution. If the non-consented project uses minimized identity, don't expect Portfolio reporting to recreate the same kind of user continuity you have in the consented project.

## Document the routing rules

If you adopt the separate-projects pattern, document it clearly for both implementers and analysts. Teams should know:

- Which events go to which project.
- When traffic moves from the non-consented project to the consented project.
- Which identifiers are allowed in each project.
- Which user-level features should be restricted in the non-consented project.
- Which charts should use the Portfolio view rather than a single source project.

This is one of the most practical ways to support privacy-sensitive measurement while keeping your analytics setup understandable and maintainable.

