Intercom custom attributes are named fields on a contact. They store the facts Inbox, outbound, and Series rely on. Mapping from WordPress means those facts update when the site of record changes, not when someone edits Intercom by hand.
Sync Engine for Intercom maps WordPress and WooCommerce fields into those attributes, including role tags, custom user fields, and store metrics.
Why custom attributes matter
- Automations branch on attributes.
- Support snippets need plan or LTV.
- Stale attributes send the wrong journey.
- CSV updates rot within a week.
If Intercom still thinks someone is on the free plan after they upgraded in WordPress, that is an attribute problem, not a copywriting problem.
What you can map
WordPress
- Roles → tags, with tag automation when roles change
- WordPress profile fields and custom user fields
- Membership-oriented fields when present
WooCommerce
- Billing / shipping fields
- Total spent, order count
- Metrics Sync Engine can compute: LTV after refunds, AOV, first/last order, days since, segments New / VIP / At-Risk / Regular
How mapping works
Map fields into Intercom attributes. Sync Engine for Intercom can create the attribute in Intercom if it is missing, so you are not blocked on a manual Intercom UI step for every new field.
LMS / membership
On membership sites, map plan and status as attributes. The membership and LMS guide covers which events to turn on.
Example mapping table
| WordPress / Woo source | Intercom destination | Why it matters |
|---|---|---|
| WP role | Role tag | Entitlements / messaging |
| Membership level | Custom attribute | Segment by plan |
| Total spent / order count | Attribute or metric | VIP / at-risk |
| Last order date | Custom attribute / metric | Win-back timing |
| Custom checkout or profile field | Custom attribute | Vertical-specific automations |
Approaches compared
| Approach | Pros | Fit |
|---|---|---|
| Manual in Intercom UI | Fine for one-offs | Doesn’t scale |
| Custom Intercom build | Flexible | Weeks to build, and you maintain it after every API change |
| Zapier field mapping | Flexible | Task cost / drift |
| Sync Engine for Intercom mapping | Built for WP/Woo | Runs on your WordPress site, next to WooCommerce |
How mapping works in Sync Engine
Install the plugin and connect with OAuth or an Access Token. See the connect guide.
The plugin can create attributes if they are missing.
Map WordPress and WooCommerce fields into Intercom attributes in the admin.
Sync and verify on a test contact, then wire Intercom automation to the attribute.
Plan details live on the WordPress Intercom plans page.
Governance tips
- Name attributes consistently (e.g. plan name, not mixed spellings of the same field)
- Avoid duplicate writers (Zapier + plugin on the same field)
- Don’t map secrets or personal data you shouldn’t store in Intercom
- Test automations after every mapping change
- For bulk backfill of mapped fields, use bulk sync in small batches you can stop
FAQ
Can Sync Engine update Intercom custom attributes?
Do I need developers?
Is this a developer guide?
WooCommerce metrics as attributes?
Is Messenger required?
Where can I see pricing?
Related
Map the fields your automations already assume exist
Install free, connect, then map WordPress and Woo fields into Intercom attributes.
Install free on WordPress.org