ht
Documentation
WelcomeConcepts

Get Started

OverviewCreate a sourceCreate a modelCreate a destinationCreate a sync

Destinations

AcousticActiveCampaignAirtableAmplitudeAsanaAuth0Bing AdsBrazeChurnzeroClientSuccessCloseCustom DestinationCustomer.ioFacebook Conversions APIFacebook Custom AudiencesFacebook Offline Conversions APIFacebook Product CatalogFreshdeskFrontGainsightGainsight PXGoogle AdsGoogle Campaign ManagerGoogle SheetsHeapHubspotIntercomIterableJiraKlaviyoMailchimpMarketoMixpanelMoengageMongoDBmParticleNetsuiteNotionOneSignalOrbitOutreachPartnerstackPendoPipedrivePostgreSQLQualtricsReply.ioRoktRudderstackS3SailthruSalesforceSalesforce Marketing CloudSalesforce Marketing Cloud File DropSalesloftSegmentSendGridSFTPSlackSnapchatStripeTheTradeDesk PostbackTiktokTotangoUserflowVeroWebhookZendesk
Documentation/Destinations/Sfmc file drop
ht
Documentation

Salesforce Marketing Cloud File Drop

Table of Contents
Overview
Marketing Cloud by Salesforce is a platform that helps marketers engage with their audience at scale. The platform provides digital marketing automation, analytics, and lead management for B2B and B2C companies.

Overview

This destination allows you to pull results from your model and securely send a CSV file to a Salesforce Marketing Cloud FTP server.

Initial Setup

To get started, you will need your FTP URL, username, and credentials. You can create an FTP user in the Salesforce Marketing Cloud console under Settings > Administration > Data Management > FTP Accounts.Port 22 will always be used.

Supported Authentication Methods

We support three authentication methods:
  • Username + password
  • Username + SSH private key
  • Username + SSH private key + passphrase
We support two formats for the SSH private key:
  • OpenSSH
  • RSA
Provide the full private key for the user, including the header and footer.For example:
-----BEGIN OPENSSH PRIVATE KEY-----
<private key body>
<private key body>
<private key body>
-----END OPENSSH PRIVATE KEY-----

Syncing to SFTP Server

This destination ignores the concept of additions, changes, removals and will send the full results of your model. For example, if your model has 1,000 records, your csv results file will be 1,000 records.

File Name

The file name field will allow you to specify which directory and the name of the file that you want to name your results. The parent directory for the file must exist. Import/ will be added to the beginning of the given path. For example, with the configuration in the screenshot below, the file results.csv will be written to path Import/results.csv.You can also timestamp variables in the file name, surrounding each with {}. We currently support these timestamp variables: YYYY, MM, DD, HH, mm. All dates and times will be UTC.For example: {YYYY}-{MM}-{DD}-{HH}-{mm}-result.csv.

Columns to Sync

For this destination, we give you the ability to export all columns as they are represented in your model.If you need remap the fields that you're exporting, maybe because you don't want to alter your model, you can manually map fields. Only the fields that you map will be exported in this instance. In this example, we're just exporting id, email and location. These fields are mapped to the new fields in the csv as user_id, user_email and user_location respectfully. All other columns from your results are ignored.

Format and Encoding

The synced file will include a CSV header.By default, the file will be saved in ASCII encoding. If there are any non-ASCII characters in your results, the file will be saved with utf-8 encoding.The file will not contain a Byte Order Mark (BOM).

Other Considerations

This destination will not respect any sorting that you have in your model. It will export the target file sorted by ID.You will need to ensure that the file that you transmit is processed from the folder before the next sync runs, or else it will be overwritten with the next sync that uses the same filename.