Salesforce OAuth 2.0 Connection for Marketing Cloud Engagement

Create the Connection

1. On the Data Manager Connections tab, click New Connection.
2. Click the name of the connector, and click Next.
3. Enter the connector settings.
4. To validate your settings and attempt to connect to the source, click Save & Test. If the connection fails, CRM Analytics shows possible reasons.

Marketing Cloud Engagement packages using a tenant-specific endpoint and OAuth 2.0 authentication are required for this connector. Package permissions must be at least:

• Read for “List and Subscribers”
• Read and write for “Data Extensions”
• Read and write for “Marketing Cloud Connect”
• Read for “Accounts”
• Read for “Users”

The security settings of the user that you use to connect determine the objects and fields available for sync.

All settings require a value, unless otherwise indicated.

Filter Data Synced to CRM Analytics

Exclude unnecessary or sensitive data from syncing to CRM Analytics with data sync filters. Filters run on the source object and speed up data sync by pulling only the data you need into CRM Analytics.

Note If you might use excluded data in the future, use a recipe filter to limit the data written to a dataset instead of a data sync filter.

1. From Data Manager, click the Connections tab.
2. Select the connection associated with the object to filter.
3. Click the name of the object to filter.
4. Click Data Sync Filter.
5. Enter the filter.
6. Click Save.

For the Marketing Cloud Engagement OAuth 2.0 Connector, enter a filter in SQL syntax equivalent to the Filterpart help. Filters can include boolean statements (AND, OR), numerical comparisons (>, >=, <, <=), equality (=, !=), and LIKE operators. Filtering is only supported for SOAP objects.

For a simple example, return entries where the Name field is Marc with the filter Name="Marc". Use this type of simple filter for optimal performance and query response. For more complex situations, combine two filter parts with an AND or an OR logical operator, for example (Name="Marc") AND (Age=57). You can also nest filters in parentheses, for example (Name="Marc") AND ((Age=57) OR (Age=37)).

To filter with dates, store date data in a Supported format. For example, column_date > '2010-12-31T22:00:00.000Z'

Salesforce Marketing Cloud Engagement OAuth 2.0 Connector Considerations

Keep these behaviors in mind when working with the Salesforce Marketing Cloud Engagement connector.

• Connected object names must start with a letter and contain only letters, digits, or underscores. Object names can’t end with an underscore.
• Only field names with combinations of alphanumeric, dot, underscore, or dash characters are supported. If a connector includes field names that contain other characters, such as spaces or brackets, the sync fails.
• The connector can sync up to 20 million rows or 10 GB per object, whichever limit is reached first.
• Standard Marketing Cloud Engagement and custom objects are supported, but may be not be available due to your package access or permissions configuration.
  

  Note The JourneyActivities object is not available.
• Don’t overwrite Data Extensions during data sync. Marketing Cloud Engagement SOAP API can return incomplete data from a Data Extension read operation if that Data Extension is being concurrently overwritten.
• This connector can't read hexadecimal character data (such as 0x1B) stored in Marketing Cloud Engagement and will generate an HTTP 302 error. To bring in the column, remove all hexadecimal values.
• When viewing Marketing Cloud Engagement Data Extensions, names have the text “Ungrouped__”, with a double underscore, added to the beginning. For example, data extension MC_East will appear as Ungrouped__MC_East.