Crisper51 min read19 views

How to know when conversion tracking stops working

Crisper tells you when a website stops sending events or conversions: the dashboard bell, one daily email, alert rules and an All websites view.

The short answer

Crisper tells you when tracking breaks. The dashboard bell shows every alert as it happens, one Daily tracking check email lists the websites still quiet, and All websites shows which sites need attention. A quiet spell is a reason to check, not proof of a fault, so open the website's Logs next.

  • Bell: Needs fixing lists websites that stopped sending events or conversions, and unverified tracking domains.
  • Email: one Daily tracking check at 13:00 UTC, only for websites still quiet.
  • Defaults: no tracked events alerts after 24 hours; set the minimum wait for purchases or leads yourself.
  • All websites is the page you land on, with a delivery check on every conversion.
  • Checked against Crisper's dashboard and changelog on 7 November 2026.

Ask an assistant

ChatGPTClaudePerplexity

FREE AUDIT

NO LOGIN

Check what Meta and Google can count on your site

  1. Your site
  2. Crisper
  3. Meta and Google count it

Enter your website to see how good its tracking is, and whether Meta is likely restricting it.

Run a free audit

Crisper watches each website for you and tells you in three places: the bell in your dashboard, one Daily tracking check email, and the All websites page. You don't need to remember to open Events Manager to find out that purchases or leads stopped.

This page covers ongoing monitoring: what each alert means, how to set it and what to do when one arrives. For a one-off check that Meta receives your events, use the verification checklist.

Each platform reports on its own conversions: Google Ads explains how it tracks website conversionssupport.google.com, and Google Analytics shows how to confirm you're collecting datasupport.google.com. Crisper's alerts watch every website you track in one place and tell you when its events or conversions stop arriving.

How do you change the dashboard's colours?

You can now pick a theme and an accent colour for your dashboard. There are six themes: Light, Paper and High contrast for a light page, and Dark, Dusk and Midnight for a dark one. The four accents are Blue, Violet, Magenta and Graphite. Light and Dark with Blue are the dashboard's usual look.

Pick a theme and an accent

Where to find it: Dashboard → Settings → Themes, under Preferences

Each theme tile shows a small drawing of the dashboard in that theme, and choosing one changes the whole dashboard. Your accent sets the colour of buttons, links and focus rings. The sidebar stays dark in every theme, tinted to suit it. Your pick is saved to your account, so it follows you to another browser, and each teammate keeps their own.

When to use it: When you would like the dashboard paler, warmer, higher in contrast or darker than its usual look.

Fig. 1Sample data · example.com. Settings → Themes with the Dusk theme and the Violet accent. Captured from the shipped component; illustrative, not a customer's account.

Pick a theme and accent from the top bar

The sun or moon button at the top of the dashboard now opens a small picker with the same six themes and four accents as Settings → Themes. Choosing a theme for the other mode, such as Dusk while the dashboard is light, switches to it. All theme settings opens Settings → Themes, and Reset to default goes back to Light with the Blue accent; it is greyed out while you already use the default.

As shipped on 15 November: The sun and moon button at the top of the dashboard still switches between light and dark. It now opens your last light theme or your last dark theme, so once you pick Dusk, switching to dark brings you back to Dusk. Since 18 November, the button opens the picker instead.

What does a theme not change?

Status and chart colours stay the same in every theme and accent, so green, amber, red and the blue that marks something in progress mean the same everywhere. Onboarding and crisper.io's public pages keep Crisper's own look. A theme changes how the dashboard looks, not your data, alerts or settings.

Read next

What an empty dashboard page tells you to do, where a page's status and main button sit, or what to do when an alert arrives.

What does an empty dashboard page tell you to do?

An empty dashboard page now says why it is empty and offers the one thing to do next. Empty pages share one look: an icon, a title, one line about your site, at most one button, and on most pages a Need help? row with Email, WhatsApp and Chat. Your remaining setup steps sit in one amber band at the top of a website's pages.

See why a page is empty and what to do

Where to find it: Dashboard → All websites, Integrations or Billing, or open a website → Logs, Integrations or Product feed

With no websites yet, All websites reads Add your first client site. Since 15 November, a new account with no website and no billing sees Book your onboarding call there instead, with Pick a time and Add website yourself. An empty Logs page names its cause: your setup call is still to come, the tracking code hasn't been seen on your site yet, with Install tracking code, or nothing matches your dates and filters. The Logs filter now reads All events instead of a code.

When to use it: When a page shows nothing and you want to know whether to wait, fix something or ask.

Ask for help from the page you are on

Under Need help?, Email opens a message whose subject names the page and your site, WhatsApp opens a chat with a first line that says which page you are stuck on, and Chat opens the chat window in your dashboard.

Fig. 2Sample data · example.com. An empty Logs page names its cause, one next step and three ways to ask for help. Captured from the shipped component with example.com data; illustrative, not a customer result.

Follow your setup steps from one band

Where to find it: Open a website that still has setup steps; the band sits at the top of the page

The amber band says how many setup steps are left. Adding billing, or booking your setup call while it is still to book, is the one main button; integrations, domain and tracking script follow in any order, and the band never offers the page you are on. Pages with a status band of their own, such as Overview or Domain, add your next step inside it instead of a second band.

