Tools Cassandra's OrganizationVisit Website →
← Back to blog

1 Day vs 30 Day Windows: View Through Attribution for Marketers

September 1, 2026
1 Day vs 30 Day Windows: View Through Attribution for Marketers

View-through attribution (VTA) credits a conversion to an ad impression a person saw but never clicked, provided the conversion happens inside a defined lookback window. It works as a supporting signal for awareness and upper-funnel campaigns, video, and CTV, where clicks are scarce but exposure still shapes behavior. VTA should never stand alone; validate it with incrementality testing before it touches a budget decision.

TL;DR:

  • Longer lookback windows, such as 30 days, significantly increase view-through conversion counts but do not necessarily improve accuracy or causality.
  • View-through attribution should be used mainly for upper-funnel channels like CTV and display, as clicks are rarely expected in these formats.
  • Validating view-through claims with incrementality testing and cross-platform reconciliation is essential to prevent overestimating channel impact and inflated attribution.
  • Disjointed definitions of viewability and overlapping claims across platforms create challenges in interpreting VTA data reliably.
  • First-party logged-in user data enhances matching accuracy, reducing errors caused by probabilistic cross-device attribution in privacy-restricted environments.

Table of Contents

What Is View-Through Attribution and How Does It Work?

VTA works on a simple mechanical chain: an ad renders, the platform logs it as a viewable impression, and if the same user (or device, depending on matching method) converts within the lookback window, the platform assigns view-through credit. No click required.

The catch is that "viewable" doesn't mean the same thing everywhere. Google's Active View standard counts a display ad as viewed once 50% of its pixels are visible for one second, a bar low enough that a banner glimpsed while scrolling past can still generate credit. Video engaged-view thresholds run much higher, often requiring several seconds of watch time. That gap in definitions is why VTA volume can swing wildly between platforms running the exact same creative.

A typical flow looks like this:

  • A shopper sees a CTV ad for a mattress brand but keeps scrolling.
  • Three days later, she searches the brand name and buys directly from the site.
  • The DSP's pixel logs a view-through conversion because the purchase fell inside its lookback window.
  • Meanwhile, Google Ads may also claim partial credit for the same session through its own view-through conversion window, creating overlapping claims neither platform can see or reconcile on its own.

That last point is the operational headache: each platform dedupes conversions inside its own walls, but nothing forces Google, Meta, and a DSP to compare notes with each other.

What Are the Default View-Through Attribution Windows?

Lookback windows vary by platform, and the differences are large enough to change your reported numbers by a wide margin. Getting familiar with the defaults matters more than most marketers assume before they start comparing channel performance.

Common defaults marketers encounter:

  • Google Ads: 1-day view-through conversion window by default, though it's adjustable.
  • Programmatic DSPs: frequently default to windows as long as 30 days.

A 30-day window will credit far more conversions than a 1-day window for identical campaigns, simply because it casts a wider net over unrelated purchase activity, according to analysis from StackAdapt. Longer isn't more accurate. It's just more inclusive, and inclusive isn't the same as causal.

A practical rule: match window length to sales cycle and ad format, then test sensitivity by running the same campaign data through 1-day, 7-day, and 30-day windows to see how much the numbers move.

How Does View-Through Attribution Differ From Click-Through and Engaged-View?

These three metrics answer different questions, and treating them as interchangeable is where most attribution reporting goes wrong.

Click-through attribution reflects an active choice. Someone saw the ad, decided it was worth a click, and followed through. That's a stronger behavioral signal because intent is baked into the action itself. View-through attribution reflects passive exposure. Nothing confirms the person even registered the ad consciously, only that the platform's system logged it as viewable within its own definition.

Engaged-view conversions sit in a third category, mostly for video. They require the viewer to watch past a defined threshold before the platform counts a related action as engaged rather than merely viewed. The complication: engaged-view conversions sometimes land directly in your main "Conversions" column rather than a separate view-through bucket, which means they can quietly influence automated bidding strategies if you don't segment ad-event types carefully.

Keep the three in separate dashboard rows, never summed into one ROAS figure. Use click-through data to inform bid tactics on direct-response campaigns. Use view-through and engaged-view data to evaluate creative resonance and channel influence, not to justify a bigger media check without further proof.

When Should Marketers Rely on View-Through Attribution?

