Configuring integrations for a given scenario

  1. Home
  2. Configuring integrations for a given scenario

Configuring integrations ikn Marketing cloud require understanding your needs and selecting the best product.

Marketing Cloud Packages

  • A package contains a functionality ( small / big)
  • Install them by Setup -> Apps
  • installed packages must be licensed from parent BU to other BUs
  • Has component which performs the action
  • It is used to
    • add custom Journey Builder components
    • create API integrations
    • install custom apps

Components can be

  • API Integration Component – To integrate with 3rd party app by Marketing Cloud REST  / SOAP API
  • Marketing Cloud App Component – iFrame into Marketing Cloud
  • Journey Builder Activity Component – for journeys which starts a REST API call in a 3rd party app
  • Journey Builder Entry Source Component – For journeys coming from a REST API call from 3rd party app
  • Custom Content Block Component – TO have a different HTML  editor

Integrations types

  • Server-to-Server Integrations
    • uses Client Credentials Grant Type
    • has no end-user interaction or UI (user interface)
    • connect to REST / SOAP services of Marketing Cloud
    • 3-step process for authentication by using access token
  • Web and Public App Integration
    • Uses Authorization Code Grant Type
    • uses app’s permissions
    • integrate on behalf of an end user
    • public app do  not store a client secret
    • web app store a client secret
    • 6-step process for authentication by using access token

Marketing Cloud Connect

  • Available only in
    • Salesforce Unlimited / Enterprise / Performance Editions / Developer Edition Sandbox.   Agency / Core / Enterprise 2.0
  • It connects Marketing Cloud account with Sales / Service Cloud org

Subscriber key

  • a text field
  • Has value to identify a subscriber
  • Marketing Cloud Connect uses it
  • The Contact ID / Lead ID is converted into the 18-digit subscriber key

Reference: Salesforce

Menu