When to use it: When you are setting up a website and want to see what is left from any of its pages.

Book your setup call from the sidebar

The full-width setup-call banner is gone. While your first-domain setup call is still to book, the sidebar shows Set up your first domain with Hassan, with a Book your setup call link, in place of the Connect your AI agent card. It stays until you book the call or dismiss it, and the setup band also lists Book your setup call as the first step.

What does this not change?

The pages look and read differently, but billing and who can change what work as before. An empty page is not a fault on its own, and Email, WhatsApp and Chat all reach the founder directly.

Read next

Where a page's status and main button sit, install your tracking script before your domain is live, or read your Logs.

Where do you find a page's status, main button and settings?

Dashboard pages now share one layout. A website's status pages open with a status band that says how things stand, each page's main button sits at the top right of its first row, lists share one toolbar with a search field, and every setting opens in one settings pop-up. Once you know one page, you know where to look on the others.

Read the status band first

Where to find it: Open a website → Overview, Usage, Domain, Tracking script, Product feed, Billing, or a request's trace in Logs

The band's colour tells you what to do. Light blue means data is arriving normally, neutral grey means it is quiet or there is no data yet, amber means there is a step for you to take, and red is kept for a failure Crisper has seen. With no data, the band is a short line instead of an empty chart, with the next step when there is one. Since 18 November, a working website with nothing yet today keeps Refresh and shows View logs on Overview, instead of a setup button. The page name now sits in the breadcrumb rather than in a title, and the main button, such as Save changes on a website's Settings, is at the top right. Since 14 November, a website's Billing page is the exception: its buttons sit under the price, with the card beside it on wider screens.

When to use it: Glance at the band when you open a page, before reading the numbers under it.

Fig. 3Sample data · example.com. A working site's status band on Overview, with the Updated button at the top right, in its earlier layout: since 18 November, View logs sits beside it. Captured from the shipped component with example.com data; illustrative, not a customer result.

Find every setting in one pop-up

Where to find it: Dashboard → Organization settings, or Manage account in the sidebar's account menu

Settings open in one pop-up for everyone, grouped as Your account, Organization (including General, Members and Key events) and Preferences (Notifications), with a Search settings field. Manage account opens it at Your account. If you leave a section with unsaved changes, it asks before discarding them.

When to use it: When you want to change your own account or your organization without hunting for the right page.

How does the shared toolbar work?

Lists use the same toolbar: a search field, labelled Search and what it searches, beside the page's filter and sort. When a search or filter matches nothing, the empty list offers Clear filters.

What does the new layout not change?

The layout changes where things are, not who can change them: the same roles can change the same settings as before. Amber is a step to take, not a fault; only red means Crisper saw something fail.

Read next

Pages keep their data as you move around, how current your numbers are, or team access and billing.

Why does a dashboard page show its data at once when you go back?

Dashboard pages now keep their data while you move between them. Go back to a website's page, or from All websites into a site and back, and it shows what it had straight away instead of loading again. Logs shows the list you last read at once and checks for newer events, with a status row above the list.

Move between pages without waiting

Where to find it: Dashboard → All websites and every page of a website

A page you leave keeps its data for 5 minutes, and signing out or switching organization clears it. Pointing at or tabbing to a link to one of a website's pages starts loading that page's dashboard data before you click. Usage keeps its statistics for each website and reads new ones only when they are more than 2 minutes old; Refresh always reads them again.

When to use it: When you check several pages of a website in a row, or compare websites one after another.

See Logs check for newer events

Where to find it: Dashboard → a website → Logs

Logs keeps the last list it read for each website and set of filters, for up to 12 of them, while the dashboard stays open in your tab. Going back shows that list at once. When it is under 2 minutes old and every day and delivery check finished, Logs shows it as it is; otherwise it checks again while you read. A status row above the list says Checking for newer events, with how many days it has checked, then Checking delivery with how many events, and ends with how many new events it found, checked just now. New rows are marked for a few seconds. If a check fails, the row keeps its message and a Try again button, and the rows you were reading stay.

When to use it: When you step away from Logs to another page and come back to the same list.

Fig. 4Sample data · example.com. The Logs status row as it checks days, then delivery, then reports what it found. Captured from the shipped component with sample values; illustrative, not a customer result.

What does a kept page not tell you?

A kept page shows what it last read, so it can miss activity from the last few minutes until its next check. Kept data lives in your browser tab only: reloading the page, signing out or switching organization starts fresh, and nobody else sees your copy. The Refresh button and Logs' own checks still read the latest data.

Read next

Read your dashboard while fresh data loads, find and re-send conversions in Logs, or how current your numbers are.

How do you compare tracking over Today, 7 days or 28 days?

Choose Today, 7 days or 28 days to read saved key-event counts, charts and delivery checks over the same period. All websites and a site's Overview remember your choice in this browser.

Where can you find it?

Where to find it: Dashboard → All websites, or open a website → Overview → period control

When to use it: Use Today to investigate a recent change, then widen the period to see whether the pattern extends across several days.

Fig. 5Sample data: All websites with per-site activity charts and the Today, 7 days and 28 days control. Cropped from the feature's original component check; illustrative, not a customer result.

How does it work?

