> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Field Event Salesforce Sync

> Mirror a field event to a Salesforce campaign so registrations and attendance reach your CRM.

Connect a field event to a Salesforce campaign and its members and statuses stay aligned in both systems. This is separate from your [platform sync](/product-docs/campaigns/field-events/platform-sync/overview), so you can sync to Salesforce whether or not the event is connected to Cvent, Luma, or Splash.

## Connect to Salesforce

**Prerequisites:**

* Salesforce is connected to your workspace. See [Salesforce Setup](/product-docs/sync/salesforce/setup/admin-user-setup).
* If you're linking an existing campaign, it isn't already linked to another Conversion campaign, webinar, or field event.

**Steps:**

1. Open the field event and go to the **Overview** tab.
2. In the **Integrations** section, click **Connect** on the **Salesforce campaign** card.
3. Choose to sync to a **new** Salesforce campaign or an **existing** one, then pick the campaign if you chose existing.
4. Click **Confirm and sync**.

Creating a new campaign runs in the background, so the card shows **Connecting** for a moment and updates on its own. Once connected, **View in Salesforce** opens the campaign in your org.

<Warning>
  A Salesforce connection can't be changed or removed, and a Salesforce campaign can be linked to only one Conversion campaign, webinar, or field event.
</Warning>

## Syncing to a new campaign

Conversion creates a Salesforce campaign named after the field event, sets its **Type** to the name of your field event type (for example **Conference** or **Tradeshow**), adds every status from the type with your [success statuses](/product-docs/campaigns/members#success-statuses) marked as responded, and syncs across any members already on the event.

Only the name, type, and statuses are set on the new campaign. Fill in the campaign's dates and description in Salesforce if you need them there.

<Info>
  Salesforce's campaign **Type** is a picklist. If your org restricts it to a fixed list of values and your field event type's name isn't one of them, Salesforce rejects the campaign and the sync log records why. Rename the type in Conversion to match a permitted value, or add the value in Salesforce.
</Info>

## Linking an existing campaign

Linking runs a two-way sync of the members, following the [shared sync rules](/product-docs/campaigns/salesforce-sync#existing-conversion-campaign-synced-to-an-existing-salesforce-campaign). Members whose Salesforce status doesn't match one of the field event type's statuses are set to the type's first status.

<Tip>
  Add your field event type's statuses to the Salesforce campaign before linking so members land on the right status instead of falling back to the default.
</Tip>

## Ongoing sync

Once connected, statuses sync both ways for the life of the event, following the [shared status sync behavior](/product-docs/campaigns/salesforce-sync#status-sync-behavior).

Everything your event platform reports reaches Salesforce without anyone touching it. Someone who RSVPs on Splash becomes **Registered** in Conversion and on the Salesforce campaign member, and the move to **Attended** at check-in or **No Show** after the event is pushed out the same way. Changes your sales team makes in Salesforce flow back into Conversion.

Two things to know about the Salesforce side of a platform-connected event:

* **Salesforce writes statuses by name.** A status change made in Salesforce sets that status in Conversion directly, with none of the platform-sync rules applied. If it disagrees with what the platform reports, the platform's next sync puts its own value back.
* **Salesforce doesn't register anyone on the platform.** Marking someone **Registered** in Salesforce updates Conversion, and nothing is sent to Cvent, Luma, or Splash.