SalesForce Marketing Cloud
Push profile data and segment membership into a Salesforce Marketing Cloud data extension.
The SalesForce Marketing Cloud connector writes your segment and the profile data behind it into a data extension in Marketing Cloud, where it can be queried, filtered and used to send communications.
Type
Server-side
Category
Identifiers sent
Profile data only - see What the connector can send
Authentication
OAuth 2.0 server-to-server, credentials shared with your Account Manager
Description
What is a Salesforce Marketing Cloud data extension?
A data extension is a table holding fields about your contacts. It can stand alone or be linked to other data extensions, and it is used to run queries, extract information and send communications to subsets of subscribers. Data extensions are available in both Contact Builder and Email Studio, and can be populated manually or through the Marketing Cloud API - which is what this connector uses.
Marketing Cloud has three kinds:
Standard
A customised set of fields.
Filtered
A subset of an existing data extension.
Random
Subscribers picked at random from a source data extension.
What you can do with this connector
Maintain a Marketing Cloud data extension from a mediarithmics segment, with membership expressed as a field on each row.
Send profile attributes alongside the membership flag, so Marketing Cloud can personalise on data held in the CDP.
What the connector can send
This connector sends only data held on the UserProfile object. That data must be present in your data model and indexed.
Three fields are always sent and must exist in the data extension, with these exact names and casing:
status
Boolean
Whether the user belongs to the mediarithmics segment.
segment_id
Text
The mediarithmics segment ID.
Any other UserProfile field can be added to the send. Name it in the data extension first, then give the exact name and casing to mediarithmics.
It is recommended to send at least one user identifier into the data extension and to reference that field as unique.
Connector setup
Prerequisites
A Salesforce Marketing Cloud account with administrator access.
A data extension created to receive the data, carrying the three mandatory fields above.
An installed API integration package, and API access generated from it.
Authentication
mediarithmics authenticates through OAuth 2.0 with access token provisioning for server-to-server integrations - the client credentials type. The API integration must include these authorisation scopes:
email_read(Permission ID 5)data_extensions_read(Permission ID 97)data_extensions_write(Permission ID 98)
Salesforce documents the steps in Install packages, API integration, Access token for server-to-server and REST permissions and scopes.
Set up the SalesForce Marketing Cloud connector
Create the data extension in Marketing Cloud.
Decide its creation method, external key, whether it is sendable and testable, and any campaign association. Set its data retention. Then define its fields.
Field options are SQL-like: Primary Key marks uniqueness - if several are selected, the combination of values is treated as unique; Nullable allows the field to be empty; Default Value fills the field when a record omits it.
Install a package at administrator account level.
This is what makes API integrations available. It also covers custom applications and Journey Builder components, which this connector does not use.
Generate API access on the integration package.
OAuth 2.0, server-to-server, with the three scopes listed above.
Send the configuration to your Account Manager.
The external key of the data extension, generated when it was created.
The Client ID and Client Secret from the API integration.
Your tenant subdomain - see Your subdomain and tenant-specific endpoints.
Select the SalesForce Marketing Cloud connector and fill in its configuration.
Name
The name of the feed as displayed in the platform.
Credential Name
Provided by your Account Manager.
Identifiers
The data to send. One or several compartments can be added. See Identifiers.
Email validation (optional)
One or several email validators.
Creating and activating the feed on a segment is covered in Send your first-party data to a destination.
Good to know
FAQ
Why is my send rejected by Salesforce?
The most common cause is segment_name: the data extension field is shorter than the mediarithmics segment name. Check the field length against the 255-character maximum mediarithmics allows.
Can I send data that is not on the user profile?
No. The connector sends UserProfile data only, and that data must be in your data model and indexed. UserAccount, UserEvent and UserChoice are not compatible.
Can I add my own fields to the data extension?
Yes. Create the field in the data extension, then give its exact name and casing to mediarithmics so the mapping can be configured.
Partner documentation
Salesforce Marketing Cloud documents its own platform at https://developer.salesforce.com/docs/marketing/marketing-cloud/overview. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.
Last updated
Was this helpful?