The dashboard starts at 7 days. Selecting another period updates the event totals and delivery summaries. Today can show hourly activity in the website's timezone when those records are available; older records fall back to the daily chart.

What should you keep in mind?

A longer period cannot fill days that were never saved. Gaps stay empty or dashed and the page states how much history it has. Events without a delivery result remain not confirmed. Identity keeps its separate seven-day window.

Read next

Choose the events to watch, inspect delivery in Logs, or check events in Meta.

Which match keys were present in your events sent to Meta?

The Identity card now checks 15 customer-information keys in recorded requests sent to Meta. It shows how many keys appear on at least half of the checked key events, alongside the number of events checked.

Where can you find it?

Where to find it: Dashboard → All websites → open a website row, or website → Overview → Identity

When to use it: Use it when you want to understand which matching fields are present, including fields beyond email and phone.

Fig. 6Sample data: Identity cards show 12 of 15 and 4 of 15 keys, checked-event counts and the expanded per-key breakdown. Cropped from the feature's original component check; illustrative, not a customer result.

How does it work?

Hover or focus the Identity card to see the share for each key, grouped by priority. The seven-day sample comes from saved checks of the outgoing Meta request. Hashed values count as present. For example, 12 of 15 means twelve kinds of key met the coverage threshold; it does not mean twelve events.

What should you keep in mind?

This is field coverage in a checked sample, not Meta's Event Match Quality score, accepted-event count or ad attribution. An unchecked site keeps the earlier wording until coverage is available. Missing phone alone does not trigger the warning.

Read next

Read the event's delivery outcome, verify Meta events, or choose key events.

How do you know Meta accepted your leads and purchases?

Open the event in your website's Logs. Its trace reads Meta accepted or Meta rejected, from Meta's own reply to that event, with the status Meta returned. An event that was never sent to Meta says Not sent to Meta.

As shipped on 23 October: Open a website's Overview and read Meta's receipts. It lists Lead, Purchase and PageView, or your website's key events, with how many Meta accepted in the last 7 days, when Meta last accepted one and Meta's trace ID for that reply. Crisper reads Meta's replies every hour. Since 18 November, Overview no longer has this list and shows your latest events as Recent Logs rows instead; Meta's reply to each event is in its Logs trace. See Overview shows your latest Logs rows.

Where can you find it?

Where to find it: Dashboard → open a website → Logs → open an event. As shipped on 23 October, it was on Overview → Meta's receipts.

When to use it: Use it after a test lead or purchase, or when your Meta numbers look low, to check whether Meta received the events your site sent.

Fig. 7Sample data: Meta's receipts with Lead, Purchase and PageView rows, as Overview showed them until 18 November (earlier layout). Captured from the feature's component with example.com data; illustrative, not a customer result.

How does it work?

A Logs trace reads Meta's own reply to the event it sent: Meta accepted, or Meta rejected with the status Meta returned, so you or your developer know what to fix. As shipped on 23 October, Overview counted each accepted lead or purchase once over the last 7 × 24 hours and showed the last rejection under the list; since 18 November, that list is gone.

What should you keep in mind?

Accepted means Meta received the event. It does not tell you which ad Meta credited; that stays in Meta Ads Manager. Meta's reply shows only for events Crisper sent to Meta, so it needs Meta connected and tracking set up.

Read next

See which match keys your events carry, read an event's delivery outcome in Logs, or verify Meta events.

How do you choose the events your website watches?

Choose up to two key events for each website: Purchase, Lead, Submit Application, Sign Up or Login. This lets you monitor the actions your website is built for, instead of reading every site as a shop with purchases and leads.

Where can you find it?

Where to find it: Open a website → Settings → Key events. An organization admin can change the choices, save for this site, or copy them to the organization’s existing websites.

When to use it: For example, when applications matter more than purchases on one website. Counts beside the choices cover the last seven days; an unknown count is not zero.

Fig. 8Sample data · example.com. The key-events picker uses sample event counts.

How does it work?

The selected events shape the dashboard counts, Key events view in Logs and no-conversion alerts. New websites use your organization’s saved default, or Purchase and Lead when no default is saved. Lead and Submit Application replace one another in the picker; they cannot both be selected.

What should you keep in mind?

Selection does not install an event on your website. Changing the choices restarts alert learning, and the no-conversion alert watches their combined latest activity, not a separate silence timer for each. Save for all sites and new ones applies to existing websites and sets the default for future additions. Platform replies still do not establish ad attribution.

What should you do next?

Use the Logs guide to inspect an event, follow the verification checklist, or check custom-site event setup.

How current are the numbers on your dashboard?

Overview and All websites show how current their numbers are on the refresh button at the top right, such as Updated 3m ago, with a coloured dot. On All websites, an open website row adds its own dot when that site's numbers are late or unknown; open it to see when they were checked and when the last event arrived.

Read the age on the Updated button

Where to find it: Dashboard → All websites, or open a website → Overview → Updated … ago. A green dot means the check is current, amber means it is late, and grey means its time is unknown. Pointing at the button changes it to Refresh now; select it to request a fresh check. On All websites, open a website's row for its own dot, then hover over it or tap it for the check time and the last event. A quiet website can have a recent check even when its last event was much earlier.

When to use it: Before treating a quiet chart as a new tracking problem. On All websites, the button uses the oldest known check across eligible websites, so one late site turns its dot amber.

