WhatsApp CAPI
Attribute the WhatsApp conversation, all the way to purchase.
Datahash sends Click-to-WhatsApp and downstream conversion events to Meta CAPI, so campaigns optimize on real business outcomes rather than message opens.
- ● whatsapp.capi :: live
- > event Purchase value=2,350 INR
- hash sha256(em,ph) ctwa_clid=captured
- stitch conversation → purchase matched
- ✓ delivered · events_received 1
Built for the teams that own the number.
Teams running Click-to-WhatsApp campaigns with no signal past the first message.
From kickoff to verified events.
-
Track
CTWA click tracking from ad to conversation.
-
Capture
Downstream conversion events such as message reply, cart, and purchase.
-
Deliver
Delivery via Meta CAPI with dedupe against WhatsApp Business API.
WHAT FLOWS WHERE
One use case, every source.
A Click-to-WhatsApp ad opens a conversation, Signals persists the ctwa_clid with hashed identifiers and stitches the downstream purchase to it, then delivers the outcome to Meta's Conversions API.
A Click-to-WhatsApp ad opens a conversation, Signals persists the ctwa_clid with hashed identifiers and stitches the downstream purchase to it, then delivers the outcome to Meta's Conversions API.
What ships with this offering.
CTWA campaigns optimizing on purchases instead of conversation starts.
A stitched journey from ad click to WhatsApp thread to conversion.
Hashed, consent-aware identifier handling throughout.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: event payload
- > POST /{dataset}/events action_source=business_messaging
- event_name "Purchase" · ctwa_clid "ARAf3k…"
- ph sha256 "c41d88…" · em sha256 "27f0a1…"
- value 2350 · currency INR
- ✓ events_received 1 · pii=hashed-at-ingestion
Adjacent moves on the same stack.
meta
Meta WhatsApp CAPI
Datahash ties a Click-to-WhatsApp conversation to the purchase or qualified lead it produces and delivers that outcome to Meta's Conversions API, so campaigns optimize on completed sales instead of message opens.
Learn morecross-channel
Lead funnel events
Datahash syncs lead-quality signal from your CRM back to Meta, Google, TikTok, and LinkedIn so campaigns optimize on the leads that actually convert.
Learn moremeta
Meta Web CAPI
Datahash is a Meta Business Partner. We set up Meta Conversions API on your website server-side, deduped with your existing Meta Pixel, hashed and privacy-safe.
Learn moremeta
Meta CAPI for CRM
Datahash ingests lead status from your CRM and sends Meta the qualified events it needs to optimize on lead value instead of lead volume.
Learn moreQuestions your team will ask.
Do we need the WhatsApp Business API?
Yes, for downstream events. The WhatsApp Business API, or a BSP built on it, is where conversation and conversion signals originate, since Meta does not expose that data any other way. Datahash connects to your existing WhatsApp Business API or BSP integration and maps message, cart, and purchase signals to CAPI events without requiring a new messaging setup.
How do you tie a message to a purchase?
The CTWA click carries the WhatsApp click ID, ctwa_clid, into the conversation, and Datahash persists it alongside the customer's hashed identifiers rather than discarding it once the chat opens. Even if the purchase closes days later, in your CRM, order system, or a completely separate checkout, that stored identifier lets the sale match back to the originating ad and campaign.
How is consent handled?
Customers opt in to WhatsApp conversations by design, since starting a chat is itself an active choice, and Datahash only forwards hashed identifiers for permitted purposes tied to that opt-in. Consent flags from your CRM or CMP are honored before any event is sent, so a customer who withdraws consent stops appearing in delivered events immediately.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.