Table of content:
Below are frequently asked questions about Integrations in Adobe Journey Optimizer.
Get started
It connects external data sources into Journey Optimizer so you can pull content and data from third party systems into your campaigns and journeys, and personalize messages using that data.
Administrators create and activate the technical configuration (Configurations > Integrations > Manage > Create Integration). Marketers use Add personalization in Text or HTML components, open Integrations, choose an active integration, and map attributes.
Go to the Configurations section in the left menu, open Manage from the Integrations card, then select Create Integration.
Examples include rewards points from loyalty systems, product price information, recommendations from recommendation engines, and logistics updates such as delivery status.
Configuration
You provide a name and description, an API endpoint URL (optionally with path variables), path template values, GET or POST, optional headers and query parameters, an authentication method, policy settings (such as timeout and optional cache or retry), a sample JSON response to map fields, then run Send test connection and Activate when valid.
These authentication types are available: No Authentication, API key, Basic Auth, and OAuth 2.0 (with payload configuration for OAuth where applicable).
Paste a sample JSON response so the system can detect data types and you can choose which fields are exposed for personalization in messages. You can limit which fields are available to marketers during authoring.
In campaign or journey content, use Add personalization on a Text or HTML component, go to Integrations, select an integration, and save. With Pills mode in the personalization editor, you can map values to variables in the configuration (such as header or query parameters, or path variables in the URL).
Capabilities and use cases
Yes. The feature is available for both journeys and campaigns for outbound channels (for example email, SMS, and push), within current product limits.
The Integrations feature is not supported in Fragments. Use integrations in campaign and journey message content where the product supports them.
Limitations
Outbound channels are supported (for example email, SMS, and push).
For API call responses, JSON is supported for field mapping. Raw binary image output and formats that are not JSON are not available for this workflow.
Retrieval APIs that target specific content are supported. Listing APIs (broad list or pagination patterns) are not supported for this integration model.
Permissions and related capabilities
Configuration is an administrator workflow under Configurations > Integrations. Exact permission names depend on your organization’s Admin Console and Journey Optimizer product profiles. Confirm with your admin or Adobe representative.
No. Integrations are for personalization fields in message content that you drive from APIs. Sources and other data ingestion capabilities serve different purposes (for example batch data ingestion and profile enrichment). Use each capability for its intended scope.
Troubleshooting
Verify the endpoint URL, HTTP method, path templates, headers and query parameters, authentication, and policy timeout. Use Send test connection after adjustments. For payload issues, ensure the sample reflects valid JSON and that selected fields match what the API returns.
Integrations must be activated after a successful test. Only active integrations appear when marketers open Integrations. If the integration is still draft or inactive, complete activation first.
Third party vendors
You can integrate with any third party platform that exposes a compatible API endpoint. Illustrative vendor patterns and configuration examples can help you model compatible APIs. Responsibility for securing endpoints lies with the third party platform and your team.