Contact Fields
Most of a Keap contact record needs no custom fields and no sync before you can map it. The connector ships with the built-in catalog wired in: names, job title, website, lead source, three email slots, five phone slots, two fax slots, three full mailing addresses, company, and seven social networks. Map them like any other field and they sync both directions.
Custom fields are the exception that needs a step. Yours live in your Keap app, so import them with Sync Fields on the connector screen's Data Sync panel and they join the same picker under Custom Fields.
Finding fields in the picker
The field map groups the built-ins the way the Keap record itself is shaped: Contact, Email, Phone, Fax, Social, one group per address, and Custom Fields for what you imported.
Search matches more than the label. Typing zip finds every postal code, mobile or cell finds Phone 1, primary finds Email 1, and the social networks answer to their common short names as well as their full names.
The built-in catalog
| Group | Fields |
|---|---|
| Contact | First Name, Last Name, Job Title, Website, Lead Source, Company |
| Email 1, Email 2, Email 3 | |
| Phone | Phone 1 through Phone 5 |
| Fax | Fax 1, Fax 2 |
| Billing Address | Street 1, Street 2, City, State, Postal Code, Country |
| Shipping Address | Street 1, Street 2, City, State, Postal Code, Country |
| Other Address | Street 1, Street 2, City, State, Postal Code, Country |
| Social | Facebook, LinkedIn, Twitter, Instagram, Snapchat, YouTube, Pinterest |
Every field in the table syncs both ways. A value a member edits on your site lands in Keap, and a value your Keap campaign changes reaches your site on the next sync, where shortcodes like [memb_contact] and the member profile treat it as any local value.
Social fields
Seven networks map without any extra setup: Facebook, LinkedIn, Twitter, Instagram, Snapchat, YouTube, and Pinterest. One field per network per contact, and each syncs with the rest of the catalog.
| Network | Also searches as |
|---|---|
| fb | |
| x | |
| ig | |
| Snapchat | snap |
| YouTube | yt |
| pin |
A handle or profile URL captured on your site lands in the matching social account entry on the Keap contact, and what Keap already holds reaches your site through the mapped field. Clearing the value locally clears it in Keap, the same as any other writable field.
Boundary behaviors
A few translations happen at the edge so the two systems stop disagreeing about format.
Email 1 is the anchor. Keap resolves your members by email address, so Email 1 never clears. Emptying the local value skips the push rather than sending an empty email that would orphan the contact.
Country codes translate. Both sides follow ISO 3166-1, the international standard for country codes, just not the same column of it: your site holds the two-letter form (US, CA), the dialect WordPress and WooCommerce use, and Keap validates the three-letter form (USA, CAN). The connector converts each into the other's standard in both directions, so an address never fails over country format.
Company maps by name. The local value is the company name you typed. The connector resolves it to the matching company record in Keap and creates one when nothing matches exactly. Clearing the local value unlinks the company from the contact.
Profile edits push on their own. A member editing their WordPress profile sends name, email, and website to Keap without waiting on a field map. Everything else moves through the map.
One bad field can hold up a batch. Keap validates an update as a unit. One invalid value, a malformed country for instance, rejects the entire push, good fields included. The failure lands in the debug log with the field groups that were sent, so the log names the suspects.