Attribution guideMatch the cycleUse observed time-to-conversion instead of copying a default. Separate interactionsClick-through and view-through windows need different treatment. Compare consistentlyAlign event definitions and windows across every report used for budget decisions.
Choose attribution windows that match the buying cycle
An attribution window sets how long an ad interaction remains eligible for credit for a later conversion. Choosing a longer window can change a report without changing the number of customers your business acquired. When reviewing FroggyAds traffic, keep the event, interaction type and timing rule explicit so you compare sources on the same basis.
What changes when you change an attribution window?
Quick answer: The time rule changes which interactions can receive credit, not whether a purchase happened. Compare the same customer event under consistent click or view rules, and keep your business's total confirmed conversions separate from overlapping platform claims.
| Section | Distinct excerpt from this page |
|---|---|
| Time eligibility | A declared hour-or-day limit controls whether this ad interaction remains eligible for conversion credit. |
| Model interaction | Eligible interactions enter the attribution model before its allocation rule distributes credit. |
| Sensitivity testing | Recompute the same campaign under narrower and wider windows to expose decisions that depend on the timing rule. |
Reference for Attribution Windows in Advertising: Google Ads: About conversion windows.
Core controls
Measure the right thing before changing delivery
These three controls keep the analysis tied to real campaign decisions instead of isolated dashboard percentages.
Time eligibility
The window decides whether an interaction can receive conversion credit after a defined number of hours or days.
Model interaction
The attribution model decides how eligible interactions share credit. The window decides which interactions are eligible at all.
Sensitivity testing
Recalculate performance under shorter and longer windows to see whether a decision depends on the reporting rule.
Field note
Attribution window, conversion window and lookback window
Advertising platforms use related terms in different reporting areas. A conversion window is generally the period after an ad interaction during which a conversion can be recorded for that interaction. A lookback window controls how far back an attribution report searches for eligible interactions before the conversion. In everyday campaign work, both describe a time boundary around credit, but the exact setting and report behavior should be verified in the platform documentation.
The attribution model is a separate choice. A last-click model, data-driven model or multi-touch model determines how credit is distributed among the eligible interactions. The window determines which interactions enter the candidate set. Changing either setting can change campaign-level CPA or ROAS without changing the actual number of orders recorded by the business.
Document the event, interaction type, window and model together. A report labeled conversions is ambiguous unless the team knows whether it means a seven-day click window, a one-day view window, a data-driven model or another configuration.
Evidence gate
Record the current eligibility duration, interaction type and report before changing a window. Confirm whether the setting affects future conversions, historical attribution or both. Google Ads documents forward-looking conversion-window changes; a longer setting does not automatically recover conversions that the earlier window never recorded.
Field note
Click-through and view-through windows answer different questions
A click-through window starts from an ad click or another qualifying interaction. It is usually easier to defend because the user took a deliberate action. A view-through window starts from an impression without a click. It can capture delayed influence, but it also has a larger risk of claiming conversions that might have happened without the ad.
Keep view-through reporting separate from click-through reporting. Use a shorter view window, require a viewability definition where relevant, and inspect overlap with other channels. For direct-response optimization, many teams make click-attributed accepted conversions the primary operational signal and use view-through results as supporting evidence.
Engaged-view rules add another interaction type, often for video. They require more engagement than a simple impression but less than a click. Treat them as their own category and avoid blending them into click conversions without disclosure.
Reporting check
Compare the click-only result with any separately supported view-through result for the same accepted events. Retain overlap and deduplication rules. If the apparent source advantage depends on impression-only credit, investigate that dependence before expanding your FroggyAds budget; a deliberate click still does not establish causality by itself.
Audience timing
Set the attribution window before the audience test changes
The window should reflect how long an eligible buyer normally needs to move from paid contact to the accepted conversion. Freeze that rule before traffic starts. If you shorten eligibility during the test, later actions may cease to qualify under the new rule even though the media path did not change. The effect on existing reports depends on the measurement system; record the effective date instead of assuming all historical results will be rewritten.
Match the rule to the actual decision
A quick registration can support a shorter observation policy than a considered B2B purchase, a subscription trial or a repeat ecommerce order. Use first-party order, lead or product data to estimate the delay between the paid visit and the outcome you accept. Segment the delay by new and returning buyers when those journeys differ.
Keep GEO, device, audience eligibility, destination and conversion definition stable during the comparison. A wider audience can naturally contain more slow converters; that does not prove the advertising became weaker. Read the attribution-window result beside delivery, loaded sessions and accepted outcomes.
Write the evidence the test must retain
Preserve the campaign ID, click timestamp, conversion timestamp, conversion type, source ID and the window applied at reporting time. That record lets you explain why an event was included or excluded and prevents a dashboard setting from becoming an invisible change to campaign economics.
Decision framework
A repeatable way to move from data to action
Use a controlled sequence that protects measurement quality before the campaign team changes delivery.
Field note
Choose the window from observed behavior
Start with the distribution of time from first qualified ad interaction to accepted conversion. Look at the median, the 75th percentile and the long tail. A low-consideration mobile utility may convert within hours, while a B2B software trial or finance lead can have a longer research cycle. The window should capture the meaningful buying process without extending so far that unrelated later activity receives credit.
Use the shortest window that captures the stable majority of valid outcomes for the decision at hand. A campaign used for daily source optimization may need a shorter operational window than a quarterly marketing-effectiveness report. Keep both definitions explicit so short-term buying controls are not confused with long-term business analysis.
When the underlying distribution changes, revisit the setting. A new GEO, device mix, checkout process or offer type can change conversion delay. Do not assume one global window fits every campaign.
Action boundary
When your observed delay distribution supports a different window, document which accepted actions the old rule excluded and what the proposed rule would add. Keep the audience and offer unchanged while evaluating that timing difference, so a reporting revision is not confused with improved customer acquisition.
Field note
Align windows before comparing platforms
Cross-platform comparisons fail when one platform reports a long click window and another uses a short click window plus view-through credit. Align the conversion event, time zone, counting method and attribution window before ranking channels. Google Ads also recommends comparable conversion events and windows when using platform-comparable reporting.
Create a warehouse or analytics view with a common decision window. Keep the native platform reports for optimization, but add a normalized report for budget allocation. If exact alignment is not possible, show the differences instead of pretending the numbers are directly comparable.
For a FroggyAds campaign, retain the supported source and campaign identifiers with click times and accepted outcome times in your chosen tracking setup. Recalculate comparable windows only from records that setup actually retains. Source-level buying controls do not imply that every external measurement history is recoverable.
Cross-metric check
Before moving spend between platforms, compare accepted outcome counts and costs under the same usable timing rule. If one system cannot reproduce that view, show its native result separately and explain the gap. A larger credited total is not sufficient evidence that its traffic brings more customers.
Format and response delay
Use one attribution policy to compare the ad formats in your test
Push, Native, Display, Pop, Video and Interstitial reach people in different contexts. The buyer may respond immediately, return later through another visit or complete a conversion after more evaluation. That makes the measurement policy part of the format comparison.
Do not let the window choose the apparent winner
If one format is reviewed after a full maturity period and another is judged from same-day conversions, the result mixes response speed with final value. Keep the accepted event, attribution model, click-through window and any view-through rule consistent where a direct comparison is intended.
Use a sensitivity view to show what changes under a shorter or longer window. Report each scenario as a measurement choice, not as three different sets of conversions. The scenario that matches the documented buying cycle becomes the operating view; the alternatives show how dependent the conclusion is on timing.
Connect format signals to buyer value
Clicks and visits can explain attention, while the accepted conversion and its timing determine commercial usefulness. We recommend choosing the FroggyAds format that fits the offer and destination, then evaluating it under a window the business can defend.
Field note
Run a sensitivity analysis before a large budget move
Where retained event records permit it, calculate CPA, conversion rate and revenue under short, working and long windows for the same campaign cohort. Stable source rankings are less sensitive to this timing assumption, but still require valid events and comparable costs. A ranking reversal calls for investigation of delayed conversions and overlapping credit.
Break the analysis down by format, device, GEO, new versus returning customer and conversion type. A one-day window may be adequate for an app install but too short for a high-consideration purchase. View-through sensitivity should be reported separately.
Use the result to set guardrails. A source that looks profitable only under the longest possible window should not receive the same scaling confidence as a source that performs under a conservative window.
Rollback check
When a longer window changes the preferred source, identify the delayed orders or qualified leads responsible for the difference. Check their acceptance and source matching before buying more of that traffic. We recommend a limited next allocation while the timing-sensitive result is being confirmed.
Comparison model
Read the signal in context
Use a consistent table so every buyer, analyst and campaign owner interprets the same metric in the same way.
| Campaign pattern | Starting analysis window | Why | Validation step |
|---|---|---|---|
| Immediate lead or app action | Hours to a few days | The user can complete the action quickly | Inspect the actual delay distribution and accepted lead rate |
| Ecommerce purchase | Several days to a few weeks | Research and return visits may matter | Compare new and returning customers separately |
| Subscription or software trial | Long enough to cover evaluation and signup | Multiple sessions may precede the trial | Separate trial start from paid activation |
| B2B or high-consideration lead | Potentially longer | The buying process includes research and approval | Use CRM stages and offline conversion dates |
| View-through reporting | Shorter than the click window | Impression-only credit has more uncertainty | Report separately and test incrementality |
Workflow
Build the control loop step by step
Complete the measurement and validation steps before a source, bid or budget decision becomes permanent.
Define the accepted event
Choose the exact business outcome that will receive attribution credit.
Measure conversion delay
Calculate the time between qualified interaction and accepted outcome.
Separate interaction types
Create distinct click, view and engaged-view reporting.
Choose a working window
Select the shortest period that captures the meaningful buying cycle.
Normalize comparisons
Align event definitions, time zones and windows across platforms.
Run sensitivity scenarios
Use the same retained event cohort to compare shorter and longer eligibility periods. Identify which accepted outcomes enter or leave each view, and state when missing historical records prevent a valid recalculation.
Set operational rules
Use a conservative window for source decisions and document any broader reporting view.
Review after material changes
Reassess when the GEO, offer, checkout, format or conversion definition changes.
Eligibility rule: interaction timestamp ≤ conversion timestamp ≤ interaction timestamp + selected window Sensitivity check: compare CPA and accepted conversion volume under short, working and long windows.
Launch contract
Freeze the attribution settings that govern the first campaign cohort
Before delivery begins, record the default window, timezone, accepted conversion, deduplication rule and reporting owner. Test the complete conversion path and confirm that the click and conversion timestamps reach the same reporting system. A campaign cannot validate a window when the underlying event chain is incomplete.
Run one bounded cohort
Choose a start date, stop rule and maturity date. Keep recent conversions provisional until they have received the full opportunity allowed by the policy. Review the cohort at its maturity date rather than comparing yesterday's partial results with an older completed period.
Make corrections prospectively
If the team discovers a broken timezone, duplicated event or missing identifier, document the affected dates and repair the configuration. Begin a clean cohort for the next decision. Silent retroactive changes can make a media improvement look real when only the reporting rule changed.
Assign the next action before launch
Write which result permits more budget, which result triggers a landing or tracking repair and which result ends the test. FroggyAds gives you budget, targeting and source controls for the next campaign action; the accepted downstream record decides whether that action is justified.
Pre-launch check
Quality gate before the campaign depends on the data
Use the checklist as a release gate. A missing identity, inconsistent window or broken redirect can invalidate later optimization.
Accepted conversion event documented
Click and view windows reported separately
Time-to-conversion distribution measured
Platform time zones aligned
Counting method aligned
Sensitivity analysis completed
Native and normalized reports labeled clearly
Window reviewed after major campaign changes
Standards and primary documentation
Worked scenarios
How the decision changes in real campaign conditions
Use these examples to separate the metric from the action. The same headline number can require a different response when the objective, data quality or business outcome changes.
Fast mobile action
A mobile utility campaign records most accepted installs within the first day after a click. A long click window adds little useful volume and increases the chance that unrelated later activity receives credit. Use a short operational window for source optimization, then check a longer reporting window to confirm that the ranking of sources does not change materially. Keep post-install events separate because their delay distribution can be longer than the install itself.
High-consideration B2B lead
A B2B campaign produces form submissions after several research visits, and accepted opportunities appear later in the CRM. A one-day window understates the campaign, while a very long window can overclaim brand-driven demand. Measure the interaction-to-lead and lead-to-qualified-opportunity delays. Use a documented working window for campaign reporting and a separate CRM analysis for pipeline impact. The media team should not optimize from raw form submissions when the business decision depends on qualified outcomes.
Platform totals disagree
Two advertising platforms both claim the same purchase. One uses a longer click window and includes view-through credit, while the other uses a shorter click-only window. Do not add the totals together. Build a normalized report with one accepted purchase event, one time zone and comparable windows. Keep native reports for platform optimization, but use the normalized view for budget allocation. Run an incrementality test when overlapping credit remains material.
Limits
What this measurement cannot prove by itself
No attribution window can determine causality on its own. It changes eligibility for credit inside a reporting model. Incrementality testing is required when the question is whether advertising created net-new outcomes.
A window chosen from historical behavior can become outdated after changes in price, offer, device mix, geography or checkout flow. Review the distribution rather than treating the setting as permanent.
Evidence gate
For a fast action, a qualified B2B opportunity and an overlapping platform claim, the accepted event and waiting period differ. Write the next budget decision against the relevant mature cohort. Do not use the fastest scenario as a timing benchmark for the other two.
Operations
Build an attribution-window policy
A useful policy names the owner, the accepted conversion event, the default click window, the view-through rule, the time zone and the exception process. It also states which report is used for source optimization and which report is used for broader budget allocation. Without that separation, a media buyer may pause a source from a conservative click-only view while a finance report uses a longer blended window, creating two apparently correct but incompatible decisions.
Keep the policy close to the data. Include the current setting in campaign briefs, tracker configuration and dashboard notes. When a window changes, record the date and avoid comparing the before and after periods as though the measurement rule stayed constant. For long-running campaigns, save a normalized view using a fixed historical window so trend analysis is not rewritten every time a platform default changes.
Finally, connect the policy to conversion maturity. A campaign should not be judged before enough of the chosen window has elapsed. Use a provisional report for early pacing and a matured report for final source decisions. This prevents recent sources from looking artificially weak simply because their conversions have not had time to arrive.
A mature reporting process also distinguishes event time from report time. The conversion can occur today but be credited to a campaign interaction from several days earlier. Daily campaign totals can therefore continue to change as the window matures. Mark recent periods as provisional, and avoid comparing a fully matured week with a current week that still has conversions arriving. For finance and executive reporting, freeze the reporting date and explain the maturity rule so later backfill is expected rather than treated as an unexplained discrepancy.
Use a consistent naming convention for every report export. Include the event, interaction type, window, model and extraction date in the file name or dashboard subtitle. This small governance step prevents an old report from being compared with a newer report that uses different attribution settings.
Reporting check
Give every policy version an effective date, reporting owner and review trigger. If a new trial length or checkout process changes conversion delay, compare the old and proposed windows on available records before changing the operating rule. Keep exports labelled with their original policy so earlier decisions remain explainable.
Questions
Choose attribution windows that match the buying cycle: FAQ
Practical answers for media buyers, analysts and campaign operators.
What is an attribution window in advertising?
It is the period after an eligible ad interaction during which a later conversion can receive advertising credit under the reporting rules. Specify the starting interaction, conversion event and duration. A click-based purchase report and a view-based lead report are different measurements. Keep those definitions attached to your FroggyAds source comparison so a change in credited results is not mistaken for a change in actual sales.
How should I choose an attribution window for my campaign?
Use the offer's observed decision timing and the customer action you need to evaluate, then confirm the settings supported by the systems involved. A quick registration and a considered business purchase may need different reporting treatment. Test whether your buying decision changes under plausible nearby windows. Choose a defensible rule before comparing sources, not whichever setting makes the latest campaign look best.
How do one-day and seven-day attribution differ?
Consider a hypothetical customer who clicks an ad and buys three days later. A one-day click window would exclude that purchase from credit for this interaction; a seven-day window could include it if the other attribution rules are satisfied. The business still has one purchase. This example explains the timing rule, not a FroggyAds default setting or evidence that the ad caused the sale.
Why should click-through and view-through attribution be reported separately?
A click and a recorded ad impression provide different evidence of interaction. Keep their eligibility windows and precedence rules distinct when both may claim the same outcome. Before using any view-through figure for a FroggyAds buying decision, confirm that the selected measurement setup actually supports it. Do not infer view-through reporting simply because the ad format buys impressions.
What risk comes with a very short attribution window?
A short window can omit legitimate delayed actions and favour channels used close to conversion. It may still fit an immediate decision cycle, but the report should quantify later excluded outcomes where the underlying data allows it. Do not describe narrow eligible credit as the customer's complete journey or assume an in-platform report retains events outside its configured measurement window.
What risk comes with a long attribution window?
A long window can keep awarding credit after the original interaction is unlikely to explain the action, while also increasing overlap between campaigns. Review elapsed time to action, repeat exposure and deduplication evidence before extending the eligible period. A larger reported return is not itself proof that the longer rule is more accurate.
Why do two ad platforms claim the same conversion?
Each may find an eligible interaction inside its own window and apply its own credit rules. Adding those totals can count one business action more than once. Reconcile with the confirmed order or lead record and document the role of your chosen attribution system. FroggyAds source reporting is useful for campaign decisions, but it should not be added to another platform's claims as though both sets were automatically exclusive.
Will changing an attribution window rewrite my historical results?
That depends on the platform, data source and report. Some changes affect future eligibility without rebuilding every historical record. Check the documented behavior before comparing periods, preserve the previous configuration and note the effective date. For analytical comparisons, only recalculate from records you actually have; do not assume missing or previously excluded events can be recovered by selecting a longer window.
Can one attribution window fit every product action?
No. An install, trial start, purchase and renewal can occur on different timelines and answer different questions. Assign windows to the event and decision being reported, then prevent one late outcome from receiving unexplained duplicate credit. Keep those events separate when evaluating which FroggyAds sources bring useful customers rather than only the fastest initial action.
How should attribution rules guide a FroggyAds budget decision?
Keep the conversion definition, window and counting rules consistent across the sources you compare. Allow recent traffic enough time to produce the intended action, while retaining your spending limits. Our source controls let you act on the resulting evidence. Record any rule change before increasing the budget, so you can distinguish better customer acquisition from a report that assigns credit differently.
Continue the workflow
Related FroggyAds resources
Connect this guide to campaign setup, source controls, tracking and optimization.
Launch with a measurable plan
Start your next FroggyAds campaign with a declared accepted event and enough observation time for your actual buying cycle. Our targeting, budget and source controls let you test a relevant audience without changing the credit rule mid-comparison. Review mature outcomes before deciding which source deserves the next allocation.
Buyer decision
Turn attribution-window sensitivity into a budget decision
Choose and document the time boundary that connects your FroggyAds traffic with an accepted conversion. Explain how the working window reflects your observed buying cycle, then show how much the source recommendation changes under reasonable shorter and longer alternatives. Use that sensitivity to size the next test.
| Policy view | Question it answers | Evidence to retain | Budget implication |
|---|---|---|---|
| Short sensitivity window | How much value appears close to the paid contact? | Included conversions, excluded later conversions and response-delay distribution | Useful for cash-flow or rapid-response diagnostics, not a substitute for the agreed default |
| Operating default | Which conversions fit the documented buying cycle? | Policy version, click and conversion timestamps, accepted status and source identity | Primary view for keep, cap, exclude or expand decisions |
| Long sensitivity window | How much later activity might change the conclusion? | Incremental conversions, repeat buyers, cross-device limits and possible organic return paths | Shows whether the result depends heavily on late credit |
| Incremental validation | Did advertising cause value beyond what would occur anyway? | Holdout or experiment design, eligibility and measured lift | Use when attribution alone cannot establish causality |
Keep attribution and causality separate
An attribution rule assigns credit among observed contacts. It does not prove that the ad caused every credited conversion. When the budget decision requires causal evidence, add an experiment or holdout method and keep its result separate from the attribution report. Our marketing attribution guide explains the broader model choices around this policy.
Choose FroggyAds when you want to buy traffic through a self-serve campaign workflow and keep budget, targeting and source evidence available for analysis. Define the accepted outcome in your business system, version the window and compare mature cohorts before you scale. This connects the feature set to a defensible media-buying decision without treating credited revenue as a guaranteed result.
Direct answer
What matters most when you choose an attribution window?
Choose the narrowest time boundary that still captures the normal conversion delay for the accepted business outcome, then test how the decision changes under shorter and longer scenarios. Keep the policy fixed across comparable campaign cohorts, wait for each cohort to mature and preserve the click, conversion, source and policy-version evidence behind every included event.
If a different window reverses the budget recommendation, treat the result as sensitive and collect better timing or incremental evidence before expanding spend. If the conclusion remains stable, increase one campaign limit at a time and keep the prior configuration as the recovery point.