VTA earns its keep in specific conditions: awareness campaigns, video, connected TV, and display placements where the format itself discourages clicking. Nobody clicks a CTV ad from their couch. That doesn't mean the ad did nothing.

VTA is genuinely useful for:

  • Surfacing assisted conversions that last-click models erase entirely.
  • Revealing which upper-funnel channels contribute to eventual conversions, even without a direct click path.
  • Preventing marketers from starving awareness budgets in favor of channels that only look better because they're easier to measure.

That last point deserves emphasis. A brand running CTV alongside search often sees search take all the last-click credit, simply because search sits closer to the purchase moment. VTA gives you a counterweight, evidence that the upper-funnel spend is doing something, even if it can't prove exactly how much.

Pro Tip: Run a side-by-side comparison of channel rankings under last-click versus view-through inclusion. If a channel's rank changes dramatically, that's your cue to test it for incrementality before touching its budget either direction.

What Are the Risks and Limitations of View-Through Attribution?

VTA's biggest weakness is that it counts exposure, not causation, and several real-world factors widen that gap further.

Non-viewable impressions and ad fraud inflate the numbers you're working with. An impression counted by a bot, or one that technically met the viewability threshold without a human ever perceiving it, still generates credit under most platform rules. Since Google's Active View bar sits at 50% visibility for one second, plenty of technically viewable impressions never register with an actual person.

Cross-platform double-counting compounds the problem. Google can dedupe conversions inside its own ecosystem, but it has no visibility into what Meta or a DSP is separately claiming for the same customer journey. Run the same campaign across three platforms and you may be looking at triple-counted credit for a single sale.

Practical checks worth running regularly:

  • Reconcile reported view-through conversions against actual CRM records to catch inflated claims early.
  • Review viewability metrics alongside conversion counts, not in isolation.
  • Run window-length sensitivity tests; if changing from 1 day to 30 days doubles your conversion count, treat the larger figure with skepticism.

Engaged-view conversions landing in your main Conversions column is a related risk worth separate attention, since it can skew automated bidding toward campaigns that only look effective on paper.

How Should Teams Report and Implement View-Through Attribution?

A reliable VTA setup depends on discipline in three places: how you separate metrics, how you set windows, and how you validate the resulting numbers before they touch a budget.

  1. Separate click-through and view-through in every report. Use the platform's distinct "Conversions" and "All conversions" columns correctly rather than blending them into a single ROAS line, a practice FoundGrove's analysis specifically warns against.
  2. Set lookback windows deliberately, not by default. Test 1-day, 7-day, and 30-day windows against the same dataset and document how much the reported numbers shift.
  3. Triangulate before acting on VTA. Cross-check view-through numbers against incrementality tests, marketing mix modeling, and CRM records before reallocating spend.
  4. Prioritize authenticated, first-party identity matching. Deterministic matching on logged-in users produces far more reliable cross-device attribution than probabilistic guesses based on behavioral patterns.

A workable monthly dashboard includes columns for click-conversions, view-through conversions, engaged-view conversions, window length used, and an incrementality-test status flag showing whether that channel's VTA claims have been independently validated.

Pro Tip: If a channel's view-through conversions have never been checked against an incrementality test, label it "unvalidated" in your reporting. That one flag prevents more budget mistakes than any dashboard redesign.

Why Validated Measurement Matters More Than Raw VTA Counts

VTA tells you exposure happened. It doesn't tell you the exposure caused anything. That distinction is where Cassandra's approach to measurement starts: treating view-through data as one input among several, never the deciding vote.

Cassandra triangulates multi-touch attribution, marketing mix modeling, and instant incrementality testing so a raw VTA number gets checked against a causal baseline before it influences spend. A brand seeing strong CTV view-through numbers, for instance, can run a geo-lift or holdout test through Cassandra to confirm whether that channel is actually driving incremental sales or simply riding along on impressions that were going to convert regardless. Clients across fashion, nonprofit, and travel sectors have used this multi-touch attribution framework to catch exactly this kind of gap before it cost them budget.

How Does VTA Compare to Last-Click, Linear, and Time-Decay Models?

A CTV ad that primed someone for two weeks gets zero recognition if search closed the deal. VTA exists partly to correct that blindness, but it corrects in the opposite direction: it can over-credit channels for exposure that had nothing to do with the eventual purchase.

