Skip to main content
Field mapping decides which Salesforce data lands on which Spotzee user property. The integration ships with sensible defaults for the standard email-and-name fields. You add more mappings for the custom fields that matter to your campaigns.
Field mappings are configured per integration. Open the integration from Integrations → Salesforce and use the Field mappings section in its configuration view.

​
Default mappings

When you connect a Salesforce org, Spotzee sets up these mappings automatically: You can change defaults or add more rows. Defaults are a starting point, not a constraint.

​
Add a mapping

1

Open Field mappings

In the integration’s configuration view, scroll to the Field mappings section.
2

Pick a Salesforce field

The Salesforce field dropdown lists every field on the objects you’re syncing. Standard fields appear first, custom fields after.
3

Pick or create a Spotzee property

The Spotzee property dropdown shows existing properties. Pick one to map onto an existing property, or type a new name and pick Create “your_property_name” to create one on the fly.
4

Add more rows or save

Choose Add mapping to add another row, or save when done.
New properties created from the mapping screen default to string type. Adjust the type later under Settings → Data Schema if you need numeric, date, or boolean handling.

​
Type compatibility

Spotzee converts Salesforce types automatically for the common cases: If a field’s data doesn’t match the destination property’s type (for example, mapping a Salesforce text field onto a numeric Spotzee property), the value is dropped and the row appears in the integration logs as a type-mismatch warning.

​
Sync email opt-out automatically

Salesforce tracks email opt-out via the HasOptedOutOfEmail boolean field on Lead and Contact records. Mapping that field into Spotzee keeps your unsubscribe state aligned across both systems.
1

Add the opt-out mapping

In Field mappings, add a row with:
  • Salesforce field: HasOptedOutOfEmail.
  • Spotzee property: unsubscribed (or your preferred boolean opt-out property).
2

Save

Save. The next sync reads the opt-out field and writes the corresponding boolean onto the user.
How it lands in Spotzee:
  • True in Salesforce sets the user as unsubscribed for the email subscription tied to the property.
  • False keeps them subscribed.
Spotzee re-checks the field on every incremental sync, so opt-outs that happen in Salesforce between Spotzee runs catch up automatically.

​
One-way sync caveat

The opt-out sync only flows from Salesforce into Spotzee. If a user unsubscribes via a Spotzee email link or preference centre, that change stays in Spotzee and isn’t pushed back to Salesforce. To keep both systems aligned, either:
  • Treat Salesforce as the source of truth and only opt users out from Salesforce.
  • Build a manual reconciliation to update Salesforce when a Spotzee unsubscribe happens (separate webhook integration or scheduled job, neither shipped by Spotzee).

​
CampaignMember and opt-out

The HasOptedOutOfEmail field exists on Lead and Contact, not on CampaignMember. If you sync CampaignMember, opt-out has to be mapped from the parent Lead or Contact record. Salesforce exposes the parent record’s opt-out value through campaign-member relationship traversal in the field selector; pick that traversal target when adding the mapping row.

​
Test a mapping

After saving a new mapping, run a manual sync from the integration’s overview page. Open one of the imported users in Spotzee and verify the mapped fields show the values you expect from Salesforce. Adjust if anything looks off.

​
Next steps

Operations

Manual sync, frequency, and monitoring health.

Define custom user attributes

Set the type and visibility on the new properties you just created.

Subscription preferences

Connect the opt-out field to an actual subscription type.

Salesforce overview

What the integration does and what data flows.