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.

Why route Adobe Experience Platform through Datafly Signal

• Your numbers stop depending on what the browser allows. Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Adobe Experience Platform receives the complete event stream.
• Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what Adobe Experience Platform needs to attribute the event to the right session.
• Presets for Retail and Automotive. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Adobe Experience Platform is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Before configuring Adobe Experience Platform in Datafly Signal, you need an AEP account with a schema, dataset, streaming connection, and API credentials.

API Endpoint

POST https://dcs.adobedc.net/collection/{connection_id}

Each event is one XDM ExperienceEvent message in the documented HTTP API streaming shape:

{
  "header": {
    "schemaRef": { "id": "{schema_id}", "contentType": "application/vnd.adobe.xed-full+json;version=1" },
    "imsOrgID": "{org_id}", "datasetId": "{dataset_id}", "flowId": "{flow_id}",
    "source": { "name": "Datafly Signal" }
  },
  "body": {
    "xdmMeta": { "schemaRef": { "id": "{schema_id}", "contentType": "application/vnd.adobe.xed-full+json;version=1" } },
    "xdmEntity": { "_id": "<event ID>", "timestamp": "<ISO 8601>", "eventType": "commerce.purchases", "...": "..." }
  }
}

Authentication is optional; see Step 6.

Configuration

Management UI Setup

1. Go to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Adobe Experience Platform or filter by Analytics.
4. 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.
   • Enter your Dataflow ID from Step 4.
   • Leave Access Token empty unless the connection requires authentication (Step 6).
5. 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",
      "flow_id": "f2ae0194-8bd8-4a40-a4d9-f07bdc3e6ce2",
      "sandbox_name": "prod"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Every event carries _id (the Signal event ID), timestamp, eventType, an identityMap, environment.browserDetails.userAgent, environment.ipV4, web.webPageDetails.URL and web.webReferrer.URL. Only standard XDM ExperienceEvent fields are written, so the dataset’s schema needs the Web details, Commerce details and Environment details field groups.

productListItems[] is built from items[]: SKU (item ID), name, quantity, priceTotal (price times quantity) and currencyCode. Vertical attributes such as insurance_type or a vehicle’s make need custom fields under your tenant namespace (_<tenant>); add them to the installed blueprint.

Identity

Experience Platform is your own profile store, and the Journey Optimizer and Campaign destinations it feeds send email to the profile, so the email is streamed in plain text in the standard Email namespace (its advertising destinations hash on export; see Personal data by integration). The Email identity namespace must be enabled on the schema. For unified Adobe profiles, also install the Adobe Identity Service so the Experience Cloud ID (ECID) joins web and AEP events.

Consent

Default consent category: analytics. AEP is treated as an analytics destination by default — add advertising if you use AEP audiences for paid-media activation.

Verify it’s working

1. In the Signal Management UI, open your AEP integration and watch the Live Events stream as you trigger events on your site.
2. Confirm 200 responses from dcs.adobedc.net/collection/{connection_id}.
3. In AEP, open Monitoring for streaming ingestion metrics and Datasets > Preview dataset to inspect ingested records.

Testing

Once your integration is active and events are flowing, verify in Adobe Experience Platform:

1. Navigate to Monitoring in the left sidebar to view streaming ingestion metrics.
2. Check your dataset under Datasets — the Preview dataset button shows recently ingested records.
3. Open Profiles and search by an identity value to verify profile enrichment.
4. Check Sources > HTTP API > Dataflows for ingestion success rates and error counts.

Troubleshooting

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.

Blueprint

The Adobe Experience Platform blueprint version is 0.22.0 (not yet tested against a live sandbox). It ships with Retail, Insurance and Automotive presets.

See also

• Adobe Identity Service — issues the ECID that joins AEP with the rest of the Adobe stack.
• Adobe Analytics — run alongside AEP for traditional Workspace reporting.