What works today

This page tells you what you can rely on in Clear Saga right now, and what you cannot. Read it before you plan around a feature. Other pages link here from the sentence where a gap matters.

There are three groups. The first works from end to end. The second is built inside the product and waits for a connection to an outside service. The third is not built.

Built and working #

• Counting visits. The tag, both scripts, page views on sites that change pages without a reload, and the installation check. See add the tracker and the install guides.
• Privacy. No cookies by default, no stored IP address, a visitor code that changes every day, and the browser's privacy signals honoured. See privacy: cookieless by default.
• Returning visitors. One switch per site, off by default, that remembers visitors who agreed with a cookie: the Visitors list, profiles with their journey, and the tools to find and delete a visitor. See returning visitors.
• The dashboard. Visitors, visits, page views, pages, sources, locations and devices, with date ranges and comparison. See the dashboard.
• Filters and saved segments. See filters and saved segments.
• Realtime. Who is on the site now, on a live screen, with a card for each live visit that says how likely such visitors are to convert. See Realtime.
• Custom events, conversion goals and funnels. See custom events, conversion goals and funnels.
• Campaigns. UTM tags and the campaign link builder. See campaigns.
• Shopify orders. Paid orders and refunds of a connected store, credited to visits. See connect Shopify and revenue.
• Ad attribution. One switch per site, off by default. Switched on, it collects the ad click behind a visit and a private customer key on each Shopify order, and the store reports use them. Ad platform accounts are listed but cannot be connected yet, as the waiting list below says. See ad attribution.
• Store reports. Five pages for a site with orders, with six attribution models and a tag on every number that says what it covers: the Store summary, Which ads earned sales, the Creative report, the Profit report and New customers. They run on ad spend uploaded as a CSV file and on the demo's seeded spend. See attribution models.
• Costs and CSV upload. A Costs tab under Settings for shipping, payment fees, product costs by hand or from a CSV file, other costs, and ad spend uploaded as a CSV file. See costs and CSV upload.
• Missing pages. See 404 tracking.
• Web vitals. See performance and web vitals.
• Bot filtering and exclusion rules. See bot filtering and excluding visits.
• Shared dashboards and embed widgets. A read-only link, and widgets for your own pages. See shared dashboards and embed widgets.
• CSV export. See data export.
• Alert rules delivered by webhook. See alerts and webhooks.
• Accounts, workspaces and roles. Sign-up, sign-in, sessions, invitations by link, and the owner, admin and viewer roles. See your account and signing in and team and roles.
• Plans and metering. The trial, the monthly count of events, the usage meter and the locks at the limit all work. Only the payment itself is missing. See plans, usage and limits.
• Tokens, the API, the MCP server and the command line. See connect an AI agent, the API reference, the MCP server and the command line.

Not finished #

The two lists below are printed from one list kept with the product's code, so every page that links here reads the same list.

Built, waiting for an outside connection

• Email delivery. No email is sent. Invitations, password resets, usage warnings, traffic alerts, the weekly digest and the monthly report are written and stored, and none of them reaches an inbox. An invited person has to be given their link by hand, and a person who forgets their password gets no message.
• Payment. No payment is taken. Choosing a plan charges nothing, and the prices shown are placeholders.
• Payment providers other than Shopify. Shopify stores are connected through two webhooks and record real orders and refunds. No other store or payment provider can be connected yet: their cards read as not connected and nothing records an order from them. Orders Shopify failed to deliver are not reconciled.
• Google Search Console. Search Console is not connected, so the dashboard shows no search keywords.
• Ad platform accounts. The store reports are built and run on spend uploaded as a CSV under Settings, Costs, and on the demo's seeded spend. Meta Ads, Google Ads, TikTok Ads, Pinterest Ads and Amazon Ads accounts cannot be connected yet, so no spend arrives by itself, and the Creative report shows no thumbnails for uploaded spend.

Not built

• Importing history. History from another analytics tool cannot be imported. The screen lists the sources and uploads nothing.
• Cross-domain visitor handoff. The cross-domain option exists on the tag and in the settings and does not follow a visitor. A visitor who moves from one domain to another is counted once on each.
• First-party collection. The script and its requests cannot be served from your own domain. The Installation screen has a section for it that says so.
• Email copies of alert rules. An alert rule on a goal or a funnel is delivered by webhook only. No email copy is written.
• Trial and grace reminders. No reminder is written when a trial is about to end or a plan has lapsed. The dashboard shows the days that are left.
• Naming a visitor. A visitor cannot be given a name or an email. Profiles are a random id.
• Consent platforms. No consent platform is connected. A site's own banner calls one function of the tracker, and Shopify's banner is read through Shopify's own API.
• One-click Connect for the Claude and ChatGPT apps. The Claude and ChatGPT apps cannot connect to the MCP server, because the sign-in flow they need is not built. Clients that accept a token in a header can connect.
• The command line tool on npm. The command line tool is not published to npm. It is installed from a file built from the source.
• Public profile pages. There are no public profile pages. To show numbers to people without an account, use a shared dashboard link.
• A choice of data region. There is no setting for where data is stored and no hosting that is limited to the European Union.
• Data processing agreement. The privacy policy, the terms of service and the data deletion steps are published. There is no data processing agreement to sign yet.
• Amazon Seller Central orders and fees. Amazon Seller Central cannot be connected, so Amazon orders and Amazon fees are not in the store reports or in profit.
• The Shopify App Store app. There is no app on the Shopify App Store. A store connects through two webhooks, and product costs are entered under Settings, Costs instead of read from Shopify.
• An "ask a question" box. The dashboard has no box to ask a question about your numbers. An AI agent connected to the MCP server can ask the same questions.
• Sending conversions to ad platforms. Nothing is sent back to an ad platform: no Conversions API, no Enhanced Conversions and no offline conversion upload.
• Marketing mix modelling. There is no marketing mix model, incrementality test or geo holdout. Credit comes from the visits before each order, and the view models estimate from daily platform totals.

How to read this page #

• Waiting for an outside connection means the part inside the product is done. An email, for example, is written with the right content at the right moment and stored. What is missing is the service that would deliver it. Until then, assume the thing does not happen: nobody receives the message.
• Not built means there is nothing behind the screen or the option, even where one is shown. Do not plan around these.
• No dates are given here, on purpose. An item moves to the first list on this page when it works, and not before.

If a page in these docs describes something that does not work for you and that is not listed here, the page is wrong. The troubleshooting page is the place to start for a tag that sends nothing.

Next: Quick start, Your account and signing in, Plans, usage and limits