amitdusane.com Adobe Analytics Learning

Shape the dataMarketing Channels

Channel Attribution

The overview promised this section and then deliberately walked away from it. Here it is.

Attribution modeling is the most interesting idea in the Adobe Analytics ecosystem, and it is worth pausing on why. There are hundreds of data analytics tools, dozens of programming languages, database systems, cloud platforms, mobile and web frameworks. Look across all of them and you will not find a parallel to attribution modeling anywhere. It has no equivalent in a data warehouse, no equivalent in a machine learning pipeline, no equivalent in any general-purpose analytics product.

That is not an accident. Every domain grows a signature technique shaped by the thing it studies. Telecom developed call duration and call volume analysis, because that is what a telephone network produces. Medicine developed anatomical imaging, and with it X-ray, CT, and MRI, because that is what a human body demands. Digital analytics developed attribution modeling, because that is what online behavior demands. It exists here and essentially nowhere else, and this section is where you meet it properly.

The journey, before the credit

Start with the thing attribution is trying to reason about, because attribution makes no sense without it.

A visitor searches for a laptop and clicks a paid search ad. That is day one. Over the following weeks they read reviews elsewhere, come back through an email your team sent, leave again, watch a video review that carries a link to your site, return, browse comparisons, add a laptop to the cart, and leave without buying. A week later a message arrives with a discount code. They come back and buy.

Inside those visits, hundreds of individual actions. Pages viewed, content read, a form filled, a document downloaded, a video played, an item added to the cart. That entire accumulation is the user journey, and it is not something you can enumerate. Trying to predict it means generating permutations of every page, every event, every source, every ordering, and the combinations explode past any useful number almost immediately.

So the goal was never to predict the individual journey. The goal is to find the pattern underneath many journeys: what people generally do, in what order, and which of those routes actually produced the outcome the business cares about. That is what attribution is for.

First, name the objective

Nothing in attribution works until the business objective is defined, because you cannot allocate credit for a success that has not been named. There is no driving on a road that leads nowhere.

So what is the objective? Higher revenue? More qualified leads? Deeper engagement? Media consumption, like video plays or downloads? Subscriptions? Or simply publishing good content and understanding how many people genuinely engaged with it? Every one of those is a legitimate objective, and each one changes which channels look valuable.

Think of snakes and ladders. The whole game is organized around reaching square one hundred. Remove that square and the dice rolls still happen, but they mean nothing. The objective is what makes a move good or bad. In Adobe Analytics that objective takes the concrete form of a success event: a purchase, a form submission, a subscription, a download.

Once the objective exists, the entire game of attribution reduces to a single question. Who helped you reach it?

Two words, taken separately

Attribution is the act of assigning credit for a success to the channels that led to it. A model is one particular method of dividing that credit up. Put them together and attribution modeling is simply this: choosing a rule for who gets the credit, and how much.

The naive answer, and why it fails

Take an ecommerce site, where the objective is a purchase. A visitor may arrive once or ten times and perform ten actions or a thousand. Somewhere along the way a visitor became a customer. Something influenced that. The question is what.

The simplest possible answer is to credit whichever channel was showing when the order was placed. Give everything to the last one.

Now watch what that does. A shopper researches for a month, is pulled in by paid search, nurtured by email, informed by organic search, and finally, having already decided, opens the site directly and buys the laptop sitting in the cart. Under naive last touch, Direct takes one hundred percent of the credit. Do this across an entire business and Direct wins nearly everything, because a customer who has already decided almost always arrives directly.

Is that logical? Plainly not. Direct did no persuading. It was simply standing closest to the finish line. The channels that did the actual work show nothing, and a marketer reading that report would cut the very campaigns that built the sale.

You already fixed part of this, in Channel Configuration

That failure is exactly why the Override Last-Touch Channel checkbox exists, and why Channel Configuration told you to leave it unchecked for Direct and Internal. With override off, Direct is not permitted to seize last-touch credit from a channel still persisting from an earlier visit. The paid search click keeps the credit, and Direct does not steal it.

But notice how blunt that fix is. It only answers a yes-or-no question: may this channel claim last touch at all? It cannot answer the harder question, which is how credit should be shared among the four channels that each did real work. Adobe patched the worst symptom at collection time. The disease needs attribution models.

So credit the first channel instead?

Try the opposite. Give everything to the channel that started the journey.

Now paid search takes one hundred percent of every laptop sale, forever, because it happened to be the front door a month earlier. The email that re-engaged the shopper gets nothing. The video that brought them back gets nothing. The discount code that actually closed the sale gets nothing at all. Run a business on this and paid search and organic search absorb the entire budget, while every closing channel stays invisible.

