Set Up a Marketing Cloud Developer Environment

Learning Objectives

• Explain different types of integration components.
• Create an enhanced installed package in your Marketing Cloud Engagement account.
• Obtain credentials for API integration authentication.

Introduction

• The module guides users through setting up a developer environment in Marketing Cloud Engagement.
• The process culminates in a simple project to test the setup.

Creating a Package

• Installed Package: A container with components that manage custom functionality.
• Purpose of Packages: Used to create API integrations, install custom apps, and add custom Journey Builder components.
• Examples of Package Components:
  • API Integration: For third-party application integration needing REST API access.
  • Marketing Cloud Engagement App: Apps to iFrame into Marketing Cloud Engagement.
  • Custom Content Block: Use alternative HTML editors like QuillJS.
  • Journey Builder Activity: Custom activities that trigger REST API requests.
  • Journey Builder Entry Source: Custom entry sources for journeys.

Steps to Create a Package:

1. Navigate to Setup in Marketing Cloud Engagement.
2. Expand Apps under Platform Tools, click on Installed Packages.
3. Click New, name, and describe the package.
4. Save and view package details.
5. Click Add Component under Components, select API Integration.

Integration Type

• Types of Integrations:
  • Web App: API requests in end-user context; uses Authorization Code.
  • Public App: For single-page or mobile apps; uses Authorization Code.
  • Server-to-Server: No end-user context; uses Client Credentials.
• For Testing: Select Server-to-Server.

Setting Properties:

• Enable scope for platform functions.
• Ensure Write access is enabled for Audiences and List and Subscribers under Contacts.
• Save the component.

Get Credentials

• After creating a package, locate client ID and client secret under component details for use in integrations.

Access Tokens for Server-to-Server Integrations:

1. Use client ID and secret to request an access token from Marketing Cloud Engagement's authorization server.
2. The server returns the access token.
3. Use the access token to access Marketing Cloud Engagement resources.

Requesting Access Token:

• Construct endpoint using v2/token.
• Provide client ID and secret.
• Access Token Lifetime: 20 minutes.
• Example Request: POST /v2/token Content-Type: application/json { "grant_type": "client_credentials", "client_id": "CLIENT_ID", "client_secret": "CLIENT_SECRET", "scope": "list_and_subscribers_write audiences_write", "account_id": "12345" }
• Example Response: Access token with expiration and URLs for REST and SOAP services.

Resources

• Links to Salesforce Developer documentation and resources for further learning.