Fig. 9Sample data · example.com. The freshness pills as they shipped on 7 November. Since 10 November, Overview and All websites show the age on the Updated button, and an open All websites row shows its own dot when a site's check is late or unknown.

What does a current check tell you?

The age comes from the source read included in the numbers. It is separate from when the dashboard last redrew. A current check does not prove that every conversion arrived or that an ad platform accepted it; use the website's Logs to investigate a missing event.

What should you check next?

Open the conversion Logs guide, follow the event verification checklist, or check your tracking subdomain.

How are websites sorted when you choose Name?

Name order is now plain A–Z by the full website hostname in the website switcher, sidebar website list and All websites. A subdomain stays in its own alphabetical place instead of being grouped under a brand.

Find a website by the name you can see

Where to find it: Open the website switcher and choose Name, read the sidebar's website list, or open All websites and sort by Site. The initial www. is ignored; the rest of the hostname, including a subdomain, counts.

When to use it: When you manage several websites and want their position to agree across the dashboard.

Fig. 10Sample data · example.com. Name order uses the full website hostname across the switcher, sidebar and All websites. Subdomains stay in their own alphabetical place.

How does a subdomain sort?

For example, alpha.example.com comes before example.com, while start.example.com comes after it. Brand headings no longer split the switcher into groups. Newest, Oldest and Needs setup first remain available in the switcher; searching still ranks matching results.

What should you open next?

Use the All websites overview, inspect a site's Logs, or set up your team's access.

Where do tracking problems show up in Crisper?

The dashboard bell now opens a searchable inbox for everyone in your workspace. See what needs attention, follow a notification to the right website page, and separate current problems from resolved ones.

Find what needs fixing

Where to find it: Dashboard → Bell → Needs fixing

The inbox shows when a website stops sending events or conversions, a tracking domain is unverified, or automatic re-sync has paused. It also shows failed payments and tracking stopped because payment was not recovered. Each row links to the relevant page for that website.

When to use it: When you want to check which websites need attention without opening each one.

Follow updates and resolved problems

Where to find it: Dashboard → Bell → Resolved or Updates

When events or conversions start arriving again, the notification about that gap is resolved. Updates include verified domains, newly added websites, plan usage warnings, automatic plan upgrades and finished re-syncs with sent, failed and unknown counts. Search the inbox or use the filters to narrow the list.

When to use it: After fixing a problem, completing setup or running a re-sync from Logs.

Keep your own read state

Where to find it: Dashboard → Bell → Mark all read

Your read state is separate from your teammates'. Mark all read covers the notifications already in your inbox, so a new notification can still appear unread. The panel fits narrow screens, and the chat bubble hides while it is open unless you already have a conversation open.

When to use it: When several people share a workspace and each needs to keep track of what they have seen.

Read does not mean resolved

Marking a notification as read does not fix the underlying problem. Follow its link to check the website's current status. A finished re-sync can still contain failed or unknown results; its completion is not proof that every event was accepted.

How do alerts know what is normal for your website?

Conversion alerts now adjust their wait to how often your website receives purchases or leads. Quieter websites get more time between conversions, and the window you choose remains the minimum.

How to set the minimum wait for a conversion alert

Where to find it: Dashboard → Organization settings → Notifications → Website alert rules

In a website's row, or the All websites row, set the No purchases or leads column to At least and the number of hours you want. Crisper can wait longer for a quieter website, up to 72 hours. If you choose a minimum longer than 72 hours, that longer minimum applies. The No tracked events alert keeps its existing rules.

When to use it: When you want to choose the shortest gap without purchases or leads that should prompt an alert.

Fig. 11Sample data. In the Website alert rules table, At least sets the minimum for purchases or leads; the actual wait can be longer for a quieter website.

How does Crisper choose how long to wait?

Crisper uses the conversion rate over the seven days ending at your website's last conversion. That baseline needs at least three conversions and complete data for the period. A quieter rate means a longer wait, within the 72-hour limit or your minimum if it is longer. Without a usable baseline, Crisper does not open a new conversion alert.

A quiet spell is a reason to check

A conversion alert means Crisper has seen a gap in purchases or leads. It does not prove that tracking is broken or explain why conversions stopped. Open the website's Logs to investigate.

Read next

What does the daily tracking check email tell you?

Website alerts used to send an email for every quiet hour, and one email per website when several went quiet at once. Now Crisper collects them into one Daily tracking check email for your workspace. It lists only the websites that are still quiet when the email goes out, so your inbox shows what needs a look today.

How the Daily tracking check email works

Where to find it: Your inbox, once a day at 13:00 UTC

Each email lists every website that is still quiet, with what stopped: no tracked events, or no purchases or leads, and since when. Each website name opens its Logs. Gaps that recover before the email goes out drop off the list, so you only see the ones still open. You get at most one of these a day, and only after a new gap.

When to use it: When you manage several websites and want one daily list of the ones that went quiet, instead of an email per gap.

Fig. 12Sample data. Each website name opens that website's Logs. This is the email's earlier layout; since 18 November it uses the shorter layout described in Crisper's emails are shorter.

Which alerts still arrive straight away?

