Skip to main content
Salesforce Marketing Cloud

How to Integrate Salesforce Marketing Cloud with WinRed

Updated over a year ago

WinRed can integrate with and send over realtime information to your salesforce marketing cloud CRM. Before this integration can be utilized, please reach out to the WinRed Support team, so this can be enabled for you.


You can find a list of all the data extensions sent to Salesforce Marketing Cloud here.


Table of Contents

Set Up in Salesforce Marketing Cloud

These steps need to be completed before a Salesforce Marketing Cloud integration is enabled in WinRed. We recommend doing this 24 hours in advance.

  1. Go to Your User -> Setup -> Platform Tools -> Apps -> Installed Packages

  2. Create a New Package by clicking "New"

    1. Enter a name (we suggest something like "WinRed")

    2. Description (this is optional and add whatever will be helpful to you)

    3. Click "Save"

  3. Add Component

    1. Select "API Integration"

    2. Click "Next"

  4. Choose Your Integration Type

    1. Select "Server-to-Server"

    2. Click "Next"

  5. Set Server-to-Server Properties (Scope)

    1. Automation -> Automations. Enable the following

      1. Read

      2. Write

      3. Execute

    2. Automation -> Journeys. Enable the following:

      1. Read

      2. Write

      3. Execute

      4. Active/Stop/Pause/Resume/Send/Schedule

      5. Delete

    3. Data -> Data Extensions and enable the following:

      1. Read

      2. Write

    4. Click "Save"

  6. Click on the "Access" tab within the Package

  7. Click into EACH Business Unit and click the toggle "Enable Integration for [Business Unit Name]"

    1. Click the "Save" button

After Step 5, the package should look like this:

Image

After Step 7, each Business Unit should have the package enabled:

Image

Set up in WinRed

First, sign in to WinRed and navigate the Utilities -> Integrations tab. There click the green Add Integration button, then select Salesforce Marketing Cloud.

The menu pictured below will then appear. Here, you can input the Integration Name and any associated notes.

Note: Event level data will be fired in realtime, but the Automation Studio will run "Hourly"

In the next section, you will need to input your Client ID, Client Secret, Business Unit MID, and Authentication Base URI. These are all required fields and can be obtained by logging into your Salesforce Account and populating the fields with the corresponding values.

The following section asks questions that allow you to customize your Salesforce Marketing Cloud integration.

  • If the Email Data Extension is enabled, then it will create two Data Extensions in Salesforce Marketing Cloud:

    • An event level Data Extension (i.e. every Donation and Lead)

    • A results Data Extension (i.e. One row for every Email Address)

  • If the Mobile Data Extension is enabled, then it will create two Data Extensions in Salesforce Marketing Cloud:

    • An event level Data Extension (i.e. every Donation and Lead)

    • A results Data Extension (i.e. One row for every Mobile)



The selected Data Extensions will then be built under the specific tab. After a few minutes, reload the integration and see that the Data Extensions have a Status of OK.

You can view the Data Extensions and the Automation Studio in Salesforce.

Image
Image

Once completed, toggle the Integration as Active and click the Save button.

Please Note: You can request that WinRed backfill the Email and/or Mobile Data Extension!

Important Notes

  • Renaming any of the Data Extension, Fields, Automation Studio or Automation Studio queries will likely cause many things to break. It is strongly advised not to make any changes.

  • If the "Email Data Extension" is enabled, then it will create two Data Extensions in Salesforce Marketing Cloud:

    • An event level Data Extension (ie every Donation and Lead)

    • A results Data Extension (ie One row for every Email Address)

  • If the "Mobile Data Extension" is enabled, then it will create two Data Extensions in Salesforce Marketing Cloud:

    • An event level Data Extension (ie every Donation and Lead)

    • A results Data Extension (ie One row for every Mobile)

  • For Data to go into the "Mobile Data Extension" there must be an "Email Address" on the event level data

  • Each organization can have multiple Salesforce Marketing Cloud integrations

    • If an organization has more than one Salesforce Marketing Cloud integration, then an ID will be added to the Data Extension and Automation Studio names

  • A Business Unit can have more than one integration

  • None of the Data Extensions are in the Transactional template

    • Organizations can still send transactions receipts for petitions when they set up their Journey Builder

  • Sendable Data Extensions

    • Email Results: "email" relates to subscriber on "Subscriber Key"

    • Mobile Results: "email_most_recent" relates to subscriber on "Subscriber Key"

    • Petition: "email" relates to subscriber on "Subscriber Key"

  • Marketing Cloud is in CST but does not observe Daylight Savings

  • Most Recent fields are Most Recent Non Null

  • First fields are First Non Null

  • Agency & Revv Share accounts will not receive donation data for some orgs

    • There is a known bug where webhooks are not working as well

  • Volunteer Upsell opt-in events will not appear in the Mobile table on Salesforce, due to Mobile # not being passed

    • This applies to both the Mobile Event and Mobile Results tables

  • Volunteer opt-in will have Address, City and State all fill into the "address" field

  • If an individual record fails to import into SFMC during the backfill or during the live sending, then we will re-send the record with limited fields:

    • email/mobile

    • record_type

    • record_id

    • donation_amount

    • created_at

    • product_name

    • lead_type

    • interval

    • recurrence_ordinal

    • part_of_subscription

    • one_click_eligible

    • one_click_donated

    • upsell_page_type

    • merchandise_order_uid

  • Salesforce has an email validation on the API import

  • There is no timeout limit on Automation Studio, but there is a 30 minute timeout for each Activity

  • The 30 minute timeout per Activity can be extended if Salesforce thinks the SQL is optimized

  • There can be performance degradation with Data Extensions of more than 1 million records

  • "language" is not going to have a value for any Data Extension for now

Questions?

If you have questions or are unsure about any of these steps, please reach out to our support team by clicking the red chat box a the bottom right corner of your screen.

Did this answer your question?