Equally illogical, in the opposite direction. Two extremes, each producing a confident report, each wrong. At this point an analytics developer is genuinely stuck, and worse, is about to make the business team just as confused.

That is where attribution models come in.

The same journey, scored four different ways

Take that laptop purchase and run it through different models. Nothing about the data changes. Only the rule for dividing credit changes, and the winner changes with it.

Same visitor, same purchase, and four defensible answers
Paid Search · day 1 Email · day 9 Social · day 20 Display · day 30, buys Last Touch Display takes all of it First Touch Paid Search takes all of it Linear 25% 25% 25% 25% U-Shaped 40% 10% 10% 40% Nothing about the data changed. Only the rule for dividing the credit, and the winner changed with it.

Look at Paid Search across those four rows: zero percent, one hundred percent, twenty-five percent, forty percent. Nothing about the visitor changed. The model is not reading a fact out of the data. The model is an opinion about what deserves credit, and choosing one is a business judgment, not a technical default.

Every model Adobe offers

Here is the full set, with the exact credit each one distributes.

ModelHow credit is dividedReach for it when
Last Touch100% to the most recent touch point before the conversion. This is the default wherever no model is specified.You want to know what closed the sale. Good for email and SMS.
First Touch100% to the first touch point seen inside the lookback window.You are measuring acquisition and brand awareness. Good for paid search.
LinearEqual credit to every touch point in the journey.Consideration cycles are long, or engagement is repeated and steady. Common for subscriptions and app notifications.
Participation100% credit to every unique touch point. Totals deliberately exceed 100%. Repeats are deduplicated.You want to know which channels a customer was exposed to at all, not who won. Excellent for discovery and overlap analysis.
Same Touch100% only to a touch point occurring on the same hit as the conversion. Nothing else gets credit.You want strictly immediate, single-hit conversions with no journey credit at all.
U-Shaped40% first, 40% last, and the remaining 20% split among everything in between.You value the channel that found the customer and the channel that closed them, while still acknowledging the assists.
J-Curve60% last, 20% first, 20% split among the middle.Same balanced spirit as U-Shaped, but you believe closing matters more than finding.
Inverse J60% first, 20% last, 20% split among the middle.Same balance, but you believe the channel that initiated the journey did the hardest work.
Time DecayExponential decay by recency, using a half-life you set. Default half-life is 7 days. Credit follows 2^(-t/half-life), then normalizes to 100%.Recency genuinely matters, and a touch a month ago should count for less than one yesterday.
CustomYou define the weights for first, middle, and last yourself. Values normalize to 100% even if your numbers do not add up to it.None of the above matches how your business actually thinks about credit.
AlgorithmicCredit is derived statistically rather than by a fixed rule, using the Harsanyi Dividend, a generalization of the Shapley value from cooperative game theory.You want the data to determine contribution instead of imposing a shape on it.

Two rules govern all of them. For the J models and Custom, a journey with only two touch points collapses to a 75 / 25 split in favor of the emphasized end, since there is no middle to divide. And across every model, if only one touch point appears inside the lookback window, it receives 100 percent of the credit no matter which model is selected. A model only has something to do when there is more than one candidate.

Where the Shapley value comes from

The Algorithmic model is worth a moment. It is built on the Shapley value, which comes from cooperative game theory and earned Lloyd Shapley a Nobel Prize in economics. The problem it solves is exactly the one you have: several players cooperate to produce a payoff, they contribute unequally, and the surplus has to be divided fairly. Attribution turns out to be a special case of a problem that economists had already spent decades on. That is a good reminder that "who gets the credit" is a genuinely hard question, not a reporting preference.

Two settings that change every answer

A model never runs alone. It runs inside a scope and a time window, and both change the result.

The container sets the scope of the journey. Visit considers only touch points within a single visit, and selecting it locks the lookback window to the reporting window. Visitor considers touch points across visits, which is what most multi-touch attribution actually wants.

The lookback window decides how far back a conversion may reach for touch points. It can follow the reporting window, or you can set a custom period, but the ceiling is 90 days. Ask for 99 and Adobe will give you 90.

This matters more than it looks. Your laptop shopper took thirty days. Set a seven-day lookback and that paid search click, thirty days back, is simply not visible to the model. Not underweighted. Invisible. The model would faithfully report that the journey began with the discount message, and it would be wrong, and nothing in the interface would tell you so. Match the lookback window to the real length of your buying cycle, not to a default.

Report-time attribution, and the release from permanence

Now the payoff, and it is worth appreciating properly, because this module has spent three sections teaching you that nothing here can be undone. Channels cannot be deleted. Rules are not retroactive. A mistake made today is still wrong in your reports two years from now.

Report-time attribution breaks that pattern completely.