If your workspace monitors one website, a gap in purchases or leads still sends its own email as soon as it is confirmed. Gaps in tracked events, and every gap in a workspace with two or more websites, go into the daily email. The bell in your dashboard still shows every alert the moment it happens, whichever email it goes into.

How to change or turn off website alerts

The daily email follows your website alert settings. Change how long Crisper waits before a website counts as quiet, or turn an alert off, for one website or all of them.

  1. Open your dashboard and go to Organization settings → Notifications.
  2. In the Website alert rules table, use a website's switches to turn No tracked events or No purchases or leads on or off, and set how many hours to wait.
  3. To change every website at once, edit the All websites row. The next Daily tracking check uses the new settings.

A quiet website is a reason to check, not proof of a fault

The email describes the events Crisper received. Fewer visitors or a slow sales day can cause a quiet spell, and the email does not check what ad platforms accepted. Since 5 November, a website counts as having no tracked events after 24 quiet hours by default, not one.

Read next

How do you set alerts for every website at once?

If you manage many websites, setting alert rules one long block at a time was slow. The Notifications page now shows every website's alert rules in one table, with an All websites row for changes you want everywhere.

How to see every website's alert rules at once

Where to find it: Dashboard → Organization settings → Notifications

Each website has one row with three columns: No tracked events (a switch and how many hours to wait), No purchases or leads (a switch and the shortest wait) and Quiet-hour protection. Open the info button on a column heading for what that rule does; it opens with a tap on phones too. Search by website address, and step through them 25 at a time. On a phone, each row stacks so nothing scrolls sideways.

When to use it: When you want to check or change which websites alert you, and after how long.

Fig. 13Sample data. One row per website, with No tracked events, No purchases or leads and Quiet-hour protection; search by address and step through 25 at a time.

How to change a rule for all your websites

Where to find it: Dashboard → Organization settings → Notifications → All websites row

The All websites row shows a value when every website shares it and Mixed when they differ. Change one setting there and it applies to every active website in the organization. Only the setting you changed is updated; each website keeps its other rules. You can then change any single website in its own row.

When to use it: When you want the same rule on every website, then a different rule on one or two.

Fig. 14Sample data. The All websites row shows Mixed where websites differ; a change there updates only that setting on every active website.

All websites changes every website, even while you search

A search narrows the list you see, not the All websites row: a change there still applies to every active website, and the row says so. New websites you add later start with the default rules, not the values you set from All websites.

Read next

How do you check every website in one place?

When you open the dashboard you now land on All websites. It shows how many sites need attention, lists the newest conversion first, and checks each purchase or lead to confirm it reached every integration on that site, so you see a missed conversion the same day.

All websites

Where to find it: Dashboard → All websites (the page you land on)

Each website has one row: tracking status, today’s purchases or leads, bars for the last 14 days and the time of its last conversion. The site with the newest conversion sits on top. The count at the top says how many sites need attention, and the side panel shows your totals and latest conversions. Click a row to see the reason, the key figures and the next fix.

When to use it: Start here each day: see which website needs a look, then open it.

A delivery check on every conversion

Where to find it: Dashboard → All websites → a website’s row and the side panel’s totals

Each purchase or lead is checked to confirm it reached every integration on its website. A row can say “3 of 4 reached every integration” or name the integration that missed it. New conversions are checked within about half an hour; a missed send is checked again over the following hours before it counts as missed.

When to use it: When a number looks low, check whether the conversion arrived but didn’t reach Meta, Google Ads or GA4.

What the delivery check tells you

It confirms each conversion reached your integrations. How an ad platform then attributes that conversion is its own decision, so use its reports for attribution.

How do you see AI agents and ad blockers in your visitor data?

On sites that send GA4 through Crisper, Overview and Logs can count AI agents, and Logs can show whether a visitor had an ad blocker on.

Overview splits the last 7 days of your leads or purchases into people, bots and AI agents. In Logs, a request's trace says who sent it and, when the request carried the signal, that an ad blocker was on.

Where can you find it?

Where to find it: Dashboard → open a website → Overview → Who sent these leads (or Who made these purchases), and Dashboard → open a website → Logs → open a request → Visitor checked

When to use it: Use it when your lead or purchase numbers look higher than your sales, to see how many came from bots or AI agents, or to see whether a test visit had an ad blocker on.

Fig. 15Sample data: an Overview visitor breakdown and a Logs trace for example.com. Captured from the feature's components with example.com data; illustrative, not a customer result.

How does it work?

Each request is checked on the way for bot signals and for detected AI-driven traffic, and GA4 carries the result with the event. Overview counts each lead or purchase once as a person, a bot or an AI agent, and lists any it could not judge as Not judged. The AI agents row reads not reported yet until a GA4 request for your site has carried the AI flag. In a trace, the Visitor checked step reads Person, Bot, AI agent, Scanner or Not judged, and adds Ad blocker on when the request carried that signal.

What should you keep in mind?

No AI flag means unknown, not proof of a human: not every AI agent is detected. Ad blocker off means none was detected, not that nothing was blocked. Both need GA4 sent through Crisper, so a site whose conversions reach only Meta keeps the AI agents row greyed out. The Overview breakdown is not shown on a site with its own key events selected. Labels are signals: bot and AI agent conversions stay in your totals and still reach your ad platforms.

Read next

