SFMC Journey Builder AMP Integrations for Text: Access and Permissions

UI Access

To support onboarding configuration and testing of AMP integration, access to the following modules within Salesforce Marketing Cloud is required:

• Journey Builder

  • API-triggered journeys used by Signals

  • Journey Entry Events configuration

• Content Builder

  • SMS Message template

  • SMS Message Content blocks 

• Contact Builder

  • Sendable Data Extensions

  • Contact Data modeling to support cross-campaign prioritization 

• Mobile Connect

  • Manage Profiles and Permission Sets

  • View All Users

  • View Setup and Configuration system 

API Permissions

AMP integration requires a Server-to-Server Installed Package in Salesforce Marketing Cloud with the following API permissions (at minimum): 

• Access: Offline Access

  • Access token and refresh token

• Journeys (Interactions): Read/Write/Execute/Activate/Stop/Pause/Resume

  • Trigger Journey Entry Events via the /interaction/v1/events endpoint

  • Power API-driven journey entry for Signals campaigns

• Audiences: Read 

  • Lookup contacts via /contacts/v1/attributes/search 

  • Retrieve ContactKey for signals payload 

• Saved Content: Read/Write 

  • Create and validate SMS Message content blocks and templates 

• Data Extensions: Read/Write 

  • Create and Validate Sendable Data Extensions 

  • Validate event data for journey processing

  • Retrieve user on Data Extension for URL ID Lookup (if applicable)

• Tracking Events: Read/Write

  • Required for API-triggered Journeys 

• Lists and Subscribers: Read/Write 

  • Support testing workflows (e.g., adding test subscribers)

  • Retrieve Subscriber for URL ID Lookup 

API Credentials

From the Installed Package in Salesforce Marketing Cloud, securely provide the following:

• Client ID

• Client Secret

• Tenant-Specific Endpoint (Tenant URI)