Attribution models in Analysis Workspace are applied at report time, not collection time. Nothing is written into the data. Nothing is baked in. You can apply a model you never considered to data collected two years ago, compare five models side by side in a single table, change your mind tomorrow, and the underlying data never moves.

Everything else in this module is permanent. This one is not.
Collection time permanent Channel definitions Marketing channel processing rules eVar allocation settings Report time reversible Attribution models Applied when the report runs The data never moves one direction, and it ends there change your mind as often as you like

Report-time attribution reaches you in three places:

  • In a freeform table. Click the gear on a metric column, check use non-default attribution model, pick a model, container, and lookback. Copy the column and set a different model on the copy, and you are comparing models side by side in one table.
  • In the Attribution Panel. Drop in a success metric and a dimension such as Marketing Channel, select several models at once, and Workspace builds the comparison for you: a Venn overlap diagram showing which channels co-occur in the same journeys, a flow visualization of the actual paths people took, and a scatter comparing model performance.
  • In calculated metrics. This is the sharpest instrument of the three. Build one metric as First Touch orders, another as Last Touch orders, and subtract. Channels with a positive result are openers, the ones that find customers. Channels with a negative result are closers. Email, for instance, usually shows up as a closer. One subtraction, and you have separated your acquisition channels from your conversion channels.
Why Marketing Channel beats First Touch Channel and Last Touch Channel

The overview mentioned that Adobe offers four channel dimensions and recommended the Marketing Channel pair. Here is the reason. First Touch Channel and Last Touch Channel have their models frozen: the name is the model, and it cannot be changed. The Marketing Channel dimension carries no baked-in opinion, so any attribution model can be applied to it at runtime. Build your reporting on Marketing Channel and every model stays open to you. Build it on the frozen pair and you have thrown that flexibility away for nothing.

Attribution outside Marketing Channels

None of this is limited to Marketing Channels, which is worth knowing because attribution appears in two other places in the product.

The older mechanism is eVar allocation, set on each eVar in report suite settings. It offers three choices: Most Recent, which is last touch and the default, Original Value, which is first touch, and Linear, which splits credit evenly. Note what it is: a collection-time setting, chosen once, applied as data arrives, and not retroactive. Change it and only future data reflects the change. It is attribution with all the permanence of everything else in this module, which is exactly why report-time attribution was such a significant addition.

The second is broader. In Analysis Workspace, an attribution model can be applied to a success event against almost any dimension, not just a channel. Internal promotions, campaign codes, page names, products, even the day of week. The dimension does not have to be a marketing channel for the credit question to be interesting.

Attribution applies to success events, not to traffic metrics

Attribution models work on conversion metrics: orders, revenue, leads, subscriptions, custom success events. They are not meaningful for baseline traffic metrics such as page views, visits, and visitors. The reason is definitional rather than technical. Attribution divides credit for something that was achieved. A page view is not an achievement anybody competed to cause, so there is no credit to allocate. If a stakeholder asks for first-touch attribution on visits, the honest answer is that the question does not have a meaning.

So which model should you choose?

There is no correct model, and anyone who tells you there is has stopped thinking. The model is a statement about what your business believes creates value, and the honest practice is to hold it loosely.

Some reasonable starting positions. Paid search is often best judged on first touch, since its job is to find people who did not know you. Email and SMS are often best judged on last touch, since their job is to close someone who already knew you. Long or considered purchases suit linear or time decay. And participation is unmatched for discovery, because it answers a question none of the others can: which channels were even present in the journeys that converted?

The deepest habit to build is this. Never look at one model alone. Two friends helped you solve a problem, one with logistics and one with money, and asking which of them to thank has no single right answer. It only becomes answerable once you say what you are trying to reward. Put two or three models side by side, watch which channels rise and which collapse, and the disagreement between them will teach you more than any single number ever will.

One thing still unresolved

A model needs touch points to work with, and a lookback window decides how far back it may look. But a separate question sits underneath all of it, and it belongs to Marketing Channels specifically: once a channel brings a visitor in, how long does that channel keep its claim as the visitor returns over the following days and weeks? At what point does an old paid search click stop counting as the reason someone showed up?

That is the engagement period, and it is where Engagement Periods goes.

Where to find it in Adobe Analytics

Attribution models live in Analysis Workspace, not in Admin. In a freeform table, use the column gear icon and check Use non-default attribution model. For side-by-side comparison, drag in the Attribution Panel. Legacy eVar allocation is set separately at Admin > Report Suites > Edit Settings > Conversion > Conversion Variables.

Need implementation steps?

This article focuses on the concepts, architecture, and practical guidance behind the topic. For the latest UI walkthroughs and step-by-step implementation instructions, use the links below. They leave this site and open Adobe's own documentation in a new tab.