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

    CONNECTIONS / WordPress / WordPress to Google OCI

    Your WordPress orders, wired to Google Ads offline conversion import.

    Connect WordPress and point Signals at your WordPress orders; it reconciles closed-won revenue to the Google Ads click through GCLID as orders complete, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    wordpress -> google-oci :: live

    1. ● wordpress → google.oci :: live
    2. > read closed_deals rows=48,097
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 42,325 matched

    WHAT THIS ENABLES

    WordPress to Google Offline Conversions

    WordPress to Google Offline Conversions: Signals reads your WordPress orders and reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your WordPress orders activated for Google Ads, as Signals reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 Google, away from any pixel. Here is how WordPress closes the loop.

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

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the records already in WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating Google Ads offline conversion import 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 Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your WordPress orders, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your WordPress orders, reconciles closed-won revenue to the Google Ads click through GCLID, and sends only the orders that changed, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: wordpress.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=wordpress.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-20T06:56:26"
    5. conversion_value 40123 · currency_code GBP
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from WordPress

    WordPress to Google Store Sales

    WordPress to Google Store Sales: Signals reads your WordPress orders and matches in-person…

    Learn more

    from WordPress

    WordPress to Meta Offline CAPI

    WordPress to Meta Offline CAPI: Signals reads your WordPress orders and credits dealer,…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the WordPress Google OCI sync run?

    Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds Google Ads on that cadence. Each run sends only the orders that changed, so a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.

    What match rate should a WordPress-sourced Google OCI 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 Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to Google OCI, in production this week.

    Talk to our team All WordPress use cases