CONNECTIONS / WordPress / WordPress to Meta Custom Audience
Your WordPress orders, wired to Meta lookalike and suppression seeds.
Connect WordPress and point Signals at your WordPress orders; it keeps Meta audiences synced as adds and removals so lists never drift as orders complete, hashed and consent-checked for Meta.
- ● wordpress → meta.audience :: live
- > read segments rows=26,355
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 20,030 matched
WHAT THIS ENABLES
WordPress to Meta Custom Audience
WordPress to Meta Custom Audience: Signals reads your WordPress orders and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked as orders complete.
- Customer segments from your WordPress orders activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
- Lookalike seeds and suppression lists that track your live customer base, drawn from your WordPress orders by content-led merchants on WordPress.
WHAT FLOWS WHERE
WordPress to Custom Audience, mapped.
Signals reads the customer segments from your WordPress orders as orders complete, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Signals reads the customer segments from your WordPress orders as orders complete, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.
Built for the teams that own the number.
Content-led merchants on WordPress activating Meta lookalike and suppression seeds straight from WordPress orders.
From kickoff to verified events.
-
Connect
Scoped API access to WordPress, reading only your WordPress orders to feed Meta's Custom Audiences API, sized for audience refresh cadence.
-
Map
Signals reads your WordPress orders, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.
-
Deliver
On each run, Signals pulls your WordPress orders, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the orders that changed, with audience refresh cadence in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your WordPress orders and sends only the orders that changed.
Always-current lookalike seeds and exclusions from your WordPress orders, with API call volume steady because Signals sends only the orders that changed.
A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your WordPress orders.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=wordpress.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 26,355 · num_invalid_entries -195
- audience_id "1685677" · session "upsert"
- ✓ accepted match=76%
Adjacent moves on the same stack.
from WordPress
WordPress to Google Customer Match
WordPress to Google Customer Match: Signals reads your WordPress orders and projects your…
Learn more
from WordPress
WordPress to TikTok Custom Audience
WordPress to TikTok Custom Audience: Signals reads your WordPress orders and delivers…
Learn more
same use case
ActiveCampaign to Meta Custom Audience
ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Custom Audience
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…
Learn moreAsked on almost every call.
How often does the WordPress Meta Custom Audience 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 always-current lookalike seeds and exclusions holds up on audience refresh cadence. The live debugger confirms every delivery inline.
What match rate should a WordPress-sourced Meta Custom Audience 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 Custom Audiences API pinpoints audience refresh cadence, the number content-led merchants on WordPress tune against.
NEXT STEP