Your traffic is up, but sign-ups aren’t, and you’d like to know where people lose interest. These are the questions a product or growth team asks every week — where people drop, which source converts, which pages hold attention, whether a number is broad use or a few heavy users. Crunch answers them from your site’s or app’s events: the record of each thing a visitor did, like viewing a page or signing up. You ask in plain words; there are no reports to build first.
What you’ll need
- Your events, sent by the BumbleB tag in Google Tag Manager — or, on a Shopify store, the BumbleB pixel.
- A verified domain, so your site’s events are accepted.
- Optionally, the business side — revenue, CRM or ad spend — as uploads, so you can ask across both.
Step by step
- Add the tag. Follow Google Tag Manager.
- Send the events that matter to you — sign-ups, key feature use, errors — not only page views. Crunch can only answer about what you send, so a step you never track is a step it can’t see.
- Hash user IDs if you identify users. Hash them in the page before anything is sent — see Hashing user IDs. That way you can follow people across visits without sending who they are.
- Add the business side when you need it. See Which route for which data.
- Pick your events dataset in the datasets pill, tell Crunch what it can’t see (below), and ask.
Tell Crunch what it can’t see
Event names are short, and their meaning lives in your team’s heads. Say once, at the start:
- Which event means what — “activation is a first project created”, “scroll_75 means the page was read all the way down”.
- Who counts as active — a visit, a session, a signed-in user. Each gives a different number, and none of them is wrong.
- Internal traffic — “ignore visits from our office domain”, so your own team doesn’t inflate the figures.
How to tell it worked
On the connector card in the hub, the status shows Active once your domain is verified, and each API key’s Last used date moves as events arrive. In the chat, ask something simple first — “how many visits did we get yesterday?” — and check the figure against what you’d expect.
An example
A listings site wants to know which of its pages actually earn their traffic.
| You ask | Crunch finds |
|---|---|
| Which of our pages actually hold attention, and which just get a glance? Rank them by how often their visits get read all the way down. | Pricing 70% (5,600 of 8,000 visits), the neighborhood guide 45% (2,700 of 6,000), the blog post 20% (1,200 of 6,000). Pricing holds attention; the blog post mostly gets a glance. |
The neighborhood guide and the blog post drew the same 6,000 visits, but the guide kept more than twice as many readers to the end. Raw traffic alone would have ranked them equal.
Good to know
- Crunch reads the events you send. If a step isn’t tracked, it says so instead of guessing.
- Events start on the day the tag goes live. There is no history before it.
- Say the definition once. “Read all the way down” or “active” can each be counted several ways. Telling Crunch which one you mean at the start keeps every later answer on the same footing.
Related
- Google Tag Manager — set up the events.
- See which ad spend comes back — put ad spend next to your events.
- Solve a problem in a conversation — one small question at a time.