Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / WordPress / WordPress to Meta Offline CAPI

    Your WordPress orders, wired to Meta's offline optimization.

    Connect WordPress and point Signals at your WordPress orders; it credits dealer, branch, and phone sales to the Meta campaigns behind them as orders complete, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    wordpress -> meta-offline-capi :: live

    1. ● wordpress → meta.capi :: live
    2. > read closed_deals rows=34,926
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 29,338 matched

    WHAT THIS ENABLES

    WordPress to Meta Offline CAPI

    WordPress to Meta Offline CAPI: Signals reads your WordPress orders and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your WordPress orders activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your WordPress orders by content-led merchants on WordPress.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Meta, away from any pixel. Here is how WordPress closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta Order sync recorded in WordPress S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating Meta's offline optimization straight from WordPress orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to WordPress, reading only your WordPress orders to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals reads your WordPress orders, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your WordPress orders, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the orders that changed, with Meta's 62-day event window in the debugger.

    WHAT YOU GET

    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.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: wordpress.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=wordpress.closed_deals
    3. event_name "Purchase" · event_time 2026-07-22T02:45:34
    4. value 39529.00 · currency GBP
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-89334"
    6. ✓ accepted match=84%
    RELATED USE CASES

    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 more

    from 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 Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the WordPress Meta 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 Meta on that cadence. Each run sends only the orders that changed, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a WordPress-sourced Meta 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to Meta Offline CAPI, in production this week.

    Talk to our team All WordPress use cases