Linear attribution splits credit evenly across every touchpoint in the journey. It's fairer to upper-funnel channels than last-click, but it assumes every touch mattered equally, which rarely reflects reality. A single retargeting click right before purchase usually carries more causal weight than an impression seen three weeks earlier, yet linear models treat them the same.

Time-decay models split the difference, weighting touchpoints closer to conversion more heavily while still acknowledging earlier ones. This handles the "search gets all the credit" problem better than last-click, but it still relies on correlation between timing and impact, not proof of causation.

VTA fits into this landscape as a data point about exposure, not a competing philosophy for splitting credit. It can feed into a multi-touch attribution model as one of several signals, but on its own it answers a narrower question: did this specific impression appear before this specific conversion within this specific window? None of these models, including VTA, prove causation by themselves. That's the gap incrementality testing is built to close, by comparing exposed and unexposed groups directly rather than inferring influence from touchpoint sequencing.

How Do Privacy Changes Affect View-Through Attribution Accuracy?

Cross-device and cross-browser tracking used to rely heavily on third-party cookies and device graphs that could stitch a person's journey together across a phone, a laptop, and a tablet. Privacy restrictions from browsers and operating systems have steadily cut into that capability, and the practical effect on VTA is a growing measurement gap between what actually happened and what a platform can observe.

When a person sees a CTV ad on a shared living-room screen, then converts later on a personal phone, deterministic identity matching, tying that activity to one authenticated account, is the only reliable way to connect the two events. Amplitude's guidance on cross-device attribution is direct about this: probabilistic matching, which infers connections from behavioral patterns like IP address or timing, carries real accuracy trade-offs compared to deterministic matching on logged-in users.

The practical consequence for VTA is twofold. First, impressions served to non-logged-in or anonymous users become harder to connect to downstream conversions, which can understate view-through's real contribution in privacy-restrictive environments. Second, and more dangerous, is the opposite failure: probabilistic matching can occasionally connect impressions to conversions that were never actually linked, inflating credit in ways that look precise but aren't.

Marketers should treat authenticated, first-party data as the foundation for any VTA analysis they plan to act on. Where a brand has logged-in users, loyalty programs, or app accounts, matching quality improves substantially. Where it doesn't, view-through numbers deserve a wider margin of skepticism, particularly for cross-device journeys where the connecting evidence is inferred rather than confirmed.

How Do Privacy Changes Affect View-Through Attribution Accuracy? — overview diagram

How Should Marketers Interpret View-Through Attribution Metrics Correctly?

The most common misread of VTA is treating a rising view-through conversion count as proof that a campaign is working better. It might be. It might also mean the lookback window got extended, or that viewability thresholds are catching more marginal impressions than before.

Before drawing a conclusion from a VTA report, check what changed. Did the window length shift? Did the platform update its viewability definition? Did spend increase, simply generating more impressions and therefore more opportunities for a coincidental view-then-convert pattern? Any of these can move the number without reflecting a real change in campaign effectiveness.

A second common error is comparing view-through conversions across platforms as if they measure the same thing. They don't. Google's 1-day default and a DSP's 30-day default aren't apples-to-apples, and a channel with a longer window will structurally outperform one with a shorter window in raw conversion counts, regardless of actual impact.

A third misinterpretation involves assuming VTA numbers are additive with click-through numbers to calculate total campaign value. They're not meant to be summed into one figure, since overlapping claims and different confidence levels make a combined total misleading rather than clarifying, a point FoundGrove's practitioner analysis makes plainly.

The safest interpretation habit: treat every VTA figure as a directional signal about exposure and possible influence, not as a settled conversion count. Ask what would need to be true for that number to reflect real causation, then go test it.

What Tools Support View-Through Attribution Analysis?

Most advertising platforms build view-through reporting directly into their own interfaces. Google Ads reports view-through conversions in dedicated columns alongside standard click conversions, with adjustable windows described in its own attribution documentation. Meta's Ads Manager similarly separates view and click attribution windows inside its reporting settings. Programmatic DSPs typically expose their own conversion window configurations, often defaulting longer than either Google or Meta.

Beyond native platform reporting, mobile measurement partners and analytics glossaries like AppsFlyer provide cross-app view-through tracking for mobile campaigns, useful when a brand's conversion event happens inside an app rather than on a website.

