Cookiebees

The platform

Measure, follow up, and prove it - built in.

Nine modules on one identity. Each one below has its own page, its own drawn scenes, and a proof you can open. No web developer to capture cookies, no CRM developer to map them, no Zapier to forward payloads.

No developer required

Measurement that sets itself up.

The painful part of conversion tracking isn’t the strategy - it’s the plumbing. We removed it. No web developer, no CRM developer, no Zapier in the middle.

  • No hidden form fields to capture cookies - every cookie and click-id is captured automatically.
  • No mapping hidden fields to contact fields - attribution persists with the lead out of the box.
  • No Zapier or Cloud Functions to build and parse payloads - we post to Meta CAPI, GA4 and Google Ads natively.
Settings · connect your accounts

Meta pixel

Conversions API

Connect

Lead Ads

instant forms

Connect

Ad spend

measured ROAS

Connect

Catalog

product carousels

Connect

WhatsApp

shared inbox

Connect

Google Ads

Data Manager API

Connect
Tokens are exchanged server-side. Nothing is ever pasted by hand.

First-party attribution

Every cookie, kept and connected.

We track the cookies and click-ids from every major platform as first-party data on the lead - the foundation for CAPI offline conversions and backend funnel events that survive iOS, ad-blockers and cookie loss.

  • Google, Meta, GA4, TikTok & Snapchat cookies + click-ids
  • Powers offline conversions & backend funnel events
  • Optional server-side GTM client when you want full control
  • WhatsApp leads from website chat - attributed, never anonymous
Signal delivery

Third-party pixel

blocked

cdn.some-tracker.com/px.js

ITP · blocker

First-party path · your own domain

arrives

yourstore.com/a7f2k/collect

Attribution coverage

0%

of orders tied to a real source on live stores

The identity lives on the visitor, not the browser - so it survives the wipe.

Attribution reports

See which click actually made the sale.

Attribution lives in the CRM, next to the revenue - not in a separate analytics tool you have to reconcile. Connect Meta Ads Manager and pull spend straight in.

  • Reports by click-id, UTM, referrer and cookie
  • Campaign → ad-set → ad revenue tree
  • Connect Meta Ads Manager - pull spend, clicks & impressions
  • Spend vs revenue and blended ROAS, in one place
Order #4821 · path to purchase

10d 5h first touch → purchase

₹4,860

Viewed product→Added to cart→Checkout→Purchased

Session 1 · Google AdsTRACKED CLICK

landed on a product page

day 1 · 08:03

Session 2 · Direct

came back, added to cart

day 6 · 21:14

Session 3 · EmailCONVERTED

checkout, purchased

day 10 · 13:41
Purchase sent to Meta & Google · order.4821 · deduplicated

WhatsApp, built in

A full WhatsApp suite - templates, broadcasts and bots.

Run all of WhatsApp from the CRM. Design message templates here and publish them to Meta, broadcast to a whole segment, and build a visual chat bot that follows up on its own - no Business Manager juggling, no second tool.

  • Create WhatsApp templates in the CRM and publish to Meta - text, image, video, document & carousel headers
  • Broadcast an approved template to a segment - throttled, opt-out aware, with a per-recipient delivery report
  • A visual, stateful flow builder: menus, ask-and-save, media, timed waits and hand-off to a human
  • Send images, PDFs & video free inside the 24-hour window - no template approval needed
  • Two-way inbox, plus email templates & nurture from your own domain on the same triggers
Signals · engagementserver-side

You sent

Email campaign
WhatsApp template
what they did with it

Opened the email

→

EmailOpened

email

Clicked a link inside it

→

EmailLinkClicked

email

Replied on WhatsApp

→

WhatsAppReplied

business_messaging

Tapped a tracked link

→

LinkClicked

website

Four more reasons for Meta to keep this person in your audience - and four more things its bidding now knows about who actually engages.

Real actions only. No value is ever attached - engagement is not revenue, and a faked page view would corrupt both.

Run the pipeline

From form to close, organized.

Capture each segment with its own form, route it to the right pipeline, and see everything you ever collected about a lead in one explorer - with scheduling and calendar built in.

  • Multiple forms per segment, each mapped to its own pipeline
  • Workflows & automations on every meaningful event
  • Lead Explorer - every lead and all the data we capture
  • Scheduling with Google Meet & Zoom, added to the calendar
Pipelinesource travels with the card
New

₹42,000

Meta

₹18,500

Google

₹64,000

Referral
Qualified
Won
Every stage change is a signal you can send back - so the ad platform learns which leads were actually worth having.

Your data, your way

Our managed database - or your Firestore.

Run on our managed, isolated database with row-level security, or connect your own Firestore if you’d rather own the storage. Either way, the measurement loop works the same.

  • Managed Postgres with per-workspace row-level isolation
  • Or bring your own Firestore
  • Your own integration credentials, your own sending domain
  • Export your data anytime
Event stream · purchase payload

What came in

email

the shopper typed it

phone

from checkout

address

