Naming and documentation release; no functional changes.<\/p>","1.1.0":"
Feed URLs changed to end in This plugin builds and maintains one CSV file per billing country<\/strong> in the Google Ads Customer Match Lists<\/strong> format from your WooCommerce orders billing data. Each country file is downloadable via a private and secure (tokenized) URL \u2014 ideal for marketing teams that run per-country campaigns and want clean, single-market audience lists.<\/p>\n\n The values are hashed with the same SHA-256 normalization used by both Google Ads Customer Match and Meta Ads Custom Audiences, so the same file can also be uploaded manually to Meta Ads Manager (see FAQ).<\/p>\n\n Why this export?<\/strong>\nNot all purchases are captured by Google Ads tracking; periodic uploads of Customer Match Lists<\/strong> help targeting and campaign performance.<\/p>\n\n Why per-country files?<\/strong>\nMarketing teams optimize Google Ads campaigns per country. Mixing a German audience into a Romanian campaign's match list pollutes the targeting. This plugin keeps each market in its own file.<\/p>\n\n WooCommerce \u2192 Marketing \u2192 Customer Match List<\/strong>.<\/p>\n\n From there you can:<\/p>\n\n Marketing teams optimize Google Ads campaigns per country. Mixing audiences degrades match-rate signals and wastes budget on irrelevant impressions. Each country file is independent and can be wired into its own Customer Match list. Google's Data Manager pulls each URL on its own schedule, so you can refresh some markets without affecting others.<\/p><\/dd>\n In Google Ads \u2192 Tools and Settings<\/strong> \u2192 Audience Manager<\/strong> \u2192 Your data sources<\/strong>, set up a Customer Match<\/strong> audience and choose the HTTPS<\/strong> data source. Paste the country-specific URL from the plugin's admin page. Google Ads fetches the file on its own cadence; our plugin keeps the file fresh per the schedule you picked.<\/p><\/dd>\n Yes. Meta Ads Custom Audiences use the same SHA-256 hashing of normalized (trimmed, lowercased) values, so a country CSV can be uploaded to Meta Ads Manager as a customer list \u2014 map the columns in Meta's upload screen. Note that Meta does not pull files from URLs; the pull-from-URL workflow is Google-specific, so on Meta use manual upload.<\/p><\/dd>\n Roughly 10 seconds per 150,000\u2013200,000 orders on typical hardware. The query path is direct SQL against In theory it's impossible as billing and shipping is country based; but in case this ever happens they are skipped. There is no correct file to route them to, and Google's per-country Customer Match campaigns can't use them anyway. The same applies to orders with an invalid country code.<\/p><\/dd>\n They get written. Google Customer Match accepts a row with any one<\/strong> of: email, phone, or full mailing address (first name + last name + zip). The plugin includes a row as long as one of those identifiers is present alongside a valid country. Deduplication is still single-column: it uses email when available, otherwise phone, otherwise the mailing address.<\/p>\n\n Google handles cross-identifier deduplication on its side after matching to a Google account \u2014 so a customer who orders once with email + phone and again with only their phone will appear as two rows in the CSV but as one user in your Customer Match audience.<\/p><\/dd>\n Yes \u2014 but only if they actually ordered from multiple countries!<\/p><\/dd>\n This is by design, as every To regenerate from scratch (for example after toggling debug mode or changing normalization), use WooCommerce \u2192 Marketing \u2192 Customer Match List \u2192 Danger zone \u2192 Delete all files & reset dedup<\/strong> or Some security plugins (\"Admin and Site Enhancements\" \/ ASE has this option, Disable REST API, etc.) block all unauthenticated REST traffic. This plugin does not<\/strong> attempt to override those policies \u2014 that would be hostile to the security setting you deliberately chose.<\/p>\n\n If you hit this error, whitelist the plugin's feed prefix in your security plugin's exclusion list: For most countries (RO, DE, UK, FR, ES, US, NL, BE, PT, IT mobile, \u2026) it's correct. The routine accepts There is a known limitation for Italian landlines<\/strong>: in Italy the leading If you need strict accuracy across all locales, swap WordPress's built-in cron is request-triggered: it only fires if someone hits the site. On low-traffic stores it may drift. For predictable runs, configure a real system cron that calls Yes. use the integrated define Yes. The plugin declares The plugin itself makes no outbound HTTP calls<\/strong> \u2014 no analytics, no tracking pixels, no telemetry. All processing happens on your WordPress install.<\/p>\n\n However, the whole point of the workflow is that Google Ads (or any other consumer you configure) will pull the CSV from your site<\/strong> at the tokenized URL. Anyone in possession of that URL can retrieve a file containing:<\/p>\n\n Treat the tokenized URL as a secret. If it leaks, use Reset Token<\/strong> in the admin (or wp-content\/uploads\/customer-match-list-google-ads\/customer-match-{hash}-{country}.csv. The The settings page does a one-second loopback HTTP request to the uploads directory URL ( The check is cached for an hour and re-runs immediately if you click Re-check now<\/strong>.<\/p><\/dd>\n Google Ads Customer Match uses data uploaded within the last 540 days. The plugin doesn't enforce this so you can decide how much history to include. The \"Last 540 days\" preset in the backfill range dropdown matches that window. Older data is still appended if you ask for it, but Google won't actively use it.<\/p><\/dd>\n Yes. One row per unique The plugin's admin page shows a notice and stops scheduling cron, but data isn't lost. Re-activate WC and the plugin resumes from the noted order.<\/p>\n\n If you uninstall the plugin then the The files contain hashed personal information (email, phone, name) and plaintext country + ZIP. Treat the directory and its access URLs as sensitive data! If a customer requests deletion under GDPR \/ similar:<\/p>\n\n Targeted per-row deletion isn't supported on purpose: the SHA-256 hashing is one-way and rebuilding from source is fast.<\/p><\/dd>\n\n<\/dl>\n\n\n.csv<\/code> and hashing normalization was corrected \u2014 run "Delete all files & reset dedup", then re-run the backfill.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3607354,"resolution":"1","location":"assets","locale":"","width":1878,"height":1726}},"screenshots":{"1":"The admin page under WooCommerce \u2192 Marketing, showing the schedule selector, per-country URL table, and backfill controls.","2":"Backfill in progress \u2014 live progress card with orders processed, rows written and order lock.","3":"WP-CLI: wp cmls status<\/code> printing the per-country breakdown."}},"plugin_section":[],"plugin_tags":[567,271475,985,456,286],"plugin_category":[45,55],"plugin_contributors":[97974],"plugin_business_model":[],"class_list":["post-318548","plugin","type-plugin","status-publish","hentry","plugin_tags-csv","plugin_tags-customer-match","plugin_tags-google-ads","plugin_tags-marketing","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-seo-and-marketing","plugin_contributors-rwky","plugin_committers-rwky"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/customer-match-list-google-ads.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/customer-match-list-google-ads\/assets\/screenshot-1.png?rev=3607354","caption":"The admin page under WooCommerce \u2192 Marketing, showing the schedule selector, per-country URL table, and backfill controls."}],"raw_content":"\nHow it works<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
--days=N<\/code>, --since<\/code>, --until<\/code>), dry-run, and batch-size control.<\/li>\nEmail, Phone, First Name, Last Name, Country, Zip<\/code>.<\/li>\n+<\/code> \u2014 the same hashing Meta Ads Custom Audiences accept.<\/li>\nwp-content\/uploads\/customer-match-list-google-ads\/<\/code> with filenames containing a 64-bit hash derived from the token.<\/li>\nnocache_headers()<\/code>.<\/li>\nJOIN<\/code> on wc_orders<\/code> + wc_order_addresses<\/code> (or posts<\/code>+postmeta<\/code> on classic). Designed for stores with tens of millions of orders.<\/strong><\/li>\n<\/ul>\n\nAdmin Dashboard Settings<\/h4>\n\n
\n
WP-CLI<\/h4>\n\n
\n
wp cmls backfill<\/code> \u2014 one-time backfill of historical orders, split by country. Flags: --statuses=completed<\/code> (default), --all-statuses<\/code>, --days=N<\/code>, --since=YYYY-MM-DD<\/code>, --until=YYYY-MM-DD<\/code>, --dry-run<\/code>, --batch-size=5000<\/code>, --force<\/code>.<\/li>\nwp cmls run-now<\/code> \u2014 runs the incremental writer immediately (same code path as the scheduled cron).<\/li>\nwp cmls status<\/code> \u2014 prints a table with one row per country: row count, file size, URL.<\/li>\nwp cmls reset-token<\/code> \u2014 regenerates the token and renames every country file to match.<\/li>\nwp cmls delete-file<\/code> \u2014 deletes every country CSV and truncates the dedup table.<\/li>\n<\/ul>\n\n\n\n
wp-content\/plugins\/customer-match-list-google-ads<\/code> (or install from the WordPress.org repository).<\/li>\n\n
wp cmls backfill --days=540<\/code> (or any range that suits you).<\/li>\n<\/ul><\/li>\n\n
Why one file per country?<\/h3><\/dt>\n
How do I plug a URL into Google Ads?<\/h3><\/dt>\n
Does the file work with Meta (Facebook) Ads?<\/h3><\/dt>\n
How long does the backfill take?<\/h3><\/dt>\n
wc_orders<\/code> + wc_order_addresses<\/code> (HPOS).\nFor 1M+ orders the CLI is still the most reliable option because no PHP\/web timeout applies; the admin Action-Scheduler-backed runner also handles 1M+ but each batch must complete within the host's PHP limit and if it does not then it won't finish.<\/p><\/dd>\nWhat happens to orders with no billing country?<\/h3><\/dt>\n
What about orders with no email?<\/h3><\/dt>\n
Will the same customer appear in multiple country files?<\/h3><\/dt>\n
I ran the backfill twice \u2014 why didn't it write more rows the second time?<\/h3><\/dt>\n
(email, country)<\/code> pair is recorded the first time it's seen and never re-written.<\/p>\n\nwp cmls delete-file<\/code>, then run the backfill again.<\/p><\/dd>\nI get a 401 \"REST API has been restricted to authenticated users\" when I open the URL<\/h3><\/dt>\n
\/wp-json\/cmls\/v1\/feed\/<\/code>. Google Ads (and any other configured consumer) needs unauthenticated GET access to that prefix \u2014 the tokenized URL is the sole authentication mechanism.<\/p><\/dd>\nPhone numbers \u2014 how reliable is the normalization without libphonenumber?<\/h3><\/dt>\n
+<\/code>, 00<\/code>, the country's national trunk 0<\/code>, and bare national numbers (using the order's billing country to fill in the dialing code).<\/p>\n\n0<\/code> is part of the national number, not a trunk prefix, so the routine may strip a digit it shouldn't. Italian mobile numbers (3xx) are fine.<\/p>\n\nCMLS_Writer::normalize_phone()<\/code> for a libphonenumber-based implementation.<\/strong><\/p><\/dd>\nIs WP-Cron reliable enough for the incremental updates?<\/h3><\/dt>\n
wp-cron.php<\/code> every minute \u2014 standard WordPress practice and recommendation.<\/p><\/dd>\nCan I disable hashing for debugging?<\/h3><\/dt>\n
CMLS_DISABLE_HASHING<\/code> in wp-config.php<\/code>:<\/p>\n\ndefine( 'CMLS_DISABLE_HASHING', true );\n<\/code><\/pre><\/dd>\nDoes this support High-Performance Order Storage (HPOS) \/ Legacy Postmeta?<\/h3><\/dt>\n
custom_order_tables<\/code> compatibility and queries wc_orders<\/code> + wc_order_addresses<\/code> directly when HPOS is enabled. On classic (postmeta) storage it falls back to wp_posts<\/code> + wp_postmeta<\/code> with a single conditional-aggregation query per batch.<\/p><\/dd>\nDoes the plugin send any data outside my server?<\/h3><\/dt>\n
\n
wp cmls reset-token<\/code>) to invalidate all existing URLs and rename the files on disk. See the site's Privacy Policy page \u2014 this plugin registers suggested policy text via WordPress's Privacy tool.<\/p><\/dd>\nWhere are the files stored?<\/h3><\/dt>\n
{hash}<\/code> is a 16-character hex derived from the secret token, so filenames are not guessable. An index.php<\/code> placeholder in the directory prevents listing if your host happens to have it enabled and then it notifies the shop owner (when visiting the dashboard).<\/p><\/dd>\nWhat about directory listing?<\/h3><\/dt>\n
\/wp-content\/uploads\/customer-match-list-google-ads\/<\/code>) when you open it, caches the result for an hour, and shows one of three banners:<\/p>\n\n\n
index.php<\/code> silence file is served, or because the webserver explicitly blocks directory listings).<\/li>\nIndex of \u2026<\/code> or with our CSV filename prefix in the body. Anyone who guesses the directory URL can enumerate your country files. Fix it: Apache \u2192 Options -Indexes<\/code> (or rely on the WordPress-shipped .htaccess<\/code>); nginx \u2192 autoindex off;<\/code> in the relevant location<\/code> block.<\/li>\nWhat about Google's 540-day lookback window?<\/h3><\/dt>\n
Can I include orders that aren't `completed`?<\/h3><\/dt>\n
wp cmls backfill --statuses=processing,completed,on-hold<\/code> for an explicit list, or --all-statuses<\/code> for everything. The scheduled (incremental) writer is wc-completed<\/code> only by design \u2014 Customer Match doesn't benefit from including pending or cancelled orders.<\/p><\/dd>\nHow is the deduplication table sized?<\/h3><\/dt>\n
(email_hash, country)<\/code>. At ~110 bytes per row, 1M unique customers across all countries is roughly 100 MB.<\/p><\/dd>\nWill deactivating WooCommerce break it?<\/h3><\/dt>\n
uninstall.php<\/code> routine cleans up the option keys, database tables, and any generated files.<\/p><\/dd>\nGDPR \/ privacy<\/h3><\/dt>\n
\n
wp cmls delete-file<\/code>).<\/li>\n1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
.csv<\/code> so Google Ads' HTTPS connector accepts them.<\/li>\n1.0.0<\/h4>\n\n
\n
(identity, country)<\/code> dedup, WP-CLI and Action Scheduler backfills, tokenized REST download endpoint, HPOS-first SQL.<\/li>\n<\/ul>","raw_excerpt":"WooCommerce to Google Ads Customer Match CSV exporter. Per-country lists, scheduled\/WP-CLI backfills, secure URLs. Files also work for Meta Ads.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/318548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=318548"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/rwky"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=318548"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=318548"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=318548"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=318548"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=318548"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=318548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}