Cookiebees
1Capture: Every visit, on your own domain

Store sync

Every order, from every place
it was placed.

Your store, the one-click checkout, your app and your courier each know part of an order. Cookiebees puts them on one row: the visit that started it, the checkout that took it, and whether the parcel came back.

30-day free trialNo card requiredSet up in minutes

Does a GoKwik or Shopflo order still credit my ad?

Are returned COD orders still counted as revenue?

Orders · todayevery source, one row
OrderCame fromParcel
#10482Meta adDelivered
#10483Google adIn transit
#10484Your appDelivered
#10485Meta adReturned
#10486Keyed by teamManual
The store, the checkout app, the app and the courier each fill their part. A return comes off the day it was ordered.

Where do app orders and orders my team keyed go?

Which store platforms can I connect?

What it is worth

Revenue you can bank on, credited to the right ad

Returns stop counting as revenue

A parcel that comes back leaves the day it was ordered, so that day’s ROAS reads what you really earned.

Checkout apps keep the journey

GoKwik, Shopflo, Shiprocket Checkout and Pragma orders are joined back to the visit that started them.

A coverage number you can defend

App orders and orders your team keyed are counted apart, so the web number is never diluted.

One row per order

The browser, the webhook and the checkout app, on one order.

On Shopify the order webhook brings the store’s own record the moment an order is placed. The custom pixel and the site script record the visit. The visitor id rides the cart onto the order, which is how each sale is joined to the visit that made it. Nothing acts on the order until the store’s record is in.

  • Shopify: one webhook address for orders, updates, fulfilments and refunds
  • WooCommerce, BigCommerce and Magento connect their orders on their own cards
  • Any other store: the data layer, or post the order from your server
  • Stripe, SamCart and Razorpay payment links for sales outside a store
Orders · #10482arriving
Shopify custom pixel· checkout steps, from the checkout app
Shopify order webhook· the store's own record of the order
Visitor id on the cart· carried through checkout onto the order
Value·
Payment·
Items·
Checkout·
Journey·
Each source is kept as it arrived. The order is read once, after the store's own record is in.

One-click checkouts

The checkout app took the order. The visit still gets the credit.

A checkout app replaces Shopify’s checkout, so Shopify’s checkout events never fire. Cookiebees reads the app’s events instead and stores them under the same names. The visitor id written to the cart survives the app’s own checkout, and each app’s session ids are a second way back to the visit.

  • GoKwik, Shopflo, Shiprocket Checkout and Pragma, picked once per store
  • Each checkout step listed with where it comes from, and what one app cannot measure
  • Health: your last 30 days of orders by the checkout that took them
  • The install code warns when orders go through a checkout the pixel is not set to
Cart attributesin transit

Browsing

visitor id in a first-party cookie

Cart

id written onto the cart as an attribute

Checkout

cookie gone - the attribute travels anyway

Only our own keys are sent, so subscription apps, gift notes and delivery dates all survive untouched.

Delivered or returned

Your courier knows which COD parcels came back. Now your revenue does too.

Connect Shiprocket, Delhivery, ClickPost or any other shipping partner with one webhook address. A parcel returned to origin stops counting as revenue on the day the order was placed. A failed delivery can start a WhatsApp while the sale can still be saved.

  • Shiprocket and ClickPost from their dashboards; Delhivery switched on by your account manager
  • Any other partner through a generic webhook
  • Order delivered can report the sale to an ad platform once it is really paid for
  • Each partner’s address carries its own secret key
Order #10482 · ₹2,340 · cash on deliveryin transit

Shipped

Shiprocket · AWB 1442…07

Delivery attempt failed

customer not reachable · a WhatsApp can go now

Returned to origin

the parcel is back at your warehouse

Revenue, 3 Oct

the day #10482 was placed

₹48,620

The money that never arrived leaves the day the order was placed, so that day's revenue and ROAS read what you earned.

Where it was placed

Web orders, app orders and keyed orders, each counted as what it is.

An app built on Appbrew sends its in-app journey, so an app order joins the screens that led to it instead of reading Direct. A draft order your team keyed has no browser behind it, so it sits on its own Manual tab and never counts against your web coverage.

  • App orders with no campaign read Mobile app, their own channel
  • A deep link that opened the app keeps its campaign, even days later
  • A draft order with no web trace is offline; one a checkout app completed is not
  • Refunded orders kept in the list, so totals reconcile with the store
Orders · where each was placed
#10482

Website

joined to the visit · Meta ad

web
#10483

Your app

joined to the in-app journey · Appbrew

app
#10484

Draft order

keyed by your team · nobody browsed

manual
All ordersManualRefundedkeyed orders sit on their own tab
A keyed order never had a browser, so it never counts against your web coverage.

Store & checkout sync, on your own site.

Start a workspace and watch it work on your next order or lead, or let us walk you through it.

Switching it on

Connecting a Shopify store

Settings, Tracking takes you through it in this order. Other platforms follow the same idea on their own cards.

  1. 1

    Paste the site script

    Into theme.liquid, just before the closing head tag. It writes the visitor id to the cart.

  2. 2

    Add the order webhook

    In Shopify, Settings, Notifications, Webhooks: one address for orders and their later changes.

  3. 3

    Pick your checkout

    Shopify checkout, or the app the store runs: GoKwik, Shopflo, Shiprocket Checkout or Pragma.

  4. 4

    Paste the custom pixel

    Into Settings, Customer events. It is built for the checkout you picked.

Inside the module

What is inside

Each source has a card that says when it last sent something, and how many failed.

Shopify

Connection, Checkout, Custom pixel and Health, with page views from each collector

Other stores

WooCommerce, BigCommerce, Magento, and custom stores through the data layer

Checkout apps

GoKwik, Shopflo, Shiprocket Checkout and Pragma, each seen or not seen on your store

Shipping partners

Shiprocket, Delhivery, ClickPost and any other, each with its own address and setup steps

Mobile app

The Appbrew integration: screen views to purchase under one device id

Orders

All orders, Manual and Refunded tabs, each order with its journey and its sources

Integrations shows when each source last sent something, and Shopify's Health tab shows your last 30 days of orders by the checkout that took them.

Where this sits

One of the four steps an order goes through.

Every feature reads the same identity. Open any of them; each has its own page.

Connect your store

Every order joined.Every return taken off.

Connect the store, pick your checkout and add your courier. The next order arrives with its visit, and the next return comes off the right day.