---
title: Filter internal referrers from attribution
description: "Use excluded values on a persisted property so internal page-to-page navigation doesn't overwrite the original marketing source."
product: data
lang: en
last_updated: 2026-11-20
token_estimate: 501
---
# Filter internal referrers from attribution

This pattern builds on [Set up a persisted property](https://amplitude.com/docs/data/persisted-properties/set-up).

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

When a user navigates within your own site, the referrer is your own domain. If you classify referrers into channels and persist that channel with Most recent allocation, every internal page-to-page click can overwrite the original marketing source — attribution flips to "internal" or "direct" the moment the user moves to a second page.

Use _Excluded values_ on the persisted property to skip internal navigation during allocation. The previously valid value — the campaign or external referrer that originally brought the user in — continues to apply through any internal events.

## Set up a filter for internal referrers

1. Create a channel in _Data → Channels_ that classifies your traffic sources. Add a definition that maps your own domain (in the `referrer` event property) to a channel value such as `internal`.
2. Create a persisted property in _Data → Properties_ that uses your channel as the event property. Set **Allocation** to **Most recent** and **Expiration** to match your analysis (commonly **Session**).
3. In the persisted property's **Excluded values** field, add the channel value you want to ignore — for example, `internal`. Persisted properties treat excluded values as if the property weren't on the event at all, so allocation rolls forward from the previous valid value.
4. Use the persisted property in your charts. Internal navigation no longer resets the persisted source; the original campaign or referrer continues to attribute downstream events such as `Add to Cart` or `Purchase`.

The same pattern works for any value you want allocation to ignore — internal QA traffic, bot signatures, or test events — not just internal referrers.

