---
title: "Achieve last non-direct touch attribution"
description: "Combine a channel classifier with no Direct catch-all and a persisted property that renames (none) values, so direct visits don't overwrite the marketing source."
product: data
lang: en
last_updated: 2026-11-20
token_estimate: 974
---
# Achieve last non-direct touch attribution

Last non-direct touch attribution assigns credit to the most recent marketing channel a user engaged with before converting, skipping over direct visits. Persisted properties can replicate this model. This is the attribution model Google Analytics uses for user-scoped and session-scoped dimensions.

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

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

Last non-direct touch attribution assigns credit to the most recent marketing channel a user engaged with before converting, skipping over direct visits. Persisted properties can replicate this model.

This is the attribution model used for user-scoped and session-scoped dimensions in Google Analytics.

Attribution event properties such as `referrer` and UTM parameters attach to every event by default on Browser SDK 2.45.0+ and GTM template 5d7e5+. You don't need to change your SDK or GTM configuration before following these steps.

## How it works

Persisted property allocation automatically skips events where the property has no value, so direct visits with no channel value don't overwrite the persisted source. If a user enters through Paid Search, browses, returns directly later, and converts, the conversion event still attributes to Paid Search.

The setup combines two configurations:

- A channel classifier that doesn't assign "Direct" as a catch-all fallback. Direct sessions arrive without a channel value rather than with a Direct value.
- A persisted property that renames `(none)` to "Direct" for display, so genuinely unattributed users still appear under a named value rather than blank.

## Set up the persisted property

1. Go to _Data → Properties_ and create a new persisted property.
2. Select your channel classifier output (for example, `Marketing Channel`) as the event property.
3. Set **Allocation** to **Most recent**.
4. Set **Expiration** to a window that matches your business cycle, such as 7 days.
5. In **Rename (none) values**, enter `Direct`. Users with no attributed channel display as "Direct" rather than blank.

## Configure the channel classifier

In _Data → Channels_, make sure your classifier defines explicit rules for each channel — Paid Search, Organic Social, Email, and so on. Don't add a catch-all rule that assigns Direct to everything else. With no catch-all, direct sessions arrive without a channel value, and the persisted property carries the most recent non-direct channel forward.

## Supported metrics

This approach works with Event Totals, Session Totals, and Unique counting mechanisms in Data Tables. Amplitude doesn't support changing the attribution method within data tables when you use a persisted property as a group-by, so multi-touch attribution models don't apply.

## Related pattern: Excluded values for named traffic

If you want to skip specific _named_ values during allocation — for example, an "internal" channel for same-domain referrers, QA traffic, or bot signatures — use _Excluded values_ on the persisted property. Refer to [Filter internal referrers from attribution](https://amplitude.com/docs/data/persisted-properties/filter-internal-referrers). The Rename `(none)` approach above is the right tool when direct visits arrive as fully unattributed sessions; Excluded values is the right tool when allocation needs to skip a specific value the classifier emits.

## Verify the setup

After you configure the property and the classifier, follow the [verify persisted properties guide](https://amplitude.com/docs/data/persisted-properties/verify-persisted-properties) to confirm direct visits don't overwrite the persisted channel for users who arrived through marketing.