city, zip, country

click id

captured on landing

→

What we sent

em

a1f4…9c02

ph

7be1…44d8

ct / zp / country

3d90…b7e1

fbc / gclid

passed through raw

external_id

stable per customer

Match quality

0/10

Nothing leaves as plain text. Every identifier is SHA-256 hashed first.

The platform, by vertical

Everything inside, grouped by the job it does.

Tracking, attribution, signals, commerce and connections - each vertical below is a set of features that ship together and feed the same loop.

Track · Ecommerce + Lead gen

First-party tracking that survives

Safari caps, ad blockers and URL-stripping browsers eat third-party tracking. Cookiebees serves tracking from your own domain and keeps every signal alive on the visitor, not the browser.

  • A tracking path on your own domain - no CNAME for Safari to detect, nothing for blocker lists to carry
  • Parameter aliases: click ids arrive under names no browser strips, and Google fills them via tracking templates
  • Owned domains + cross-domain identity - one visitor id across every site you run
  • The first-party cookie store rebuilds identity after ITP wipes it
  • Journey coverage on live stores: 97% of orders carry their full story
tracking · your own domain
yourstore.com/a1b2c3no CNAME · no DNS record
utm_source → mm_sgclid → mm_gcfbclid → captured
Orders we can see the journey for97%

Measure · Ecommerce + Lead gen

Attribution that names the ad

Every order carries its journey - first touch, every session, the converting click - and every report ends in a verdict, not a chart.

  • Per-order journey: sessions, click ids and pages from first visit to purchase
  • Funnel by channel with the biggest leak named, priced, and assigned to a team
  • Action report: every campaign judged - cut, fix, scale or watch - on measured ad spend
  • Analytics & insights: retention by channel, time-to-buy, product performance, trends
  • Our number next to Ads Manager’s, with the attribution-window difference explained honestly
attribution · last 30 days
first touch · Meta→day 4 · Email→converting click · Google
Google Ads
₹12.8L
Meta Ads
₹7.3L
Email
₹3.1L
Organic
₹1.9L

Biggest leak: view → cart on Meta · fixing 5% ≈ ₹64,000/mo

Send back · Ecommerce + Lead gen

Signals the ad platforms can bid on

The loop closes server-side: every conversion goes back to the platform that earned it, enriched with everything the identity graph knows.

  • Meta Conversions API with graph enrichment - purchases regularly match at 8–10
  • Google Ads Data Manager: direct uploads with enhanced conversions and basket data
  • Server GTM destination: one rich event, fanned out to any tag you run
  • The Event stream console: shadow mode, per-event payload inspector, dedup on your order id
  • Health & wellness redaction strips sensitive URLs and product names before anything leaves
event stream · what left the building
Shadow modecaptured, not sent - until you flip it
PurchaseMeta₹4,8609.0
PurchaseGoogle Ads₹4,860sent
AddToCartMeta-4.5

em ✓ · ph ✓ · address ✓ · click id ✓ · dedup: order.7390…

Sell & recover · Ecommerce

Shopify commerce, measured and recovered

Orders, customers and the money you almost lost - one workbench, honest about currencies and match quality.

  • Orders workbench: search the whole history, match quality per order, and exactly what we sent for it
  • Recovery playbooks: abandoned checkout, cross-sell, replenishment - recovered revenue attributed back
  • Exit-intent popups and segments with live counts
  • Customer records with clean E.164 phones and full addresses, match-ready
  • Ad spend in the ad account’s currency, revenue in the store’s - never silently mixed
order · what we sent
Order #7390470111423 · ₹3,240match 9/10

Arrived with the order

emailgoogle click

Left for the ad platforms

emailphonenamecitypostcodeclick idstable id

5 signals added from this customer’s history.

Connect · Ecommerce + Lead gen

One click to connect, nothing to paste

A verified Meta Tech Provider app and a verified Google platform - so connecting is a popup, not a credentials scavenger hunt.

  • Connect WhatsApp, Lead Ads, Ad Spend, Pixel and Catalog - one click each, zero tokens
  • WhatsApp suite: shared inbox, broadcasts, flow builder, rich templates
  • Instant-form leads land in the right workspace, routed per form
  • Google sign-in for conversions with the Data Manager scope only - no over-asking
settings · connections
WhatsApp Connected
Lead Ads Connected
Ad Spend Connected
Pixel · Conversions API Connected
Product CatalogConnect

No tokens. No developer accounts. A popup each.

And everything else

The full capability list.

Each is a tool you’d otherwise buy separately - shipped together and feeding the same loop.

Automatic cookie capture

Google, Meta, GA4, TikTok & Snapchat cookies + click-ids captured first-party - no hidden form fields, no web developer.

Meta Conversions API

Server-side Lead, QualifiedLead & Purchase events - hashed PII, event-ID dedup, real deal value on close.

GA4 Measurement Protocol

Client + session id stitched from the lead’s own cookies, lifecycle events pushed native - multi-stream aware.

No Zapier, no Cloud Functions