The harder problem, reconciling view-through claims across multiple platforms and validating them against actual causal impact, is where dedicated marketing measurement platforms fill a gap that native ad-platform reporting can't. Cassandra's approach combines multi-touch attribution, instant incrementality testing, and marketing mix modeling in one system, so a marketing team isn't stuck manually cross-referencing five different platform dashboards and guessing at overlap. For teams running VTA across CTV, display, and social simultaneously, that reconciliation layer is often the difference between a defensible budget decision and an educated guess dressed up as data.

How Do You Validate View-Through Data With Incrementality Testing?

The cleanest way to confirm whether view-through credit reflects real influence is a holdout or geo-lift test that compares exposed and unexposed groups directly, rather than inferring impact from impression timing.

A geo-lift test works by pausing or reducing ad exposure in selected markets while running normally elsewhere, then comparing conversion rates between the two groups. If the "exposed" markets convert meaningfully higher than the holdout markets, that's causal evidence the advertising drove behavior, evidence VTA alone cannot provide. One real-world example: an incrementality test on Meta ads uncovered a case of roughly 4x over-attribution compared to what the platform's own reporting claimed, a gap that view-through metrics alone would never have surfaced.

A practical validation sequence looks like this: start with view-through data to identify which channels appear to be contributing outside the last-click path. Flag the highest-claiming channels for a holdout test. Run the geo-lift or audience holdout for a defined period, long enough to reach statistical confidence. Compare the lift result against the platform's reported view-through conversions for that same period and market. Where the two diverge significantly, trust the incrementality result over the raw attribution number.

This sequencing matters because incrementality testing is resource-intensive; you can't run holdouts on every channel simultaneously. VTA data helps prioritize which channels most urgently need that validation, turning a supporting signal into a useful triage tool rather than a decision-maker in its own right. It's worth noting that even incrementality multipliers can mislead if applied without accounting for diminishing returns at higher spend levels, so validation itself needs periodic recalibration.

How Do You Validate View-Through Data With Incrementality Testing? — overview diagram

Cassandra's Take: Treat VTA as a Prioritization Signal, Not a Verdict

VTA earns a seat at the table when you're deciding which channels deserve a closer look, not when you're deciding how much budget they deserve. That distinction gets lost constantly, and it's the single most expensive misread in upper-funnel measurement.

Our recommended order of operations: secure authenticated first-party identity matching first, since nothing downstream is trustworthy without it. Run incrementality tests on your highest-claiming channels second. Only then use VTA data for what it's actually good at, spotting channel influence and creative resonance patterns worth investigating further.

This week, pull your view-through numbers by channel, flag the top three claimants, and ask whether any of them have ever been checked against a holdout test. If the answer is no, that's your starting point.

— Tools

How Cassandra Helps Teams Validate View-Through Signals

Raw view-through numbers tell you a story about exposure. Cassandra tells you whether that story holds up under a real causal test, which is the gap between a defensible budget call and an expensive guess. The platform combines measurement validation, instant incrementality testing, and marketing mix modeling in one workflow, so a team can check its VTA claims against a geo-lift or holdout test without stitching together five separate tools.

Cassandra

A practical starting pilot: pick your highest-claiming upper-funnel channel, run a short incrementality test through Cassandra alongside your existing view-through reporting, and compare the two results directly. Clients in fashion, nonprofit, and travel have used exactly this sequence to catch over-attribution before it drained budget from channels that were actually working. If you're ready to see where your own VTA numbers might be overstating impact, explore Cassandra's measurement use cases and start a pilot built around your current channel mix.

Sources

FAQ

What Does "7-Day Click, 1-Day View" Attribution Mean?

It means a platform credits a conversion to a click within 7 days of that click, or to a view-through impression only within 1 day of that impression, a common configuration used by ad platforms including Meta.

What Is the Purpose of Attribution?

Attribution assigns credit for a conversion to the marketing touchpoints that preceded it, helping teams understand which channels and creative are influencing customer decisions so budget gets allocated more effectively.

What Is an Example of an Attribution Model?

Last-click attribution is a common example, giving full conversion credit to the final touchpoint before purchase; view-through attribution is another, crediting an ad impression even without a click, provided the conversion falls inside the platform's lookback window.

How Does Cassandra Help Validate View-Through Attribution?

Cassandra combines multi-touch attribution with instant incrementality testing and marketing mix modeling, letting teams confirm whether view-through conversions reflect real causal impact rather than coincidental exposure.

Made with BabyLoveGrowth to create content that ranks