Data quality

Your ad platforms learn from every event they receive. When bots, your own team or test orders reach them, they learn the wrong lessons and your results suffer. Data quality shows you what Zappush keeps out, and what still needs your attention.

Where to find it

Open Connections → Data quality. Pick a period at the top; every number on the page follows it, counted in your store's own time zone. With Compare on, each number shows its change against the period before.

The page has four tabs: Overview, Bots, Internal traffic and Consent.

Overview

Three cards, one per tab, each with one sentence on what matters most right now and three numbers. Open a card to go to its tab.

Bots

Search engines, AI crawlers, link previews, uptime monitors and scripts visit your store every day. Zappush recognizes them and holds them back from your ad platforms, so they never train your ads.

At the top:

• Bot events: events that came from bots.
• Share of traffic: the part of all your events that came from bots.
• Fake purchases: purchases a bot triggered, for example by loading your order confirmation page.
• Fake purchase value: what those purchases would have added to your sales.
• Bot profiles: shopper profiles that bots created. They stay out of Shoppers, audiences and email lists.
• Possible bots: visits from anonymous browsers or rented servers. Some real shoppers use these, so they are counted apart and still sent unless you choose to hold them back.

Below, Who's visiting lists every bot by company or by name, with how Zappush knows it is a bot. A crawler that pretends to be another, such as a fake Googlebot, is listed apart. Open a bot to see its pages, its recent events and where it came from.

When a bot places a real order, a warning at the top names the order so you can check it before you ship anything. Zappush also emails you when it happens; you can turn that off in Settings → Bot traffic.

Allowing a bot

Some bots work for you, such as a partner's price checker. Open the bot and choose Allow this bot. Its visits are then treated like a shopper's and reach your ad platforms. Choose Hold back again to undo it. A crawler pretending to be another bot can never be allowed.

Internal traffic

Your team browses the store, tests the checkout and places test orders. Add them to Your list and their events are kept out of your ad platforms. Your reports still count their visits.

• Your list: add an email for one person, or a domain such as yourstore.com for everyone with an email there.
• Looks like your team: emails Zappush thinks belong to your team, from test orders, 100% discount orders and the people on your account. Add them in one click, or dismiss the ones that are not yours.
• Test orders: orders marked as tests, and orders a 100% discount brought to zero. Each shows whether it reached your ad platforms. If one did, a warning offers to add the email that placed it.
• Office networks: the networks your team uses. Add one and visits from it are kept out too, even before anyone signs in.

Under the numbers, each connected ad platform shows whether it keeps your team out. Some keep the conversion and leave out your team's details instead.

On a store in privacy mode, Zappush keeps no list of your team, so this tab shows your test orders only.

Consent

If you collect cookie consent through Zappush, this tab shows how shoppers answered your banner:

• Accepted: shoppers who accepted.
• Declined: shoppers who declined. Their events are not sent to your ad platforms.
• No answer: shoppers with no choice recorded.

By country shows the same answers for each country your visitors came from.

If your store does not collect consent through Zappush, the tab explains how to start in Settings → Consent.