See which leads and purchases came from bots, the GA4 fields Crisper sends, or read an event's delivery outcome in Logs.

Can you read the dashboard while fresh data loads?

Opening the dashboard shouldn't mean waiting for every new lookup before you can read it. Overview and All websites start with saved figures when available, and Logs can show recent purchases and leads while it loads the latest list.

Start with the figures already available

Where to find it: Dashboard → All websites and a website's Overview

Saved figures can appear as the page opens, then update as fresh data arrives. While Overview is loading, metric names and section labels stay visible so you can see what each number will describe.

When to use it: Check recent activity when you first open the dashboard.

See how old the site figures are

Where to find it: Dashboard → All websites → Updated … ago

The refresh button says how old the numbers are, such as Updated 7m ago, and reflects the oldest site's figures. Select it, shown as Refresh now when you point at it, to request a fresh check.

When to use it: Check the age of the numbers before deciding to refresh them.

Read recent conversions while Logs loads

Where to find it: Dashboard → a website → Logs

Logs opens on the last seven days, including today. Saved rows appear when available while the latest list loads, filtered by the event, status, client and URL you chose, then are replaced by that list. Automatic delivery checks cover the newest 50 rows; open an older event to check its delivery.

Since 12 November, going back to Logs in the same session shows the list you last read for that website and filters at once, with its delivery results. If that read is under 2 minutes old and finished in full, Logs shows it without checking again; otherwise it checks for newer events while you read. See pages keep their data as you move around.

When to use it: Look over recent purchases and leads without starting from an empty list.

Saved rows are a starting point

The first figures and rows may be from an earlier update, so they can miss newer activity. Saved rows cover the events Crisper keeps a copy of, such as purchases, leads and your key events, so some views have no saved rows and wait for their own results. A row appearing is not confirmation that an ad platform received or attributed it.

What else changed in the dashboard?

Website alerts wait 24 hours by default

No tracked events now waits 24 hours by default, not 1. Quiet-hour protection needs 12 events in an hour, up from 6. Websites with rules you saved keep them.

Browser tabs name the website and show unread alerts

Dashboard tabs now show the website's domain on site pages and your workspace name elsewhere, so two tabs are easy to tell apart. Unread alerts show as a count at the start, such as (2).

Find sites in the same order

The sidebar lists every site in the same A–Z name order as the site switcher, with no Show more. As shipped on 1 November: The sidebar now lists your sites in the same name order as the site switcher, including when you choose Show more. Since 14 November, Show more is gone and the sidebar lists every site.

Keep the dashboard background consistent while scrolling

On wider screens, the background revealed by overscrolling matches the dashboard's dark outer gutter.

See leads and purchases on the same website

All websites shows both types when a site sends both. Today's totals and the switch from today to yesterday follow each website's timezone.

Open a recent conversion directly in Logs

Recent conversions on All websites show the visitor's email or phone when available. Select a conversion to open that request in Logs.

Recognize long domains in the sidebar

Long domains keep their beginning when shortened in the sidebar and website picker, making them easier to tell apart.

A dark sidebar with menus beside it

The dashboard sidebar stays dark in every dashboard theme, tinted to suit it. On desktop, its menus open beside the sidebar so they leave your navigation visible. As shipped on 29 October: The dashboard sidebar stays dark in either page theme. On desktop, its menus open beside the sidebar so they leave your navigation visible. Since 15 November, it stays dark in every dashboard theme.

Website alerts are on by default

Every website starts with both alerts on: No tracked events after 24 hours with no events, and No purchases or leads after at least 24 hours without one, longer for a quieter website. Quiet-hour protection is on at 12+ events an hour, so hours that are normally quiet don't raise an alert. Open alerts go into the Daily tracking check email at 13:00 UTC; when a workspace monitors only one website, a gap in purchases or leads is emailed straight away. Change the timing or turn alerts off in the Website alert rules table under Notifications.

As shipped on 28 October: Every website emails you when a normally busy hour goes silent, or when no purchases or leads arrive for 24 hours. Change the timing or turn them off in Notifications. Since 4 November, alerts arrive in one Daily tracking check email, and since 5 November, No tracked events waits 24 hours by default.

Counts no longer stop at 100

Overview and All websites now count every purchase and lead from the last 7 days on busy sites, and update about every 15 minutes.

A shorter Add website form

Add website puts the URL first, suggests timezone and currency, starts with Meta restriction on, keeps settings behind Change, and shows creation errors under the URL field.

Compare each site's conversions with Meta's receipts

The Sites page gained a Delivery column for sites with Meta connected and delivery data available, comparing purchases or leads over the last six full days, with today left out.

Since 28 October, All websites replaced that page and shows how many of each site's conversions were delivered. For Meta's own reply to a lead or purchase, open the event in Logs; see how you know Meta accepted your leads and purchases.

Follow the next step when adding a website

Add Website opens billing first, then guides you through each setup step: Domain, Integration, Scripts and First event. While you set up your first domain, a Setup call step comes before Domain.

As shipped on 9 October: Add Website opens billing first, then guides you through integrations, domain verification and the tracking script. Since 21 October, setting up your first domain can also include a setup-call step.

Use the dashboard more comfortably on a phone

