Adobe Analytics

Server-side event delivery to Adobe Analytics via the Data Insertion API for pageviews, custom events, and e-commerce tracking.

Why route Adobe Analytics 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 Analytics receives the complete event stream.
• Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Adobe Analytics attributes 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 Analytics is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Before configuring Adobe Analytics in Datafly Signal, you need an Adobe Experience Cloud account with Adobe Analytics provisioned, your tracking server URL, and a report suite ID.

API Endpoint

POST https://{tracking_server}/b/ss//6
Content-Type: application/xml

One event per call, as an XML <request> to the Data Insertion API. The report suite travels in <reportSuiteID>; no API key is needed. Every call carries a visitor (<marketingCloudVisitorID> when the ECID is known, and always <ipAddress> with <userAgent>) and either a page (<pageName>, <pageURL>) or a custom link (<linkType>o</linkType> with <linkName>). Adobe answers 200 with <status>SUCCESS</status>, or <status>FAILURE</status> and a <reason> for a hit it will not report.

Configuration

Management UI Setup

1. Go to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Adobe Analytics or filter by Analytics.
4. Click Install, select a variant if available, and fill in the required fields:
   • Enter your Tracking Server hostname from Step 3.
   • Enter your Report Suite ID from Step 2.
   • Paste your API Key (Client ID) from Step 4.
   • Select your Visitor ID Type from Step 5.
   • Optionally enable Timestamps and set a Currency Code.
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_analytics/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Adobe Analytics",
    "variant": "default",
    "config": {
      "tracking_server": "mycompany.sc.omtrdc.net",
      "report_suite_id": "mycompanyprod",
      "api_key": "your-adobe-client-id",
      "visitor_id_type": "ecid",
      "timestamp_enabled": true,
      "currency_code": "GBP"
    },
    "delivery_mode": "server_side"
  }'

Presets

Event Mapping

products is Adobe’s Category;Product;Quantity;Price string built from items[] (Price is the line total). Every documented property of the event is sent as contextData.<name> (for example contextData.insurance_type, contextData.quote_id): map them to eVars, props and success events with the report suite’s processing rules. currencyCode falls back to the integration’s currency_code.

Identity

For cross-solution identity, pair this integration with the Adobe Identity Service so the Experience Cloud ID (ECID) is the visitor key everywhere. Without an ECID Adobe identifies the visitor from IP and user agent. No personal data is sent.

Consent

Default consent category: analytics. Events are suppressed for visitors who have not consented to analytics tracking.

Verify it’s working

1. In the Signal Management UI, open your Adobe Analytics integration and watch the Live Events stream as you trigger events on your site.
2. Confirm 200 responses from {tracking_server}/b/ss//6 with <status>SUCCESS</status> in the body.
3. In Adobe Analytics, open Real-Time Reports (if enabled on your report suite). Page views appear within ~60 seconds.

Standard Workspace reports may take 30-90 minutes to populate.

Testing

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

1. Go to your Adobe Analytics workspace and open Real-Time Reports (if enabled on your report suite).
2. Alternatively, open the Adobe Experience Debugger browser extension and check the server calls section.
3. In the Workspace, create a freeform table with the Page dimension to verify page views are arriving.
4. Check the Events report to confirm custom events and ecommerce events are being recorded.
5. Use the Visitor Profile Viewer to verify that visitor IDs are being stitched correctly.

Troubleshooting

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Adobe Analytics Data Insertion API. No client-side Adobe scripts are loaded for this integration.

Blueprint

The Adobe Analytics blueprint version is 0.17.0 (not yet tested against a live report suite). It ships with Retail, Insurance and Automotive presets.

See also

• Adobe Identity Service — pair to use ECID as the cross-solution visitor key.
• Adobe Experience Platform — for streaming XDM ingestion alongside Analytics.