Adobe Experience Platform
Server-side data ingestion into Adobe Experience Platform (AEP) via the Streaming Ingestion API for real-time profile enrichment and audience activation.
Prerequisites
Before configuring Adobe Experience Platform in Datafly Signal, you need an AEP account with a schema, dataset, streaming connection, and API credentials.
Step 1: Access Adobe Experience Platform
- Go to experience.adobe.com and sign in with your Adobe ID.
- Click the app switcher (nine-dot menu) and select Experience Platform.
- If you do not have access, contact your Adobe account administrator to provision AEP for your organization.
Step 2: Create an XDM Schema
- In AEP, navigate to Schemas in the left sidebar.
- Click Create schema and select XDM ExperienceEvent (for time-series event data).
- Give the schema a name (e.g. “Datafly Signal Events”).
- Add field groups relevant to your use case (e.g. Commerce Details, Web Details).
- Click Save and copy the Schema ID from the schema details panel.
XDM ExperienceEvent is the correct schema class for event data from Datafly Signal. Use XDM Individual Profile only if you are sending profile updates rather than events.
Step 3: Create a Dataset
- Navigate to Datasets in the left sidebar.
- Click Create dataset from schema.
- Select the schema you created in Step 2.
- Give the dataset a name (e.g. “Datafly Signal Events Dataset”).
- Click Finish and copy the Dataset ID from the dataset details page.
Ensure the dataset is enabled for Profile if you want incoming events to contribute to Real-Time Customer Profiles. This is configured on the dataset details page.
Step 4: Set Up a Streaming Connection
- Navigate to Sources in the left sidebar.
- Find HTTP API under the Streaming category.
- Click Add data and then New account.
- Enter a name for the connection (e.g. “Datafly Signal Ingest”).
- Optionally enable XDM-compatible data and authentication.
- Click Connect to source and copy the Connection ID and Streaming endpoint URL.
Step 5: Find Your Organization ID
- Go to the Adobe Admin Console.
- Click Organization in the top navigation.
- Your Organization ID is displayed in the format
1234567890ABCDEF@AdobeOrg. - Copy this value.
Step 6: Generate an Access Token
- Go to the Adobe Developer Console.
- Create a new project or open an existing one.
- Click Add API and select Experience Platform API.
- Choose OAuth Server-to-Server as the authentication method.
- Select the product profiles that include AEP access.
- Once created, go to the Credentials tab and click Generate access token.
- Copy the access token.
OAuth Server-to-Server credentials generate short-lived tokens. For production use, Datafly Signal handles token refresh automatically using the client ID and client secret. Enter both in the integration config.
Step 7: Note Your Sandbox Name
- In AEP, check the sandbox selector in the top-right corner.
- The sandbox name is shown (e.g.
prodfor production, or a custom development sandbox name). - Use this value for the
sandbox_nameconfig field.
API Endpoint
POST https://dcs.adobedc.net/collection/{connection_id}Events are sent as JSON payloads conforming to your XDM schema. Authentication is handled via the access token in the Authorization header.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
connection_id | string | Yes | The streaming connection ID from your HTTP API source. Found in Sources > HTTP API > connection details. |
org_id | string | Yes | Your Adobe IMS Organization ID in the format XXXXX@AdobeOrg. Found in the Adobe Admin Console. |
dataset_id | string | Yes | The target AEP Dataset ID to receive ingested data. Found in Datasets > dataset details. |
schema_id | string | Yes | The XDM Schema ID that the dataset is based on. Found in Schemas > schema details. |
sandbox_name | string | Yes | The AEP sandbox to target. Use prod for production or the name of your development sandbox. |
access_token | secret | Yes | OAuth 2.0 access token for the Adobe Experience Platform API. Generated via the Adobe Developer Console. |
Management UI Setup
- Go to Integrations in the sidebar.
- Open the Integration Library tab.
- Find Adobe Experience Platform or filter by Analytics.
- Click Install and fill in the required fields:
- Enter your Organization ID from Step 5.
- Enter your Connection ID from Step 4.
- Enter your Dataset ID from Step 3.
- Enter your Schema ID from Step 2.
- Enter your Sandbox Name from Step 7.
- Paste your Access Token from Step 6.
- Click Install Integration to create the integration with a ready-to-use default blueprint.
Management API Setup
curl -X POST http://localhost:8084/v1/admin/integration-catalog/adobe_experience_platform/install \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "Adobe Experience Platform",
"variant": "default",
"config": {
"connection_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"org_id": "1234567890ABCDEF@AdobeOrg",
"dataset_id": "5f1234abcd567890ef123456",
"schema_id": "https://ns.adobe.com/mycompany/schemas/abc123",
"sandbox_name": "prod",
"access_token": "your_access_token"
},
"delivery_mode": "server_side"
}'Event Mapping
Datafly Signal maps events to XDM ExperienceEvent format:
| Datafly Event | XDM Field Group | Notes |
|---|---|---|
page (page view) | web.webPageDetails | Maps page URL, title, referrer to XDM web fields |
Product Viewed | commerce.productViews | Product details mapped to productListItems |
Product Added | commerce.productListAdds | Product details mapped to productListItems |
Order Completed | commerce.purchases | Revenue, order ID, product items mapped |
identify | identityMap | User identifiers mapped to identity namespaces |
| Custom events | _experience.custom | Custom event data placed in extension fields |
Testing
Once your integration is active and events are flowing, verify in Adobe Experience Platform:
- Navigate to Monitoring in the left sidebar to view streaming ingestion metrics.
- Check your dataset under Datasets — the Preview dataset button shows recently ingested records.
- Open Profiles and search by an identity value to verify profile enrichment.
- Check Sources > HTTP API > Dataflows for ingestion success rates and error counts.
Streaming data typically appears in AEP within 1-3 minutes. Profile updates may take up to 15 minutes to propagate to all downstream services.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
401 authentication error | Expired or invalid access token | Generate a new token in the Adobe Developer Console |
403 forbidden | Insufficient permissions or wrong sandbox | Verify product profile permissions and sandbox name |
400 schema validation error | Event payload does not match XDM schema | Check that your blueprint field mappings match the schema field groups |
| No data in dataset | Incorrect connection ID or dataset ID | Verify IDs match in both AEP and Signal config |
| Profile not updating | Dataset not enabled for Profile | Enable the Profile toggle on the dataset details page |
| Events accepted but not visible | Sandbox mismatch | Ensure the sandbox_name config matches the sandbox where your dataset exists |
Intermittent 503 errors | AEP service temporarily unavailable | Signal retries automatically with exponential backoff; no action needed |
Delivery
Events are delivered server-side from your Datafly Signal infrastructure directly to the Adobe Experience Platform Streaming Ingestion API. No client-side Adobe scripts are loaded for this integration.
Visit the Adobe Experience Platform API documentation for full API reference and advanced configuration options.