FanThreeSixty Audience Export to Salesforce Guide

Overview

When you export an audience from FanThreeSixty to Salesforce using the FTS Integration, fans are created or updated as Contacts in Salesforce. This article explains what data is sent, how fields are mapped, and what limitations apply.

How fans are exported

• Each fan in your exported audience is sent to Salesforce as a Contact record.

• Email is used for de-duplication and updates:

  • If a Contact with the same email already exists in Salesforce, supported fields are updated on that record.

  • If no Contact with that email exists, a new Contact is created.

Default field mappings

By default, FanThreeSixty exports the following fan fields to Salesforce Contact fields:

Fan record → Salesforce Contact field

• First Name → FirstName

• Last Name → LastName

• Email 1 → Email (used for de-duplication / updates)

• Phone 1 → Phone

• Postal Code 1 → MailingPostalCode

• Ticketing ID → Ticketing_ID__c

• Audience Name → Audience_Name__c

• Mobile User → IsMobileUser__c (checkbox)

• Identified On → Originally_Identified__c

• Customer Tags → Tags__c (Picklist, Multi-Select)

• Total Membership Points → Total_Membership_Points__c (Number)

• Membership Points (this year) → Membership_Points_this_year__c (Number)

• Distance Away → Distance_Away__c (Number, in miles)

Updating field mappings

You can change which fields are mapped between FanThreeSixty and Salesforce.

1. In the FanThreeSixty platform, go to Settings → Integrations → Salesforce.

2. Click on your Salesforce integration connection.

3. Update the field mappings as needed and save.

Important: use Salesforce Field Name, not Field Label

When choosing which Salesforce field to map to, always enter the Field Name (API name), not the user-friendly Field Label you see on Salesforce screens.

For example:

• Originally_Identified__c instead of Originally Identified

If you are unsure of the Field Name, your Salesforce administrator can help you find it.

Limitations & special behavior

Creation date cannot be changed

• The integration cannot change the standard Salesforce record Created Date.

• The FanThreeSixty Identified On value represents when a fan was first identified in FanThreeSixty.

• By default, Identified On is synced into a custom field like Originally_Identified__c on the Contact.

Customer Tags (multi-select picklist)

• Customer Tags can be synced to a Salesforce Picklist (Multi-Select) field (e.g. Tags__c).

• The integration will automatically create a unique picklist value for each tag it sends.

Recommended Salesforce field configuration (by your Salesforce admin):

• Values: set to Enter values (so values can be created as needed).

• Restrict picklist: not checked.

• This allows new tag values from FanThreeSixty to appear in Salesforce without additional configuration.

Technical details (for reference)

• Exports are generated as CSV files and uploaded to Salesforce in bulk.