Released September 15, 2025
Summary
We’re rolling out
Omni V2
and introducing new
Omni models
in direct response to merchant feedback since our June app launch. The update gives teams a choice between:
  • Harmonized Date
    views that align all sources to the same most-recent fully-available week (ideal when anchoring the business to lagging syndicated sources like NielsenIQ/SPINS), and
  • Latest Week
    views that always show each source’s most current week (ideal for fast-moving eCom/retail operations where recency is preferred).
What’s New
  • Omni V1 → Omni V2
    data model migration (metrics parity maintained).
  • New
    Omni explores
    supporting both
    Harmonized Date
    and
    Latest Week
    reporting modes.
  • Anchor‑date logic applied to harmonize across sources when needed.
  • V1 explores will be
    renamed and retired
    after validation is complete.
Explores Added/Updated
The following explores are now available in two parallel variants:
  • dm_omni_company_performance_harmonized_date.explore.lkml
  • dm_omni_company_performance_latest_week.explore.lkml
  • dm_omni_omnichannel_sales_harmonized_date.explore.lkml
  • dm_omni_omnichannel_sales_latest_week.explore.lkml
Data Model Logic:
Company Performance vs Omnichannel
  • Company Performance
    : These (2) omnichannel explores are filtered to only your brand, and non-duplicative markets that total up to total enterprise sales.
  • Omnichannel
    : These (2) omnichannel explores include all available markets and products. These will enable competitive analysis on top of the omnichannel market view (combine your syndicated data with POS retailer portals, for a total universe category analysis.
Date Alignment across Data Sources: Harmonized vs Latest Week
  • Harmonized Date
    : Aligns all included sources to the most recent
    common
    complete week (e.g., when syndicated data lags 1–3+ weeks, you can still make apples‑to‑apples comparisons across channels against that same anchor week).
    Typically useful company performance analysis with a lagging data source, like syndicated data (SPINS/NielsenIQ/Circana)
  • Latest Week
    : Surfaces the freshest available data per source (useful for near‑real‑time ops and pacing without forcing older lagging sources to gate the view). Updates weekly on Mondays with week through the day prior (all sources normalized to week ending Sunday).
How to Choose: Harmonized vs Latest Week
  • Choose
    Harmonized Date
    if leadership or FP&A wants to anchor the weekly business review to
    syndicated (NielsenIQ/SPINS) timelines
    and maintain strict apples‑to‑apples comparisons.
  • Choose
    Latest Week
    if your operational cadence prioritizes
    recency
    (e.g., eCom performance, retailer week closures) and you accept that syndicated datasets will trail.
Tip:
Many teams adopt
Harmonized Date
for executive/board and
Latest Week
for day‑to‑day operations.
---
Rollout & Impact
  • Who is affected
    : All merchants using Omni explores. (Note: this has NOT impacted home page dashboard yet, but will in a following release. Should not impact your use of the homepage, and we will update again when that is copleted.
  • Dashboards
    : Expect
    no or minimal changes
    ; any differences will be documented during validation.
  • Custom YAMLs
    : We are updating custom YAMLs as part of the rollout for all teams with custom Omni data model development or dashboards.
  • Deprecation
    : V1 will be renamed and removed post‑validation.
Why It Matters
  • Preserves
    metrics parity
    while giving you
    flexibility
    to match your org’s preferred reporting cadence.
  • Reduces reconciliation friction between
    omnichannel
    and
    syndicated
    timelines.
  • Directly addresses top feedback themes from the June launch around
    date alignment
    and
    data lag
    .