On this page: Find answers to frequently asked questions about Integrations in Adobe Journey Optimizer, covering configuration, authentication, supported channels and formats, permissions, and troubleshooting.
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 supported in Fragments.
Limitations
Outbound channels are supported (for example email, SMS, and push).
For API call responses, JSON and HTML are 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
To start using Integrations, users need to be granted the Manage AJO integration configuration and View AJO integration configuration permissions.
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.
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page answers frequently asked questions about Integrations in Adobe Journey Optimizer, covering configuration, authentication, supported channels and formats, API patterns, permissions, and troubleshooting.
Intents:
- Understand what Integrations do and who configures versus uses them
- Learn how administrators configure and marketers add an integration to message content
- Determine which channels, response formats, and API patterns are supported
- Find the permissions required to configure Integrations
- Troubleshoot a failing test connection or an integration missing from the marketer picker
Glossary:
- Integrations: Feature that connects external data sources so you can pull content and data from third-party systems into campaigns and journeys and personalize messages (product-specific)
- Add personalization: Action on a Text or HTML component that marketers use to open Integrations, choose an active integration, and map attributes (product-specific)
- Pills mode: Personalization editor mode used to map values to variables in the configuration, such as header or query parameters or path variables in the URL (product-specific)
- Retrieval APIs: APIs that target specific content, which are supported for this integration model (product-specific)
- Listing APIs: Broad list or pagination patterns, which are not supported for this integration model (product-specific)
Guardrails:
- Outbound channels are supported (for example email, SMS, and push).
- For API call responses, JSON and HTML are supported for field mapping; raw binary image output and formats that are not JSON are not available.
- Retrieval APIs that target specific content are supported; Listing APIs (broad list or pagination patterns) are not supported.
- To configure Integrations, users need the Manage AJO integration configuration and View AJO integration configuration permissions.
- Only active integrations appear when marketers open Integrations; the integration must be activated after a successful test.
- Supported authentication types: No Authentication, API key, Basic Auth, and OAuth 2.0.
- The Integrations feature is supported in Fragments.
Terminology:
- Canonical name: Integrations — Acronym: n/a — variants: external integrations, third-party integrations
- Synonyms: administrators “create and activate the technical configuration” = the setup marketers later select via “Add personalization”
- Do not confuse: “Integrations” (personalization fields in message content driven from APIs) ≠ “Sources” (Experience Platform data ingestion, such as batch ingestion and profile enrichment)
- Do not confuse: “Retrieval” APIs (supported) ≠ “Listing” APIs (not supported)
FAQ:
- Q: Which channels support Integrations? — Outbound channels (for example email, SMS, and push).
- Q: Which API response formats are supported? — JSON and HTML; raw binary image output and non-JSON formats are not available.
- Q: Which API patterns can I connect to? — Retrieval APIs that target specific content; Listing (broad list or pagination) APIs are not supported.
- Q: Can I use Integrations in reusable fragments? — Yes, the feature is supported in Fragments.
- Q: Do Integrations replace Experience Platform Sources? — No; Integrations drive personalization fields from APIs, while Sources handle data ingestion such as batch ingestion and profile enrichment.
- Q: Why do marketers not see my integration in the picker? — Integrations must be activated after a successful test; only active integrations appear.