Skip to content

What's new in TraceLog

Everything we ship to TraceLog, in plain language — newest first. We're in active beta, so expect frequent improvements.

  1. Improved

    TraceLog now detects when your snippet is installed with a wrong project ID

    If your snippet is live on the store but uses an unrecognized project ID, the Tracking Health and setup pages now show a clear diagnostic instead of silently dropping your events.

  2. Improved

    Core Web Vitals now measured from every page load, not just slow ones

    TraceLog now collects performance metrics from every navigation on your store, giving a complete and unbiased picture of how it loads across all visits — not just the sessions where something was slow.

  3. Improved

    Analytics now shows how much of your revenue is unattributed

    Traffic and revenue breakdowns include an 'Unattributed' row with a coverage percentage, so you always know what share of your store's business has a clear source and what doesn't.

  4. Improved

    Overview KPIs now confirm when everything is within normal range

    KPI cards now show a 'within normal range' label when your metrics are behaving as expected — giving you quick positive confirmation alongside the usual alerts when something needs attention.

  5. Fix

    Conversion rates no longer show 0% when the sample is too small to be reliable

    Analytics, reports, and Ask now withhold the conversion rate figure — rather than showing 0% — when there isn't enough traffic to compute a meaningful rate, so you're never misled by an artificially low number.

  6. New

    AI assistant traffic now shows as its own channel in analytics

    Visits referred by AI assistants — ChatGPT, Perplexity, and similar tools — are now grouped into a dedicated traffic source so you can see whether AI-referred shoppers convert differently from search, social, or direct traffic.

  7. Improved

    TraceLog now warns you when revenue tracking is set up but no purchases have come through

    If you've completed the revenue integration but TraceLog hasn't received any purchase events yet, the setup page now flags it clearly — so you can catch a silent misconfiguration before it leaves gaps in your revenue data.

  8. Fix

    WooCommerce plugin now retries order events that fail to send

    Fixed a bug in the WooCommerce plugin where order events that couldn't be delivered were silently discarded instead of retried, which could leave quiet gaps in your revenue data.

  9. Improved

    Dashboard and reports now show when automated sessions have been excluded from your metrics

    Session counts and conversion metrics now include a disclosure of how many automated visits were excluded, so you always know your numbers represent real shoppers rather than bots or crawlers.

  10. New

    Generate your weekly report scoped to one campaign

    You can now scope a weekly report to a single UTM campaign when generating it. The campaign name appears in the report headline and on the reports list, and the scope travels with the shared link so teammates always know what they're looking at.

  11. Improved

    Weekly reports now include a verdict, top products, revenue delta, and recovered revenue

    Reports now open with a headline verdict summarizing your week, followed by a revenue-vs-last-period block, the top products sold across campaigns, a new-vs-returning breakdown, and a recovered revenue highlight when applicable. The weekly digest email now links directly to that week's full report.

  12. Improved

    Error issues now show which real visitors were affected — and separate bot traffic

    When TraceLog surfaces a JavaScript error issue, the evidence panel now shows reproduction context: which visitor segments encountered the error and whether automated traffic accounts for a meaningful share of the affected count — so you can focus on what your real shoppers experienced.

  13. Fix

    Revenue figures now labelled as gross of refunds

    Revenue figures across the dashboard and in reports now explicitly state they are gross of refunds, making them straightforward to reconcile with the net revenue shown in your store's admin.

  14. Improved

    Opportunities ranked by estimated revenue impact, with two new cohort detectors

    The opportunity queue in the Overview now sorts actions by estimated revenue magnitude — the highest-impact item always comes first. Two new detectors have also been added: one flags when mobile and desktop visitors convert at significantly different rates, and another highlights gaps between new and returning buyers.

  15. Improved

    Fewer false alarms — anomaly and conversion-drop detectors are now more precise

    Duplicate traffic anomaly cards no longer accumulate in the Overview; a resolved alert is not re-fired once the store recovers; conversion-drop detectors now require sufficient week-over-week coverage before raising an alert; and patterns that have already reversed no longer keep triggering new issues.

  16. New

    New detector: TraceLog now spots when a traffic channel loses volume

    TraceLog can now detect when a specific channel — paid social, email, organic, or direct — is sending significantly fewer visitors than its own recent baseline, not just when those visitors convert poorly. The finding appears in your opportunities queue so you can investigate before the shortfall compounds.

  17. New

    Average order value and order count now in your KPI strip

    A new KPI card shows your average order value alongside sessions and conversion rate. Your order count for the selected period is shown too — so you can see whether a revenue shift was driven by more orders, bigger baskets, or a mix of both.

  18. New

    Overview rebuilt: revenue at risk, trend charts, and top opportunities in one view

    The Overview has been rebuilt around four zones: a money band showing your estimated weekly revenue at risk, KPI and trend charts for sessions and conversion rate, a prioritised opportunity queue with the highest-impact actions right now, and a recent reports zone. The number of issues you have resolved is also shown directly on the dashboard.

  19. Improved

    Weekly reports now arrive on a schedule and carry richer campaign and issue summaries

    TraceLog now generates your weekly performance report on an automatic schedule. Reports include clearer campaign performance metrics and a summary of active issues, so the picture of your week is ready for you without any manual step.

  20. New

    TraceLog now suggests copy improvements for the pages dragging down your conversion

    When a detected issue points to a specific product or landing page, TraceLog now generates a copy suggestion — showing the current text side by side with a proposed revision. The suggestion also appears in your weekly report so you can pass it directly to whoever manages your content.

  21. New

    TraceLog now flags when a region is outperforming the rest of your store

    A new detector surfaces when a specific country or region is converting significantly above your store's average. The finding appears in your opportunities queue so you can decide whether to invest in growing that region.

  22. Improved

    Conversion rate now available as a trend chart in Analytics

    You can now chart your conversion rate over time alongside sessions and revenue. Compare how your rate shifted across campaigns or after a site change — without leaving TraceLog.

  23. New

    WooCommerce stores can now configure revenue tracking from inside TraceLog

    The revenue setup wizard now includes a dedicated WooCommerce path with a managed plugin download and PHP snippet. TraceLog automatically maps the standard WooCommerce order structure to its revenue model, so your order data flows in without manual field configuration. A built-in guard also flags integrations that consistently report the same order value — catching a common misconfiguration before it pollutes your revenue figures.

  24. New

    Shopify merchants can now track checkout events via Custom Web Pixel

    TraceLog now supports Shopify's Custom Web Pixel as an additional tracking path. Stores that install the pixel can capture checkout events — including purchases — directly from Shopify's sandbox environment and have them appear in TraceLog analytics.

  25. New

    TraceLog now detects when your tracking stops — and tells you before it affects your analysis

    The Tracking Health view now detects when your event volume collapses unexpectedly — distinguishing a real data outage from a quiet period — and surfaces the cause directly on the page. Alerts for tracking issues now hold back while a potential outage is still resolving, reducing false alarms when the problem has already self-corrected.

  26. New

    TraceLog now celebrates your strong weeks, not just the problems

    A milestone card now appears in the Overview when your store has an especially strong week — solid conversion, healthy traffic, no critical issues. Good performance deserves to be noticed.

  27. Fix

    Fewer false alarms — issue counts and severity now backed by cleaner data

    Session counts in detected issues now exclude bot and phantom activity. Core Web Vitals scores use statistically robust p75 measurements instead of inflated means. Checkout friction and conversion-drop detectors no longer raise alerts when the underlying pattern has already reversed.

  28. New

    See which traffic source is underperforming — right on your Overview

    A new persistent card on the Overview highlights when a traffic source — paid social, email, organic — is converting below its own usual rate, with the estimated weekly revenue at stake. Tap through to the source × landing explorer to find the specific pages where the gap is widest.

  29. New

    Checkout funnel breakdown shown directly on the issue detail

    When TraceLog detects checkout friction, the issue detail now shows the full funnel — which step is losing the most buyers compared to its own baseline — so you know exactly where your checkout is leaking before deciding what to fix.

  30. Improved

    JavaScript error alerts fire less, and show the errors that matter most

    JS error alerts now only trigger when errors reach a meaningful share of your visitors. The issue card also surfaces the specific errors causing the most impact, so you spend less time on noise and more time fixing what is hurting your store.

  31. Improved

    Overview redesigned with a sticky context rail

    The Overview now uses a two-column layout: a sticky rail on the right keeps your store's readiness state and recovery history in view as you scroll through issues and recommendations — less hunting, more deciding.

  32. Improved

    Ask is now one tap away from anywhere in the dashboard

    The Ask button is now a persistent floating button visible on every page — Analytics, Tracking, Settings, and beyond. You can ask TraceLog a question about your store without navigating back to Overview first.

  33. New

    See your estimated weekly revenue at risk during setup

    The setup progress screen now shows the estimated weekly revenue at risk while you configure TraceLog — so you can see what is on the line before the first insights arrive.

  34. Improved

    Complete setup and hand off to your developer before the first event arrives

    You can now finish the setup checklist and send the developer handoff guide without waiting for live tracked events. TraceLog activates automatically the moment your data starts flowing — setup no longer blocks on having traffic first.

  35. Fix

    Ask no longer overstates revenue impact when confidence is low

    Ask previously could cite inflated revenue figures when your store's data history was too thin to support the estimate. It now withholds the monetary callout when confidence is insufficient — so the numbers you see are defensible, not projections.

  36. New

    Choose who receives alert emails, per project

    You can now select exactly which team members receive alert emails for each project. The project owner is included by default, and you can add or remove recipients directly from the alerts settings.

  37. Improved

    Alerts lead with conversion impact — and fire far less on noise

    Alert messages now open with the estimated conversion impact so you see the business cost at a glance. Several sources of false positives have been eliminated: low-traffic nights, TikTok Pixel technical errors, and thin revenue history no longer trigger alerts incorrectly.

  38. Improved

    Funnel analysis stays available even under heavy load

    Funnel and campaign analysis now degrades gracefully when queries take longer than expected — falling back to the most recent precomputed data instead of showing an error. You see numbers, not a blank page, during traffic spikes.

  39. New

    Control how often you receive alert emails

    Alerts now default to a weekly digest so they don't fragment your day. You can switch to instant notifications in the alerts settings if you prefer to be reached the moment an issue is detected.

  40. New

    New funnel preset for stores tracking checkout via page views

    Shopify stores that don't have Web Pixel events enabled can now use a ready-made page-view funnel to track the full checkout journey — no custom configuration needed to get started.

  41. Fix

    Revenue estimates only shown when backed by real history

    The revenue exposure band is now hidden when your store doesn't have enough order history to calculate a reliable baseline, so you never see a misleading estimate in place of real data.

  42. Improved

    Issue cards now show reach, exposure and fix suggestions at a glance

    The issues queue in Overview now shows how many sessions and how much revenue are at risk per issue, alongside a preview of the fix recommendation — so you can prioritize without clicking into each card.

  43. Fix

    Affected session rate now shown as a percentage, not a decimal

    Fixed a display issue where the share of sessions affected by a detected issue appeared as a raw decimal (e.g. 0.05) instead of a readable percentage (5%).

  44. Improved

    Exit-page breakdown and untagged UTM campaigns now tracked

    Analytics now surfaces the pages where visitors exit most often, and groups traffic from untagged UTM campaigns into a dedicated segment — giving you a cleaner view of where your funnel leaks.

  45. Fix

    Paid traffic classification now matches GA4

    Traffic from paid social, retargeting, and cost-per-* campaigns is now classified the same way as GA4, so your source breakdowns stay consistent when you cross-reference with other tools.

  46. Fix

    No more silent gaps when the server sends an empty error

    Fixed a case where an empty error response from the ingest server could cause your analytics event batch to fail silently, leaving gaps in your store data.

  47. New

    Your analytics, reorganized into clear tabs

    The analytics area is now split into focused tabs — Analytics, Landing pages, Funnels and Visitors — with a date-range compare toggle and an export menu. Your Home stays the place where the day's priorities land.

  48. Improved

    Deeper breakdowns by source, segment and landing

    Analytics breakdowns now carry more per-dimension detail, so it's easier to see where your conversion comes from — and where it leaks.

  49. Improved

    A faster, more stable dashboard

    We hardened how analytics data loads — timeout protection and cleaner handling of overlapping requests — so the dashboard is quicker and steadier under load.

  50. New

    See estimated € upside, not just leaks

    The Source × landing breakdown now shows an estimated gain per cell, so you can spot where there's room to grow — not only where you're losing conversions.

  51. Improved

    Ask is sharper — and knows what it recovered for you

    Ask runs on an upgraded AI model and now has your recovered-revenue track record in context. Ask it directly how much TraceLog has helped you recover. Answers are still verified against your real metrics.

  52. Fix

    No more silent data gaps during the beta

    We made data ingestion more forgiving while you're in the beta, so a domain mismatch never quietly stops your data. Revenue capture is also more precise.