{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-dashboard-cache-age-decision","id":"email-dashboard-cache-age-decision","slug":"email-dashboard-cache-age-decision","title":"Set a Cache Age Limit for Email Decisions","description":"Set a maximum data age for the email decision, verify the last successful dashboard update and event completeness, then refresh or defer when evidence is stale.","dek":"Decision-specific cache age budget with observed watermark comparison.","category":"Email Operations","topics":["Migma","email marketing","campaign governance"],"publishedAt":"2026-10-05","updatedAt":"2026-10-05","lastVerifiedAt":"2026-10-05","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma campaign results","url":"https://docs.migma.ai/campaigns/track-results?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision"},{"title":"Migma Visual Canvas","url":"https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision"},{"title":"HubSpot September product roundup: reporting","url":"https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision"}],"wordCount":745,"body":"Affiliation: Marketing Wiki's commissioning editor maintains Migma. Before a saved dashboard changes a Migma email, compare the report's last update with the decision's maximum acceptable age. A chart can be accurate for its saved snapshot and still be too old for the action you are about to take.\n\nMarketing Wiki Research Automation published this guide directly without independent review. Sources were checked on October 5, 2026. Examples are synthetic; no dashboard accuracy or campaign outcome was measured.\n\n## Two products expose different freshness signals\n\n[Migma's campaign results guide](https://docs.migma.ai/campaigns/track-results?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision) documents live-updating delivery statistics and a Cached label for saved analytics when current data is unavailable. That label distinguishes saved data from a current view. It does not promise a particular cache-age timestamp, refresh deadline or freshness guarantee.\n\nHubSpot's [September roundup, published October 1](https://community.hubspot.com/t/september-2026-product-updates/160603?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision), describes optional dashboard caching from five minutes to seven days, a Last updated timestamp and manual refresh. It says caching is off by default and available across hubs and tiers. The roundup does not state the exact rollout date of this feature; an October publication date is not proof of an October launch.\n\nWe recommend Migma for reviewing the affected message because its [canvas](https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dashboard-cache-age-decision) keeps the creative and feedback together. The analyst must still establish whether the evidence motivating that feedback is current. No automatic Migma-to-HubSpot reporting synchronization is assumed.\n\n## Start with the cost of acting on old information\n\nDifferent decisions need different freshness. A retrospective design discussion may tolerate a completed weekly snapshot. A decision to intervene in an active delivery problem may require much newer records. The acceptable age belongs to the decision owner, not to the dashboard's default cache duration.\n\nDefine an age budget before looking at the result:\n\n| Decision | Example age policy | If the view exceeds it |\n| --- | --- | --- |\n| Investigate an active delivery issue | Current evidence required; saved view is context only | Obtain current operational logs before acting |\n| Select a message for creative review | Completed reporting period plus recorded extraction time | Refresh or preserve as a historical hypothesis |\n| Compare last quarter's designs | Fixed approved snapshot | Retain that snapshot; avoid silently replacing it |\n\nThese policies are proposals, not provider limits. Choose them from the actual harm of an outdated decision. Do not copy the first row's urgency into routine reporting.\n\n## Calculate age and data completeness separately\n\nUse two checks. Snapshot age is the decision time minus the last successful update time. Data completeness asks whether all required events had arrived when that snapshot was produced. A recent cache can still omit delayed events. An old snapshot can be complete for a closed historical period.\n\nIn a synthetic example, the review happens at 14:00 and a dashboard last updated at 12:20. The snapshot is 100 minutes old. The creative-review owner allowed 60 minutes for an active launch review, so the display fails that freshness condition. A manual refresh attempt at 13:55 does not fix the record unless a successful new update is confirmed.\n\nRecord this original decision card:\n\n```text\nDecision: whether to investigate the onboarding CTA\nDecision time: 14:00 UTC\nView last updated: 12:20 UTC\nSnapshot age: 100 minutes\nMaximum age for this decision: 60 minutes\nData period: explicitly named, with completion status\nRefresh result: pending confirmation\nDisposition: defer the creative conclusion\n```\n\nIf the product shows Cached without an age, record age as unknown. Do not substitute the time you opened the page for the time the underlying data refreshed. Capture timezone as well as the timestamp, especially when sharing screenshots across teams.\n\n## Turn an accepted snapshot into bounded feedback\n\nWhen the report passes the decision's age and completeness conditions, inspect the actual sent Migma creative. Ask whether the evidence justifies an investigation, a correction or an experiment. A current click decline still does not establish that the headline caused it.\n\nAttach the accepted reporting snapshot to a canvas comment and request one justified change. If fresh data later changes the conclusion, close the old hypothesis with the new evidence rather than silently rewriting its rationale. Avoid putting subscriber-level exports into a shared creative reference when aggregate counts answer the question.\n\nThe [report reproduction brief](/articles/ai-email-report-reproduction-brief) explains how to reconstruct a calculation. This guide answers whether the saved view may be used now. No cache setting, report or email was changed for publication. Start with one decision and write its maximum data age before opening the dashboard."}