Salesforce Marketing Cloud integration with Amperity

Q: Can Amperity use SFTP without managing the data extension?

Yes. With SFTP-only delivery, your team configures the data extension, import definition, and process that loads the file. Salesforce defines ImportDefinition as a reusable set of import options; a file delivery alone does not complete that import.

Q: Is a data extension key the same as a Contact Key?

No. A data extension CustomerKey identifies the object. A Contact Key identifies a person in Engagement, while SubscriberKey identifies a subscriber. Plan the person identifier consistently across channels; do not substitute the data extension object key.

Q: Does updating a data extension change consent or unsubscribe status?

Do not use a data extension update as a consent change. Filter audiences using the permission data available in Amperity and retain Salesforce sending controls. Manage SubscriberStatus, including Unsubscribed and Held, through the appropriate Salesforce subscription workflow.

Q: Does removing an audience row delete the Salesforce contact?

Manage Salesforce contact deletion through a separate workflow. Replacing data extension contents controls the audience rows; verify subscriber and contact removal separately when processing a privacy request.

Q: How often can Salesforce Marketing Cloud audiences refresh?

Configure campaign delivery for your workflow rather than assuming continuous updates. The batch connector does not promise real-time synchronization. Inbound files can run on a configured courier-group schedule; freshness also depends on when Salesforce exports them.

Send audiences built from trusted customer context to Salesforce Marketing Cloud Engagement data extensions through CSV transfer and API-managed imports. Amperity also supports a separate SFTP source for exported email campaign data.

Get a demo See the SFMC docs

CSV transfer | Data extensions | Separate SFTP source

Target offers using customer attributes available in Amperity.

Carry established subscriber identifiers into audience exports.

Refresh data extension audiences for planned campaigns.

Bring exported email campaign data back into customer context.

How Amperity and Salesforce Marketing Cloud connect

Define the audience. Choose a segment or query and select the attributes required by your destination schema.
Deliver the file. The standard batch destination combines SFTP transfer with API-managed data extensions; SFTP-only delivery requires your own import workflow.
Validate before activation. Send a sample, inspect the destination records, and confirm subscriber mapping before sending the full audience.

Choose a destination mode. Configure the inbound source independently.

What the Salesforce Marketing Cloud integration supports

Capability	Supported behavior
Outbound method	CSV transfer; API-managed data extensions or SFTP-only delivery.
Inbound method	Separate SFTP source pulls exported email campaign files.
Destination objects	Data extensions with fields matching the export schema.
Row updates	Append data on: upsert. Off: replace extension contents.
Refresh	Configured batch delivery and inbound schedules; no fixed freshness guarantee.

Map data extension objects and subscriber keys

Salesforce object or field	Amperity mapping	References
DataExtension	Selected contact columns become extension fields.	Amperity destination; Salesforce DataExtension
DataExtensionObject	An exported contact record corresponds to a data extension row.	Amperity audiences; Salesforce DataExtensionObject
SubscriberKey	Preserve the existing subscriber_key through inbound feeds and outbound attributes.	Amperity source; Salesforce Subscriber
ImportDefinition	For SFTP-only delivery, configure the destination and field mappings in Salesforce.	Amperity destination; Salesforce ImportDefinition

Use customer context to choose more relevant audiences

Tailor offers to the relationship you already have

Build an audience from the purchase history and customer attributes available in Amperity, then choose the contact fields your Salesforce Marketing Cloud data extension needs. For example, separate repeat purchasers from customers who have purchased once and prepare a different offer for each group. Review the audience and exclusions in Amperity before export, then use the resulting data extension in your Salesforce Marketing Cloud workflow.

Use campaign exports to inform the next audience

Bring exported email campaign data into Amperity through the separate Salesforce Marketing Cloud SFTP source. Preserve the subscriber key in the feed and make it available for subsequent audience exports, so your team can relate campaign records to customer context. Use the imported fields that your export actually contains to inform audience selection, then validate a sample before activation. This workflow depends on the files you prepare and the schedule you configure.

Prepare the Salesforce Marketing Cloud connection

For the standard destination, supply SFTP credentials and an installed-package API integration. Configure OAuth scopes and target-business-unit access. Amperity specifies Data Extensions Read/Write and Automations Read/Write/Execute permissions.

Align the primary key and subscriber field: subscriber_key with Subscriber Key, or an email variant with Email Address. Choose Append data deliberately: enabled upserts rows; disabled replaces data extension contents.

Review the Salesforce Marketing Cloud setup requirements

Salesforce Marketing Cloud integration FAQs

Can Amperity use SFTP without managing the data extension?

Is a data extension key the same as a Contact Key?

Does updating a data extension change consent or unsubscribe status?

Does removing an audience row delete the Salesforce contact?

How often can Salesforce Marketing Cloud audiences refresh?

Put customer context to work in your next campaign

See how Amperity can help your team choose audiences and prepare the customer attributes your Salesforce Marketing Cloud workflows need.

Get a demo