Cookiebees

Signals back

Every conversion leaves enriched.
You can inspect every payload.

Purchases go back to the platform that earned them with 44 parameters attached, hashed, deduplicated on your own order id, and scored for match quality before they leave. The exact payload is one click away, so you never have to trust us blind.

Questions this answers

  • What exactly did Meta receive for this order?
  • Why is my match quality 6 and what would make it 9?
  • Can I see what would be sent before I switch it on?
  • Can Meta learn from my emails and WhatsApps?

44 parameters

A pixel cannot send what it does not know.

Which order this is for that person, their lifetime value, prepaid or COD, the discount, every channel in the path, how long they took, ten behavioural parameters with real distributions. Attached to the Purchase, so custom conversions built on any of them inherit the full history. Value on the wire as what they paid, or profit after costs.

  • Ten behavioural parameters, real numbers on every value
  • The exact values to type into a Meta rule, shown
  • Describe the order rather than invent an event for it
  • Health data stripped before anything leaves
Event stream · Purchase · parameters44 attached

Your pixel sends the order. This is what we know about it.

Lifecycle · 7
order_index1is_first_purchasetruecustomer_ltv8430days_since_last_order47
Money · 6
payment_methodprepaiddiscount_pct12.5coupon_codeWELCOME10
Journey · 10
first_touch_channelmeta_adslast_touch_channelgoogle_adshas_paid_touchtrue
Behaviour · 10
sessions_before_order3abandoned_before_buyingtruedecision_speedfew_days
Product · Place · State · 8
primary_categorySkincareship_stateKarnatakaorder_statuspaid

Built on one parameter, in Meta

Purchase where is_first_purchase = true → CB First-time buyers · cost per genuinely new customer, per campaign

Every one is opt-in, omitted when unknown, and named for good: a custom conversion built on it inherits the Purchase's full history.

The event stream

A console, not a settings screen.

Every delivery and what happened to it, per destination, with the payload readable. Per-destination shadow switches show exactly what would be sent before anything is. The sending switches ask before they move and email the owner after. Retry rules come from Meta’s contract; held events are resent.

  • Received and sent per event, per destination
  • Shadow mode per destination
  • Trial-run suffix for Meta event names
  • A ledger that names the order a human can find
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.

Integrations

Meta, Google Ads, GA4, server GTM. And five more.

Meta CAPI with match quality scored first. Google Ads conversions through the Data Manager API with basket data, or a Sheet with no API token. GA4 on the visitor’s own client and session ids. Your own server GTM container. TikTok, LinkedIn, Snapchat, Pinterest and Reddit through generic adapters.

  • One-click connects, and a disconnect that actually stops the flow
  • Product IDs mapped per destination
  • Auto fans out to every connected platform
  • Google Ads conversions live in the event stream
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.

Custom and engagement signals

Twenty fields, any condition. And the signals nobody else sends.

A builder with twenty fields across four groups, one-click recipes for the lead-gen conversions that need a condition, standing rules per workspace. Email opened, email link clicked, WhatsApp replied, tracked link tapped: each sent server-side as a real event with the right action source. Never a fabricated page view.

  • Fifteen high-intent presets, created off
  • Workflow-editor conditions and a None mode
  • Engagement retention from one to 180 days
  • Real actions only, no value attached
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.

Inside the module

Inside Signals

Every switch is a decision you make; nothing fires until you say so.

Event stream

The console: sections, switches, ledger

Integrations

Every ad platform on one page, with its status

Custom signals

Builder, recipes, presets

Match quality

Scored per event, the field to fix named

Payload inspector

The exact JSON posted, via the real sender

Catalog IDs

Explicit per-destination choice; GA4 mappable

See a real payload end to end from the homepage: what came in, what we attached, what left, and the match score it earned.

Send the platforms something worth learning from

Every conversion enriched.Every payload inspectable.

Connect Meta and Google in two popups and watch the first enriched Purchase leave with its payload open.