Integrations
Every ecosystem you sell and advertise on. One identity underneath.
Stores and apps, checkout and payments, ad platforms, messaging. Each one connects natively, with your own credentials and tokens exchanged server-side, and every one of them reads the same customer record.
Stores and apps
Shopify
Orders, checkouts, customers and refunds arrive by webhook and are deduplicated on your own order id, so a redelivered webhook is one order and one automation. The custom pixel is served with your key already in it, and cart attributes carry the campaign to any checkout.
- One-click connect; orders flowing in minutes
- Checkout creation and update, for abandoned checkouts
- Partial refunds keep the order a sale and the money honest
- Works on password-protected development stores
Appbrew, Apptile, MobiLoud, Twinr, Swipecart
A shopper taps an ad, installs your app, and buys three days later. Shopify files it as Direct. The app-builder package keeps the campaign attached to the order across the install and the days in between, with no app-store release.
- One tracking key in the app dashboard, no code
- A stable install id as the backstop when a checkout app rebuilds the cart
- Every app order is a Mobile app journey, not Direct
- Proven live on a store before it shipped
WooCommerce
Orders arrive by a webhook signed with your own secret, created and updated, so payments, cancellations and refunds follow the order. A short snippet copies the visitor id onto each order as hidden meta, so the sale joins the visit that made it even when the thank-you page never loads.
- Signed Order created and Order updated webhooks
- One snippet carries the visitor onto the order
- Reads GA4, Universal Analytics and GTM4WP dataLayers
- A sample order proves the setup before a real one
BigCommerce
Paste an API token and press Connect: the order webhooks are created for you, each carrying a secret header, and every order is read from the API. BigCommerce’s own cart id joins the order to its visit, with no checkout code to install.
- Order webhooks created from the settings card
- Cart id join, nothing added to checkout
- Refunds and cancellations follow the order
- Every delivery listed with what happened to it
Magento 2
A three-file module posts each order the moment it is placed, signed, with the shopper’s visitor id attached. Or let Cookiebees pull changed orders every five minutes through an integration token, cancellations and refunds included. Use either, or both.
- Signed order observer on order placement
- Optional order pull every five minutes
- Configurable products read as the line the shopper bought
- Reads GA4 and Universal Analytics dataLayers
Checkout and payments
Shopflo, GoKwik, Pragma
One-click checkouts strip the browser identity. Each partner is an entry in a registry that knows which id it forwards, and the pixel reads every one of them on a shared handler, so a checkout is stitched to the browser that started it and the journey survives a change of provider.
- Order attribute to browser key, per provider
- Mid-checkout steps captured: contact, address, shipping
- A new partner is one line of config, not a project
- A discovery log names the id when one is missing
Razorpay
Payment links from the lead, paid status on the deal, and a payment as a first-class trigger: a successful payment can fire a Purchase to Meta and Google, move the pipeline and send a WhatsApp confirmation.
- Send payment links from the lead over WhatsApp
- Payments drive automations and conversions
- Gateway fee counted as an order cost
- Receipts and confirmations on autopilot
Ad platforms
Meta: Pixel, Conversions API, Lead Ads, Catalog, Audiences
Cookiebees is a verified Meta Tech Provider. Pixel, CAPI, Lead Ads, catalog, ad spend and audiences each connect from a login popup with tokens exchanged server-side. Every Purchase leaves with 44 parameters, hashed, deduplicated on your order id, and a match score computed before it is sent.
- One-click connects for every surface, and a disconnect that actually stops the flow
- Ten behavioural parameters and custom conversions on any of them
- Behavioural segments synced as audiences, sized against match first
- Ad spend pulled from the Marketing API, never double-counted
Google Ads, GA4, Server GTM
Conversions upload directly to Google Ads through the Data Manager API with basket data, or through a Sheet when you would rather not grant an API token. GA4 receives lifecycle events on the client and session ids stitched from the visitor’s own cookies. Server GTM gets one rich event per order.
- Enhanced conversions with basket data, direct to the API
- gad_source read as a Google click and the network named
- GA4 with no PII, per Google policy
- Your own sGTM container as a destination
Messaging and email
WhatsApp Cloud API
One-click Connect through Embedded Signup. A two-way inbox tied to the customer, templates built in the product and published to Meta, broadcasts to a segment, a stateful flow builder, and every chat that starts from a button on your website attributed to its campaign.
- Templates with media headers and carousels, built in-product
- Broadcasts, throttled and opt-out aware
- Click-to-WhatsApp ads attributed by ctwa_clid
- Replies and button taps sent to Meta as engagement events
Email: your own domain, ZeptoMail, Klaviyo
Every automated email sends from your own domain through your SMTP, with opens and clicks tracked and taught back to the ad platforms. Klaviyo syncs natively by API key; more ESPs follow the same path.
- Own SMTP or ZeptoMail for volume
- Open and click as real engagement signals
- Store emails by moment: abandoned, won back, reorder
- Klaviyo audience sync
Bitespeed, Wati, Interakt, AiSensy
Already sending on another WhatsApp tool? Orders that arrive from its links are credited to it by name, as an owned channel, so the revenue those sends bring shows up as theirs rather than as Direct.
- Each tool recognised as its own source
- Filed under owned channels, never as paid
- Its own mark in every attribution journey
- No change to how you send
Google Calendar, Gmail, Meet, Zoom, Microsoft Teams
Booking pages that respect each rep’s live calendar, meeting links created automatically, reminders before and a no-show cascade after. Follow-ups send from the rep’s own Gmail so replies land where they already look.
- Live free/busy in slot picking
- Pooled or round-robin booking, least-loaded first
- Cal.com and Bolna bookings land as native meetings
- Google user data under Limited Use, never read or stored
Everything else
Partner API and webhooks
A per-workspace inbound API lets any system push leads in, mapped to your forms and routed by your workflows. Signed outbound webhooks push events wherever you need them, with retries.
- Inbound Partner API mapped to your forms
- Signed (HMAC) outbound webhooks with auto-retry
- Generic events: any payload to any endpoint
- No Zapier in the middle
Website WhatsApp chats, solved
Even your WhatsApp chats, perfectly attributed.
When a visitor taps your “Chat on WhatsApp” button, the CRM captures their cookies and click-ids at that moment and ties the conversation to the exact source. So a WhatsApp lead isn’t an anonymous phone number anymore, it carries its campaign, UTM and click-id like any other lead, and can fire conversions back to Meta and GA4.
- Cookies & click-ids captured the instant they tap to chat
- ctwa_clid ties click-to-WhatsApp ads to the exact campaign
- Organic website chats attributed via the session, too
- The WhatsApp lead carries source, UTM & click-id - not anonymous
New WhatsApp lead
via website WhatsApp chat
Connect your stack
Plug in your stack. Watch it agree with itself.
Connect the store and the ad accounts in a few popups, and every one of them starts reading the same customer. 30-day free trial, no card.