We build and post the payloads to Meta, GA4 and Google Ads natively - no external webhook to parse and forward.

Server-side GTM client

Use our managed sGTM client to post data, or plug in your own when you want full control.

WhatsApp inbox

Two-way chat from the CRM, template sends, 24-hour-window awareness, delivery state - every message tied to the lead.

WhatsApp template builder

Build templates - text, image, video, document or carousel - inside the CRM and publish to Meta for approval. No Business Manager juggling.

WhatsApp broadcasts

Send an approved template to a whole segment at once - throttled, opt-out aware, with a live per-recipient delivery report.

WhatsApp flow builder

A drag-and-drop, stateful chat bot - menus, ask-and-save variables, media, timed waits and hand-off to a human. No code.

Free-form WhatsApp media

Send images, PDFs and video straight to a lead inside the 24-hour window - no template approval needed.

Click-to-WhatsApp attribution

Capture ctwa_clid and stitch website-chat leads back to the exact campaign. Not anonymous anymore.

Attribution reports

By click-id, UTM, referrer & cookie - a campaign → ad-set → ad revenue tree, in the CRM.

Meta Ads Manager sync

Connect your ad account and pull spend, clicks & impressions straight into the CRM, beside the revenue.

Multiple forms → pipelines

A form per segment, each mapped to its own pipeline and default routing. No code to wire them up.

Lead capture, everywhere

Embedded forms, public forms, WhatsApp, or the Partner API - captured with full cookie + click context.

Lead Explorer

Every lead and all the data we collect - attribution, cookies, timeline, messages - in one profile.

Pipelines

Drag-and-drop stages, round-robin assignment, per-form default routing, won/lost tracking.

Workflows & automations

No-code automations on lead-created, meeting-booked, no-show, stage-change & payment - route, message, convert.

Payment automations

Send WhatsApp on payment links, confirmations, reschedules & stage moves - automatically.

Scheduling & calendar

Live slot booking, Google Meet or Zoom links auto-created, added to the calendar, reminders, attended / no-show.

Email templates

Build email templates in the platform; send on the same triggers, from your own domain via custom SMTP.

AI assistant

Parse messy lead data, draft follow-ups, and summarize a contact’s history in a click.

Partner API & webhooks

Per-account inbound API mapped to your forms; signed outbound webhooks push events anywhere.

Our DB or your Firestore

Run on our isolated managed database, or connect your own Firestore if you’d rather own the storage.

Your own credentials

Your Meta pixel, GA4 keys, WhatsApp number, Razorpay and SMTP - your credentials, your workspace.

Team & roles

Granular per-module permissions, read-only analysts, round-robin reps.

Data isolation (RLS)

Postgres row-level security per workspace - a database guarantee, not a WHERE clause we hope nobody forgets.

Command Center

This week beside last week’s counted figures, target against trajectory, the two day-by-day stories the tiles compress.

Today’s Actions

Scale, cut, hold or rebalance, per campaign, priced on your own break-even and on who each one brought.

What We Found

Sixteen structural findings about your store, the same in every workspace, each naming the wrong conclusion first.

Customer Value

LTV by the ad that first found them, LTV to CAC, payback, acquisition cohorts aged from their own first order.

Costs and profit

Product, gateway, shipping and packaging per order; contribution beside revenue; POAS beside ROAS.

Audience Builder

Behavioural segments sized against what Meta can match, previewed before the sync, ranked on cost per add-to-cart.

Who buys next

A propensity score calibrated nightly on your own store. Never a ranking published as a rate.

Post-purchase survey

One question after every order, over WhatsApp or email. The answer is a credit model beside last click.

On-site recommendations

A widget with a holdout, eight rules previewed through the real engine, discounts learned from orders.

Abandoned checkouts

Every checkout as it is filled in, for Shopify native and every one-click app, with one definition of abandoned.

Site scan

Every tag on your site, what fires before consent, which ids survive. Free, nothing to install.

Tag observer

Records what every other tag on the page did and stitches it to the order, so a silent tag is named.

First-party path

A path on your root domain, no CNAME to classify. Server-set cookies, 400 days; Meta and Google cookies re-issued at their own lifetimes.

Event stream console

Every delivery and what happened to it, per-destination shadow switches, retry rules from Meta’s contract.

Custom signal builder

Twenty fields across four groups, any condition, one-click recipes, fanning out to every connected platform.

Deals and quotes

One row per sale beside one card per person; products and services; quotes built from the catalogue.

Phone verification

OTP at the button they meant to press, over WhatsApp or SMS. Fails open when no channel is configured.

Lead routing

Decide where leads land, per channel and per form. One Facebook page can fan out to many workspaces.

Google Ads Data Manager

Direct conversion uploads, enhanced conversions with basket data, no API token or Sheet to maintain.

Server GTM feed

One rich normalised event per order or lead to your own container, when you want full control.

See it on your own data

Every feature, working as one platform.

Start free and watch capture, measurement, follow-up and attribution run together on your very first lead.