CONNECTIONS / WordPress / WordPress to Google Store Sales
Your WordPress orders, wired to Google Store Sales matching.
Connect WordPress and point Signals at your WordPress orders; it matches in-person transactions to Google accounts as store-sales conversions as orders complete, hashed and consent-checked for Google Ads.
- ● wordpress → google.sales :: live
- > read closed_deals rows=42,016
- hash sha256(email,phone) consent=filtered
- route google deliver
- ✓ delivered · 35,714 matched
WHAT THIS ENABLES
WordPress to Google Store Sales
WordPress to Google Store Sales: Signals reads your WordPress orders and matches in-person transactions to Google accounts as store-sales conversions, hashed and consent-checked as orders complete.
- Offline and in-store sales from your WordPress orders activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
- Counter and showroom revenue inside the same ROAS view as online orders, drawn from your WordPress orders by content-led merchants on WordPress.
The click, the conversion, and the credit.
The conversion happens off Google, 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 Google Store Sales matching straight from WordPress orders.
From kickoff to verified events.
-
Connect
Scoped API access to WordPress, reading only your WordPress orders to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.
-
Map
Signals reads your WordPress orders, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.
-
Deliver
On each run, Signals pulls your WordPress orders, matches in-person transactions to Google accounts as store-sales conversions, and sends only the orders that changed, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.
- ● signals :: store sales upload
- > POST /offline_user_data_jobs source=wordpress.closed_deals
- transaction_time 2026-07-21T10:49:23 · transaction_amount_micros 39358000000
- currency_code SAR
- hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
- ✓ accepted match=85%
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 Meta Offline CAPI
WordPress to Meta Offline CAPI: Signals reads your WordPress orders and credits dealer,…
Learn more
same use case
ActiveCampaign to Google Store Sales
ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…
Learn moreAsked on almost every call.
How often does the WordPress Google Store Sales 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 store visits reconciled to campaign spend holds up on the store-sales match rate. The live debugger confirms every delivery inline.
What match rate should a WordPress-sourced Google Store Sales 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 Store Sales Direct API pinpoints the store-sales match rate, the number content-led merchants on WordPress tune against.
NEXT STEP