Skip to main content

When to NOT use Attribution

Which problems Klar's attribution can solve — and in which cases it does not add real value over your platform data.

Written by Frank Birzle

tl;dr

  • Attribution adds value when you spend across multiple channels, have multi-touchpoint customer journeys, and sell products with different margins or LTV

  • Attribution adds little value when 80–90% of budget goes to one channel, most customers buy in a single session, or your product catalogue is largely homogeneous

  • Platform data is inherently flawed — ad accounts overcount conversions and are always last-touch. Attribution gives you a cross-channel view of what's actually driving revenue

  • If you're unsure: the first two conditions (channel mix and journey length) are the most decisive


What problems does Klar's attribution solve?

Attribution helps with three things that platform data can't do reliably:

1. Identifying which channels actually drive conversions

Ad account data is always last-touch and limited by lookback windows. A customer who sees a Meta ad, then a Google ad, then converts via brand search — Google and brand search each claim the full conversion. The actual media that initiated the journey gets no credit.

Attribution models like Data-Driven or Linear distribute credit across the full journey. This often reveals that a large share of "direct" or "brand search" conversions are in fact driven by push marketing — and how much is genuinely word of mouth that shouldn't be credited to any paid channel.

2. Tracking the entire user journey across touchpoints

Ad accounts clip the journey at their lookback window and always credit the last interaction. Klar's attribution tracks every touchpoint — including the top-of-funnel ad that brought a customer into the journey days or weeks earlier — and distributes value dynamically.

3. Measuring performance beyond gross revenue

Ad accounts only report gross revenue. Attribution in Klar lets you evaluate channels by net revenue (post-returns), new customer revenue, profit (CM1/CM2), and customer lifetime value — metrics that determine whether a channel is actually profitable, not just large.


When does attribution NOT add value?

Attribution adds little to no value if all three of the following are true for your business:

1. You concentrate 80–90% of your budget in one channel

If almost all of your spend goes to a single channel, the question "which channel is responsible for this revenue?" answers itself. Marketing mix modeling and multi-touch attribution are built to disentangle channel contributions — if there's effectively only one channel, there's nothing to disentangle.

2. Your customers almost always buy in a single session

If you sell an impulse purchase product and most customers arrive, decide immediately, and either buy or leave — there is no meaningful journey to attribute across. Single-touchpoint journeys don't benefit from multi-touch attribution. Last-touch is accurate by default.

3. Your product catalogue is largely homogeneous

LTV and margin variation is most useful when different channels bring in customers with different purchasing behaviour. If most of your revenue comes from the same or very similar products, there will be little variation in margins or LTV across channels — so the third benefit of attribution (identifying which channels generate the most profitable customers) doesn't apply.


How to decide

If none of the three conditions above apply to your business, attribution will add meaningful value. Use the Klar Attribution Plan to understand your true channel mix, full customer journeys, and profitability by channel.

If all three conditions apply, you can rely on platform data and Klar's overall marketing efficiency metrics (MER) without the Attribution Plan.

The first two conditions are the most decisive. A diverse channel mix with multi-touchpoint journeys is where attribution delivers the clearest uplift. Product homogeneity alone is rarely a reason to skip attribution if the other two conditions are in play.

Did this answer your question?