As shipped on 9 October: Sites and DNS records use stacked layouts on phones, dialog buttons fit narrow screens, and account settings open as a page. Since 12 November, Manage account opens Your account in the settings pop-up.

Move around the dashboard with keyboard shortcuts

Press Command K on Mac or Ctrl K elsewhere to find websites, pages and integrations; the sidebar now keeps each website's monitoring, setup and account pages together.

Explore the dashboard before adding a website

Finish later is now available before you create your first website, and your choice is remembered in that browser.

Use consistent rounded controls

Buttons, inputs, search fields, dropdowns and toggles are now pill-shaped across the dashboard and crisper.io. Icon-only buttons are circles, and text areas have softer rounded corners. Cards, panels, table rows and checkboxes keep their own shape, and a button still saves the same thing with the same permissions. Some specialized controls keep their own layout.

Move between pages with smoother transitions

On crisper.io's public pages, navigation uses short crossfades where the browser supports them. Opening a blog card carries its image into the post's cover, and opening a case study or tool card carries its title into the page heading. Since 15 November, dashboard pages only fade in briefly, and a loading placeholder gives way to the page in place; see Dashboard pages open on the click. If your device is set to reduce motion, these animations are turned off. A transition is not a completed data check, and other browsers navigate as before.

Each domain break gets its own Needs fixing notice

When a tracking domain that was fixed breaks again, the bell's Needs fixing list now gets a new notice for that break, and the notice moves to Resolved once the domain works again. Before, a second break showed nothing new. While a domain stays broken it keeps one notice, not one per check. Crisper sees a working domain break when the domain is checked again, for example from its Domain page, during setup or with your AI tool's DNS check. The emails and the notice wording are unchanged.

Loading screens match their pages

Each dashboard page now loads in its own layout, so its content fills in where its placeholder was. Pages such as Logs and a log trace no longer flash back to a loading screen after they appear, and while Logs checks delivery it says Checking delivery… instead of a count of zero delivered. Usage shows placeholders, not Unknown, while its numbers load; a number that really is unknown still says so.

The sidebar lists every website

The sidebar's website list now shows all your websites in A–Z order, the same order as the website switcher, with no Show more. A long list scrolls while your account menu stays at the bottom.

Organization billing and settings stay in the sidebar

Inside a website, the sidebar now keeps Organization billing and Organization settings after the website's own pages, so you no longer go back to All websites to reach them. Members who can't see billing still get no billing row. On organization pages, such as All websites, the sidebar drops Jump to website: the A–Z website list and search already reach every site. Inside a website, the switcher still names the website and switches to another.

Organization Billing now shows its Add website button at the top of the page even when you have no websites yet, as well as in the empty page itself.

Tracking script and Usage show your saved copy at once

A website's Tracking script page now shows the script it last generated in your browser straight away, instead of generating it again on every visit. It generates a new one on your first visit in a browser, after your tracking domain changes, when the saved copy is more than 7 days old, or when you ask it to. Switching platform keeps the script on screen. On Usage, your last saved figures from the current billing period show at once with Updating… on the refresh button, and the fresh read replaces them in place.

Dashboard pop-ups share one look

Pop-ups across the dashboard, from billing and integrations to invitations and confirmations, now share one header with the title and a line of context. The body scrolls while the footer stays in view, with the main action last, and when the buttons don't fit on one line they wrap instead of being cut off. Billing pop-ups show what you pay as one large figure, Due today or Next charge. On phones, a pop-up opens as a sheet from the bottom with full-width buttons, and you can swipe its handle or header down to close it; on wider screens it grows from the button that opened it. What each pop-up does is unchanged.

Dashboard pages open on the click

Dashboard pages no longer wait for an animation before they appear. A page the browser has already loaded in the background switches as soon as you click or tap its link, and its data starts loading while it fades in. While a page loads, its placeholder gives way to the page in place instead of fading out. Pages not loaded yet still wait for their response before they switch.

On a phone, the menu's pages now load in the background once the page you are on is idle, as the sidebar's links already did on wider screens, so they are ready when you open the menu. The new page still fades in briefly; if your device is set to reduce motion, the fade is off.

Busy websites show a full week on Overview

A website's 7-day numbers on Overview now build in full for busier websites, whose week could come back incomplete before. When Crisper could read only part of a period, the count shows as a minimum with a plus, such as 230+, and the delivery note reads Of at least 230 received. A complete week shows its exact count.

The site health your AI assistant reads from Crisper now compares today's leads or purchases with the same hours on earlier days. A busy website no longer reads warning every morning just because the day has only started.

Busy websites don't flag hours they are usually quiet in

The site health your AI assistant reads from Crisper, and the status in the Daily site digest email, now also look at the stretch since a website's last lead or purchase. It counts how many the website usually gets between the same clock times on earlier days, and treats the quiet stretch as a silence only when those days usually had leads or purchases in it. A website that is busy by day but quiet at night no longer reads warning overnight just because nothing came in during hours that are usually empty.

This only makes the check more forgiving. A quiet stretch still has to be longer than the website's usual gap across the whole day before it counts, and a day that is behind its usual pace can still read warning. It applies once Crisper has read the full week and has earlier days with leads or purchases to compare. Website alerts and the Daily tracking check email keep their own rules.

Overview shows your latest Logs rows and your site's own day

