Ask Dash · Monday Brief · Help chat (metered from real token usage)$12.40 / $100.00
Per-feature breakdown and a 30-day spend trend need a per-call event log (coming soon) — today this is the combined running total.
TRACKING & DATA QUALITY
all clear · live checks
✓
Order tracking (GA4 ↔ Woo)
GA4 942 purchases vs Woo 942 orders — 0% gap
✓
Revenue tracking (GA4 ↔ Woo)
GA4 $178,900.00 vs Woo $182,450.00 — 2% gap
✓
Snapshots fresh
oldest of website/traffic/search is 0 min old (cron target ≤ 60)
✓
Warehouse current
latest daily point 2026-07-13 (0.0d ago)
•
Search Console freshness
41,300 clicks tracked · GSC reports on a ~2–3 day delay (Google-side); the most recent days backfill later
✓
Catalog hygiene
Top category "Signature Line" maps to a real product group
CROSS-CHANNEL ATTRIBUTION
3/4 ready · individual-journey tracking
✓
Order → traffic source
Orders carry a source via WooCommerce Order Attribution (e.g. "google / organic") — usable for last-touch channel attribution today
✓
First-party visitor tracking
Live — 412,300 events from 138,400 visitors (30d), stored first-party in our own event log. Last event 7/13/2026, 9:00:07 PM.
✓
Identity stitching (visitor ↔ email)
41,200 visitors tied to an email · 29.8% of 30-day visitors identified. Call DemoTrack.identify(email) at checkout/signup to raise this.
•
GA4 raw export (BigQuery)
GA4's reporting API is aggregated/sampled. True per-user cross-channel paths need the free GA4 → BigQuery export (row-level events keyed by client_id) to join against orders + email.
VISITORS (30D)
138,400
486,900 pageviews
IDENTIFIED
41,200
29.8% of 30-day visitors
TOP REFERRER
google
52,200 views
INSTALL FIRST-PARTY TRACKING
Paste this once into the storefront (WordPress: Appearance → theme header, or a headers/footers plugin). It sets a first-party visitor-id cookie on your domain and logs pageviews to your own store.
Then, on the order-confirmation and account-signup pages, call this with the customer's email to stitch their anonymous journey to the customer record:
DemoTrack.identify("customer@email.com");
WooCommerce tip: the identify call can go in the Thank-You (order-received) template, passing the billing email. It only needs to fire once per known email.
Minimum path to channel attribution: (1) turn on order-source capture, (2) drop a first-party visitor-id cookie + /api/track, (3) identify visitor→email at checkout. First/last-touch and multi-touch models then become a query over the joined event stream.