What does the baseUrl represent in a Marketing Cloud integration?

What does the baseUrl represent in a Marketing Cloud integration?

• A. The endpoint used for authentication
• B. The base URL for your application; Journey Builder loads assets relative to this endpoint
• C. The data export endpoint
• D. The UI path for the custom activity

Answer: (B)

BaseUrl is the root address of the external application you connect with Marketing Cloud. For Journey Builder custom activities, you host the activity’s UI and its server endpoints at a publicly accessible URL, and Marketing Cloud uses this base URL to load the UI assets and to call the activity’s endpoints. In practice, if your app is at https://myapp.example.com, that becomes the baseUrl, and Journey Builder will fetch UI resources and send requests to paths relative to that root (for example, resources under https://myapp.example.com and API calls like https://myapp.example.com/api/…). This isn’t specifically an authentication endpoint or a data export endpoint, and the UI path is simply a resource under the base URL rather than the base URL itself.

BaseUrl is the root address of the external application you connect with Marketing Cloud. For Journey Builder custom activities, you host the activity’s UI and its server endpoints at a publicly accessible URL, and Marketing Cloud uses this base URL to load the UI assets and to call the activity’s endpoints. In practice, if your app is at https://myapp.example.com, that becomes the baseUrl, and Journey Builder will fetch UI resources and send requests to paths relative to that root (for example, resources under https://myapp.example.com and API calls like https://myapp.example.com/api/…). This isn’t specifically an authentication endpoint or a data export endpoint, and the UI path is simply a resource under the base URL rather than the base URL itself.