Analytics

Analytics combines first-party events, Upsurge product assistance, and optional provider-reported advertising data. The dashboard keeps referral attribution and product assistance separate so assisted value is not mistaken for attributed or complete store revenue.

Start with scope and filters

1. Choose a date preset (Today, Yesterday, Last 7 days, Last 30 days, This month, Last month).
2. Select All sites or one site.
3. Filter the campaign type: overlay, recommendation, chatbot, or ads.
4. Open Filters to choose a data source (All data sources, Store activity, Product campaigns, Ad spend, or Integrations) and to add activity filters.
5. Select refresh and note the Last updated time.

Activity filters narrow recorded storefront activity by traffic channel, traffic source, traffic medium, UTM campaign, referring site, landing page, visited page, country, visitor type, device type, browser, operating system, and browser language. Filters combine with AND.

When ad data appears

Ad spend and reported ROAS load only when All sites is selected and no activity filters are applied.

Dates are normalized to avoid local/UTC off-by-one errors. When comparing an external report, use the same timezone, inclusive boundaries, currency, and conversion definition.

Core metrics

The KPI row shows Revenue, Conversions, Conversion rate, Sessions, Ad spend, and Reported ROAS.

• The chart shows activity by day, week, or month.
• Insights break activity down by countries, new vs returning visitors, traffic sources, device types, and landing pages.
• The campaign performance table switches between Campaigns and Traffic sources; traffic sources group by channel or by source / medium.

Attribution scopes

Each figure is labeled with its measurement source: Upsurge assisted, Upsurge observed, Ad platform, Full store, or Multiple sources.

Scope	Meaning
product_observed	Store conversions observed by Upsurge without assigning product credit.
product_assisted	Conversions where a signed Upsurge product touch occurred inside the configured window; this carries zero referral credit.
provider_reported	Conversion counts or value reported by an advertising provider.
full_site_imported	Reserved for a trusted full-store order import. No current integration provides it.
mixed_partial	Multiple incomplete sources are present.

Partial attribution

Ad spend without a full-site conversion import is not enough to claim global ROI. Keep product assistance, referral attribution, and provider-reported figures separate and label partial coverage. Assisted value is non-additive with attributed or provider-reported revenue.

Campaign performance

The normalized campaign table combines overlay, recommendation, chatbot, and ad rows. Product rows show Upsurge-assisted conversions and assisted value without taking referral credit; ad rows preserve provider conversions, conversion value, spend, and ROAS.

Use campaign IDs and site filters when comparing against SDK lifecycle events. If a campaign has activity but no assisted conversion, confirm that a signed product touch and canonical commerce conversion share the storefront journey inside the configured window.

Audiences

The Audiences tab builds reusable shopper audiences for targeting and reporting. See Audiences.

Saved reports and export

Select Create report to open the report builder. A saved report stores a name, data sources (including traffic sources), metrics, dimensions, filters, audiences, and a visualization: line, bar, table, or funnel. Reopen saved reports from Saved reports. Scheduled report delivery is not currently available.

Export the current view as CSV or JSON. Exporting requires the Export analytics permission. Preserve filter and attribution context alongside exported rows so downstream readers do not infer broader coverage.

Related views

• Conversions lists individual conversion records.
• Partner Intelligence reconciles AWIN and CJ partner results with store orders.
• Smart Search analytics reports search performance.

Data freshness and health

Event ingestion acknowledges accepted data before every dashboard aggregate is necessarily visible. A short delay can occur through publishing and Pinot-backed query paths.

If data is missing:

1. confirm the event ingestion response and per-item batch results;
2. check today’s date range, site, data source, and campaign filters;
3. verify stable event and campaign IDs;
4. refresh after the expected processing delay;
5. compare health and source status before concluding the event was lost.

API relationships

Dashboard reads use /api/v1/analytics/metrics, /timeseries, /top, /campaign-performance, /overlays, /recommendations, /ads, /attribution, /partners, and /publishers. Saved definitions use /analytics/reports, and audiences use /cohorts. These routes require merchant authentication and derive workspace scope from the verified user token.

Some routes limit the date range: /ads accepts up to 366 days, /recommendations up to 90 days, and /partners, /publishers, and /attribution up to 763 days.

See the API endpoint catalog and event ingestion reference.