A website's Overview now ends with Recent: its latest events in the same rows as Logs, each opening that event in Logs, with a Logs link for the rest. Recent replaces the Meta replies list that sat at the bottom of Overview. Meta's reply to each event is still there to read, in that event's trace in Logs, which says Meta accepted or Meta rejected; see how you know Meta accepted your leads and purchases.

A working website's status band now offers View logs beside Refresh, and keeps its main button for a real problem or a setup step. Today starts at midnight in the website's timezone. When your own clock differs, the Key events card on Today says when that was in both, such as Since 00:00 GMT+0 · 05:00 your time; the same card shows on All websites, where recent leads and purchases now list their times in each website's timezone. Just after the website's midnight, the map of recent key events says None today yet · showing last 7 days instead of going blank.

Settings says when a site's timezone needs a look

Under Timezone in a website's Settings, a line now says when the timezone needs your check. Not chosen yet means the website's days are counted in GMT+0 until you choose its timezone and save. Set by Crisper means Crisper chose it from where the website's visitors and address are; check it and select Save changes to confirm it, even without changing it. The line goes away once you pick a different timezone.

Crisper's emails are shorter, with one clean layout

Website alerts, the Daily tracking check, the Daily site digest and the setup emails now share one layout: the Crisper logo, a bold headline, a few short lines, a grey box for details such as the website and the time it was checked when an email has them, and one main button. In email apps that follow your device's dark mode, they switch to a dark version.

The subjects, who gets each email and when it is sent are unchanged, and so is what each alert checks. Lists in the digest and the Daily tracking check still link each website to its page.

What should you do when an alert arrives?

Treat an alert as a reason to look, not a verdict. Fewer visitors or a slow sales day can cause the same quiet spell, so check the website before you change anything.

  1. Follow the notification or the website name in the email to the website's page, and read the reason shown there.
  2. Open the website's Logs, newest first, and look for the latest purchase or lead. A conversion that arrived but did not reach an integration shows in the delivery check.
  3. If the alert names an unverified tracking domain, finish domain verification. If automatic re-sync has paused, follow the link from the bell.
  4. After a fix, watch the bell: when events or conversions arrive again, the notification moves to Resolved.

To confirm what Meta then received, use the Events Manager checklist.

How do you set key events for new or selected websites?

Organization admins can set the key events new websites start with and update selected existing websites from one table. Websites with different goals can keep their own choices.

Where can you find it?

Where to find it: Dashboard → Organization settings → Key events. Pick up to two events and tick the websites to update. When to use it: Give similar websites the same starting choice; members can read the table.

Fig. 16Sample data · example.com. New websites and selected existing websites in the Key events table.

How does it work, and what are its limits?

Keep New websites ticked to save the default. Untick all existing websites to change only that default; otherwise read the count on Update websites before saving. Without a saved default, new websites start with Purchase and Lead.

Changing the default alone leaves existing websites untouched. Choices do not install events, and existing-site changes restart alert learning. In a one-website organization, saving that site’s choices also sets the default.

Choose key events, inspect them in Logs, or manage them through your AI tool with preview and confirmation.

What changed in this guide

  • 19 November 2026: Added Recent Logs rows on Overview, timezone lines in Settings, organization rows in the sidebar and shorter emails to What else changed in the dashboard, and the top bar's theme picker to the theme section. Updated how to read Meta's reply, now in each event's Logs trace, and noted the earlier layouts of the status band and Daily tracking check screenshots.
  • 17 November 2026: Added how busy websites no longer flag hours they are usually quiet in to What else changed in the dashboard.
  • 16 November 2026: Added how to choose a dashboard theme and accent. Added dashboard pages that open on the click and full weeks for busy websites to What else changed in the dashboard. Updated the dark sidebar and page transition notes, and what new accounts see on All websites.
  • 15 November 2026: Added what empty dashboard pages tell you to do, with the shared setup band and the setup-call tile. Added domain break notices, matching loading screens, the full sidebar website list, saved Tracking script and Usage copies, and the shared pop-up look to What else changed in the dashboard. Updated Find sites in the same order now that Show more is gone, and noted that Billing keeps its buttons under the price.
  • 13 November 2026: Added the shared page layout with its status band and settings pop-up, and how pages keep their data as you move around, including the Logs status row. Updated dashboard freshness, Logs while loading and the phone notes to how the product works today.
  • 12 November 2026: Moved AI agents and ad blockers in your visitor data into its own section, with where to find it, how it works and what it does not mean.
  • 12 November 2026: Added how to read Meta's own reply to your leads and purchases on a website's Overview.
  • 12 November 2026: Added rounded controls and smoother page transitions to What else changed in the dashboard. Updated sections to how the product works today and corrected details that were wrong when they shipped. Retook the Website alert rules screenshot.
  • 11 November 2026: Added shared dashboard periods, missing-history limits and the Meta match-key breakdown.
  • 10 November 2026: Added the new-website key-event default and selected-website updates. Updated how site-level saves affect that default.
  • 9 November 2026: Added key-event choices, their Logs view and alert-learning limits.
  • 8 November 2026: Added sections on dashboard data freshness and consistent A–Z website lists.

Sources

2 sources
  1. 1how it tracks website conversions↩
  2. 2confirm you're collecting data↩