Salesforce Marketing Cloud Data Extension

Our Salesforce Marketing Cloud integration creates a mirror dataset of all events your account has in our system, inside of a data extension.

Each field in our system becomes a column inside of the data extension and each row represents an event.

Initial Setup

Before Rebel can export events into a SFMC Data Extension, you must create what SFMC calls a package, that allows third parties limited access to your account.

  1. Login to SFMC, find the menu in the upper right-hand corner, and navigate
    to {USER_NAME}! -> SETTINGS -> Administration.
  1. From there, continue on to Account -> Installed Packages.
  1. Create the new package with the New button in the upper right of the page. You can use whatever name you'd like (e.g. Rebel) and an optional description.
  1. Add a component with type API Integration

  2. Give the component Read and Write access to Data Extensions under
    the DATA header

  1. After you've saved the component to the package, you should see its credentials. We need CLIENT ID, CLIENT SECRET, and the first part of the url in your browser's location (s followed by a number). You can also optionally choose the name of the Data Extension we create, by default we write all events into a Data Extension named Rebelmail.

All Events

All events have values for the following columns:

Columns Possible Values
time 2018-05-29T20:59:35.603Z
eventId String - Used as internal identifier in Rebel's platform
campaignId String - Used as internal identifier in Rebel's platform
campaignName String - Set by the user
to String - Set by the user to identify email recipient
type String - One of open, variant, interaction, submit

Open Events

Do not have any values in additional columns.

Variant Events

Populate an additional value in the variant column.

Column Possible Values
variant String - One of interactive, limited

Interaction Events

Populate additional values in the interaction, interaction1, interaction2, interaction3, interaction4, interaction5 columns

The interaction string contains a pipe delimited string describing the full interaction. E.G. gallery||0||thumbnail||1 would represent a click on the first gallery's second thumbnail.

For convienence we also automatically delimit the string into columns for you. E.G. gallery||0||thumbnail||1 would populate as follows:

interaction1 interaction2 interaction3 interaction4 interaction5
gallery 0 thumbnail 1
Columns Possible Values
interaction String - Represents the full interaction
interactionN (1-5) Strings - Representing the parts of the interaction string corresponding with their number

Submit Events

Populate additional value in the submitPayload column.

Column Possible Values
submitPayload Object - Varies depending on the submitted values

Deprecated Columns

The click and duration columns are deprecated, but are kept in the integration to support legacy events.