CONNECTIONS / WordPress / WordPress to Snap Offline CAPI
Your WordPress orders, wired to Snapchat in-store conversions.
Connect WordPress and point Signals at your WordPress orders; it reports in-store purchases against the Snapchat campaigns that reached the buyer as orders complete, hashed and consent-checked for Snapchat.
- ● wordpress → snap.capi :: live
- > read closed_deals rows=54,147
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 47,108 matched
WHAT THIS ENABLES
WordPress to Snapchat Offline CAPI
WordPress to Snapchat Offline CAPI: Signals reads your WordPress orders and reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked as orders complete.
- Offline and in-store sales from your WordPress orders activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
- Physical-world sales counted inside Snapchat performance, drawn from your WordPress orders by content-led merchants on WordPress.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how WordPress closes the loop.
Built for the teams that own the number.
Content-led merchants on WordPress activating Snapchat in-store conversions straight from WordPress orders.
From kickoff to verified events.
-
Connect
Scoped API access to WordPress, reading only your WordPress orders to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals reads your WordPress orders, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.
-
Deliver
On each run, Signals pulls your WordPress orders, reports in-store purchases against the Snapchat campaigns that reached the buyer, and sends only the orders that changed, with offline event timing in the debugger.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Offline CAPI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment WordPress records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=wordpress.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784335777 · price 32860 · currency USD
- ✓ accepted · match=true
Adjacent moves on the same stack.
from WordPress
WordPress to Google OCI
WordPress to Google Offline Conversions: Signals reads your WordPress orders and reconciles…
Learn morefrom WordPress
WordPress to Google Store Sales
WordPress to Google Store Sales: Signals reads your WordPress orders and matches in-person…
Learn more
same use case
ActiveCampaign to Snap Offline CAPI
ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreAsked on almost every call.
How often does the WordPress Snap Offline CAPI sync run?
Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds Snapchat on that cadence. Each run sends only the orders that changed, so in-person conversions Snapchat can bid on holds up on offline event timing. The live debugger confirms every delivery inline.
What match rate should a WordPress-sourced Snap Offline CAPI batch expect?
Match rate follows identifier coverage in your WordPress orders, which content-led merchants on WordPress control, not WordPress itself. A record with a current hashed email or phone matches for Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number content-led merchants on WordPress tune against.
NEXT STEP