https://virev.ai/_blog/immutable/chunks/CFf9w1Ug.js

1import{D as e,J as t,M as n,X as r,a as i,at as a,b as o,k as s,o as c,ot as l,q as u}from"./Cd_LoYDd.js";import"./xihTtKlq.js";import{n as d,r as f,t as p}from"./DVlN4bh3.js";var m={title:`Choose a reporting window before looking at results`,description:`Set post-age checkpoints, conversion lookbacks, and report freeze dates before launch. Use separate policies for short-form posts and evergreen creator content.`,date:`2026-09-27`,author:`Virev editorial`,tags:[`campaign measurement`,`reporting windows`,`attribution`,`creator analytics`],draft:!1,canary:!1,sample:!1,featured:!1,kind:`reference`,section:`virev`,collections:[`campaign-measurement`],cover:`/_blog/covers/choose-a-reporting-window-before-looking-at-results/cover.webp`,coverAlt:`Two parallel paths begin at release markers, with a short viewing span and a longer evergreen span followed by separate purchase and closure markers.`,sources:[{title:`How to Measure Influencer Marketing in 5 Steps (From Goal Setting to Reporting)`,url:`https://www.modash.io/blog/how-to-measure-influencer-marketing`,publisher:`Modash`,accessed:`2026-09-27`},{title:`Select attribution settings`,url:`https://support.google.com/analytics/answer/10597962?hl=en`,publisher:`Google Analytics Help`,accessed:`2026-09-27`},{title:`[GA4] Data freshness`,url:`https://support.google.com/analytics/answer/11198161?hl=en`,publisher:`Google Analytics Help`,accessed:`2026-09-27`},{title:`How engagement metrics are counted`,url:`https://support.google.com/youtube/answer/2991785?hl=en`,publisher:`YouTube Help`,accessed:`2026-09-27`},{title:`Marketing reports`,url:`https://help.shopify.com/en/manual/reports-and-analytics/shopify-reports/report-types/default-reports/marketing-reports`,publisher:`Shopify Help Center`,accessed:`2026-09-27`}],headings:[{depth:2,id:`write-down-three-separate-time-rules`,text:`Write down three separate time rules`},{depth:2,id:`choose-the-window-from-the-decision-deadline`,text:`Choose the window from the decision deadline`},{depth:2,id:`two-hypothetical-reporting-policies`,text:`Two hypothetical reporting policies`},{depth:2,id:`separate-activity-time-from-extraction-time`,text:`Separate activity time from extraction time`},{depth:2,id:`freeze-the-report-with-a-correction-log`,text:`Freeze the report with a correction log`}],stats:{words:1095,chars:6234}},{title:h,description:g,date:_,author:v,tags:y,draft:b,canary:x,sample:S,featured:C,kind:w,section:T,collections:E,cover:D,coverAlt:O,sources:k,headings:A,stats:j}=m,M=new Set([`$$slots`,`$$events`,`$$legacy`]),N=s(`<p>Choose the reporting window before the first creator posts. Measure each post at a fixed age, close the eligible purchase peri

1od on a stated date, then allow time for reporting corrections. Stop routine updates when that policy says to close. Keep later activity in a separate update, with the original report preserved.</p> <p>A seven-day post snapshot and a thirty-day attribution setting answer different questions. Treating them as one deadline can exclude eligible purchases or compare posts with unequal time to accumulate results.</p> <h2 id="write-down-three-separate-time-rules">Write down three separate time rules</h2> <div class="table-scroll" tabindex="0"><table><thead><tr><th>Rule</th><th>What it controls</th><th>What to record</th></tr></thead><tbody><tr><td>Publication time</td><td>The starting point for a post's age</td><td>Actual timestamp, time zone, post URL</td></tr><tr><td>Maturation window</td><td>How much time a post gets before comparison</td><td>For example, its first seven complete days</td></tr><tr><td>Conversion lookback</td><td>How far before a purchase an interaction can qualify for attribution</td><td>Tool, model, eligible interaction type, configured duration</td></tr></tbody></table></div> <p>Maturation is your reporting choice. It does not mean the platform stops distributing the post, or that later results have no value.</p> <p>Lookback is a rule inside your measurement system. <!> as the period in which earlier touchpoints can qualify for attribution credit. That window runs backward from the key event. It does not run forward from the creator's publication date.</p> <p>Also record the dates of interactions and purchases that your report includes. A thirty-day lookback alone does not specify either range. Nor does it guarantee that a creator receives all the credit; the attribution model determines how credit is assigned.</p> <p>This planning belongs before launch. <!> similarly recommends deciding goals and setting up tracking before posts go live. The policy below adds explicit closing rules.</p> <h2 id="choose-the-window-from-the-decision-deadline">Choose the window from the decision deadline</h2> <p>Start with the decision the report must support. A weekly creative review can use an early snapshot. A renewal decision based on attributed purchases needs time for the chosen purchase peri

1od to finish.</p> <p>Use this sequence:</p> <ol><li>Choose comparable post ages. Pick one primary age for each content format. Use earlier campaigns, when available, to judge whether that age captures enough activity for the decision.</li> <li>Confirm collection access. Agree who will supply the figures, from which report, and when. Mark unavailable figures as missing.</li> <li>Set purchase eligibility. Specify whether you report purchases occurring during calendar dates or purchases linked to interactions during a defined period.</li> <li>Record the attribution settings. Keep the model and lookback unchanged during the comparison.</li> <li>Set the freeze date. Allow a stated processing buffer after the last eligible purchase date. Assign someone to approve corrections afterward.</li></ol> <p>Avoid moving the cutoff because a particular creator's result looks disappointing. If a new window becomes necessary, explain the change and apply it to every comparable post.</p> <p>Collection can happen earlier than comparison. For time-sensitive material, use the <!> to plan collection separately from the campaign's final report.</p> <!><h2 id="two-hypothetical-reporting-policies">Two hypothetical reporting policies</h2> <p>These durations are examples for planning, not platform requirements or evidence that a post has finished earning attention. All offsets below use elapsed days from the actual publication timestamp, in UTC.</p> <div class="table-scroll" tabindex="0"><table><thead><tr><th>Policy field</th><th>Short-form launch post</th><th>Evergreen tutorial</th></tr></thead><tbody><tr><td>Early operational check</td><td>Day 1</td><td>Day 7</td></tr><tr><td>Post-performance comparison</td><td>Day 7</td><td>Day 30, followed by a scheduled day-90 update</td></tr><tr><td>Eligible creator-link interactions</td><td>Publication through day 7</td><td>Publication through day 90</td></tr><tr><td>Purchase lookback</td><td>30 days</td><td>30 days</td></tr><tr><td>Latest potentially eligible purchase</td><td>Day 37</td><td>Day 120</td></tr><tr><td>

1Administrative freeze, with a 14-day buffer</td><td>Day 51</td><td>Day 134</td></tr></tbody></table></div> <p>The short-form policy can deliver a day-seven content report while its purchase report remains provisional. For the evergreen policy, a day-thirty decision uses day-thirty results. The later report measures a different age and must carry that label. The <!> covers how to organize those recurring observations.</p> <p>The arithmetic follows the policy. In the short-form example, the last eligible interaction occurs seven days after publication. A thirty-day lookback allows a qualifying purchase as late as day 37. Adding the proposed fourteen-day processing buffer produces a day-51 administrative freeze. An interaction on day 10 falls outside this policy's interaction period, even if a purchase follows within thirty days.</p> <p>Use that approach only if your data can identify the eligible interaction period and apply the attribution rule. A purchase-date filter alone cannot establish an interaction cohort. If your tool cannot produce that view, report purchases by calendar period, name the lookback setting, and disclose that later interactions may contribute. Do not label that report "purchases from the post's first seven days."</p> <p>Google Analytics allows thirty-, sixty-, or ninety-day lookback settings for most key events other than acquisition events, according to its <!>. Check your actual setting before adopting an example.</p> <h2 id="separate-activity-time-from-extraction-time">Separate activity time from extraction time</h2> <p>Write both dates on every export. "Activity through day 7; extracted on day 9" tells a reader more than "week-one results."</p> <p>This distinction matters because platforms can revise counts. <!> and may change counts or discard low-quality playbacks. Its Realtime activity figures are estimates and can differ from the watch page.</p> <p><!>, which can take 24 to 48 hours. The same documentation says attribution credit for key events can change for up to twelve days after recording. The fourteen-day buffer above is an administrative recommendation. It does not guarantee permanent finality.</p> <p>If you can export a defined activity interval, retain that interval when refreshing the report. If you can only capture a cumulative count, record the actual capture time. A late cumulative screenshot includes later activity; it cannot recreate the exact day-seven count. Mark it late rather than relabeling it.</p> <h2 id="freeze-the-report-with-a-correction-log">Freeze the report with a correction log</h2> <p>At closure, save the export, filters, time zone, attribution settings, and calculation file. Preserve the approved version. A later correction should identify what changed and whether it affects the decision.</p> <p>Distinguish these cases:</p> <ul><li>A purchase occurred inside the eligible period but reached the report late. Record it as a late-data correction.</li> <li>A purchase occurred after the eligible period. Put it in a later-period update.</li> <li>The attribution model changed. Describe it as a methodology change and retain the old result.</li> <li>An order changed status. Apply the order-status policy agreed before reporting.</li></ul> <p>Order status deserves its own rule. <!> says those reports include canceled, pending, and unpaid orders. It also distinguishes sales values from money received. A reporting deadline alone cannot turn those totals into settled revenue.</p> <p>A hypothetical correction entry could read:</p> <figure class="code-block" data-lang="text"><figcaption class="code-lang">Text</figcaption><pre class="shiki github-light" style="background-color:#fff;color:#24292e" tabindex="0"><code><span class="line"><span>Version: 1.1</span></span>
2<span class="line"><span>Scope: Same eligible period and attribution settings as version 1.0</span></span>
3<span class="line"><span>Change: 40 eligible orders revised to 42</span></span>
4<span class="line"><span>Reason: Two eligible-period orders arrived after the export</span></span>
5<span class="line"><span>Excluded: Three orders placed after the purchase cutoff</span></span>
6<span class="line"><span>Decision impact: Renewal recommendation unchanged</span></span>
7<span class="line"><span>Approved by: Campaign reporting owner</span></span></code></pre></figure> <p>Before the next creator publishes, approve the post age, eligible purchase rule, extraction schedule, and freeze date in the same reporting brief.</p>`,1);function P(s,h){let g=i(h,M);p(s,c(()=>g,()=>m,{children:(i,s)=>{var c=N(),p=r(t(c),10),m=r(u(p));o(m,()=>f,(t,r)=>{r(t,{href:`https://support.google.com/analytics/answer/10597962?hl=en`,children:(t,r)=>{a();var i=n(`Google Analytics defines its key-event lookback window`);e(t,i)},$$slots:{default:!0}})}),a(),l(p);var h=r(p,4),g=r(u(h));o(g,()=>f,(t,r)=>{r(t,{href:`https://www.modash.io/blog/how-to-measure-influencer-marketing`,children:(t,r)=>{a();var i=n(`Modash's measurement guide`);e(t,i)},$$slots:{default:!0}})}),a(),l(h);var _=r(h,12),v=r(u(_));o(v,()=>f,(t,r)=>{r(t,{href:`/blog/request-instagram-story-results-before-evidence-disappears`,children:(t,r)=>{a();var i=n(`Instagram Story evidence request guide`);e(t,i)},$$slots:{default:!0}})}),a(),l(_);var y=r(_,2);o(y,()=>d,(e,t)=>{t(e,{position:`1`})});var b=r(y,7),x=r(u(b));o(x,()=>f,(t,r)=>

7{r(t,{href:`/blog/track-youtube-sponsorship-performance-over-time`,children:(t,r)=>{a();var i=n(`YouTube sponsorship tracking guide`);e(t,i)},$$slots:{default:!0}})}),a(),l(b);var S=r(b,6),C=r(u(S));o(C,()=>f,(t,r)=>{r(t,{href:`https://support.google.com/analytics/answer/10597962?hl=en`,children:(t,r)=>{a();var i=n(`attribution settings documentation`);e(t,i)},$$slots:{default:!0}})}),a(),l(S);var w=r(S,6),T=r(u(w));o(T,()=>f,(t,r)=>{r(t,{href:`https://support.google.com/youtube/answer/2991785?hl=en`,children:(t,r)=>{a();var i=n(`YouTube says it verifies engagement events`);e(t,i)},$$slots:{default:!0}})}),a(),l(w);var E=r(w,2),D=u(E);o(D,()=>f,(t,r)=>{r(t,{href:`https://support.google.com/analytics/answer/11198161?hl=en`,children:(t,r)=>{a();var i=n(`Google Analytics reports can change during processing`);e(t,i)},$$slots:{default:!0}})}),a(),l(E);var O=r(E,12),k=r(u(O));o(k,()=>f,(t,r)=>{r(t,{href:`https://help.shopify.com/en/manual/reports-and-analytics/shopify-reports/report-types/default-reports/marketing-reports`,children:(t,r)=>{a();var i=n(`Shopify's marketing-report documentation`);e(t,i)},$$slots:{default:!0}})}),a(),l(O),a(6),e(i,c)},$$slots:{default:!0}}))}export{P as default,m as metadata};