Adobe Analytics

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

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.

Step 1: Access Adobe Experience Cloud

Go to experience.adobe.com and sign in with your Adobe ID.
If you do not have an account, contact your Adobe account team or start a free trial.
Verify that Adobe Analytics is listed in the app switcher (nine-dot menu in the top-right).

Step 2: Find Your Report Suite ID

In Adobe Analytics, go to Admin > Report Suites.
Locate the report suite you want to receive events from Datafly Signal.
Copy the Report Suite ID (e.g. mycompanyprod).
If you need a new report suite, click Create New and follow the wizard.

Use a development report suite for initial testing. You can switch to your production report suite once you have verified events are arriving correctly.

Step 3: Find Your Tracking Server URL

In Adobe Analytics, go to Admin > All Admin > Tracking Server.
Your tracking server URL will be in the format yourcompany.sc.omtrdc.net or a custom CNAME domain.
Copy the tracking server hostname.

Alternatively, check your existing Adobe Analytics implementation (browser network tab or Adobe Experience Debugger) for the trackingServer value.

Step 4: Enable the Data Insertion API

Go to the Adobe Developer Console.
Create a new project or open an existing one.
Click Add API and select Adobe Analytics.
Choose OAuth Server-to-Server as the authentication method.
Select the product profile that includes your report suite.
Copy the Client ID (API Key) from the credentials page.

⚠️

The Data Insertion API requires a valid API key (Client ID) from the Adobe Developer Console. This is separate from your Adobe Analytics login credentials.

Step 5: Choose Visitor ID Type

Datafly Signal supports the following visitor identification methods:

ECID (recommended): Uses the Adobe Experience Cloud ID for cross-solution identity resolution. Requires the Adobe Identity Service integration to be active.
Custom Visitor ID: Uses a custom visitor identifier that you provide via _df.identify().
Fallback ID: Uses the Datafly anonymous ID as the visitor identifier.

Select the method that matches your Adobe Analytics implementation.

Step 6: Check Timestamp Configuration

In Adobe Analytics, go to Admin > Report Suites > Edit Settings > General > Timestamp Configuration.
Note whether your report suite uses Timestamps Required, Timestamps Optional, or Timestamps Not Allowed.
If timestamps are required or optional, enable timestamp_enabled in the Signal integration config.

API Endpoint

POST https://{tracking_server}/b/ss/{report_suite_id}/6

Events are sent as XML payloads to the Adobe Analytics Data Insertion API. Authentication is handled via the API key in the request headers.

Configuration

Field	Type	Required	Description
`tracking_server`	string	Yes	Your Adobe Analytics tracking server hostname (e.g. `mycompany.sc.omtrdc.net`). Found in Admin > All Admin > Tracking Server.
`report_suite_id`	string	Yes	The Adobe Analytics Report Suite ID to receive events (e.g. `mycompanyprod`). Found in Admin > Report Suites.
`visitor_id_type`	select	Yes	The type of visitor identifier to use: ecid (Experience Cloud ID), custom (your own user ID), or fallback (Datafly anonymous ID).
`timestamp_enabled`	boolean	No	Enable if your report suite uses Timestamps Required or Timestamps Optional. When enabled, each hit includes a UTC timestamp.
`currency_code`	string	No	ISO 4217 currency code for revenue events (e.g. `GBP`, `USD`, `EUR`). Defaults to the report suite’s configured currency.

Management UI Setup

Go to Integrations in the sidebar.
Open the Integration Library tab.
Find Adobe Analytics or filter by Analytics.
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.
- Select your Visitor ID Type from Step 5.
- Optionally enable Timestamps and set a Currency Code.
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",
      "visitor_id_type": "ecid",
      "timestamp_enabled": true,
      "currency_code": "GBP"
    },
    "delivery_mode": "server_side"
  }'

Variants

Adobe Analytics is available in multiple pre-configured variants to match your industry:

Variant	Key	Description
Default	`default`	Standard Adobe Analytics server-side delivery with pageview, custom event, and conversion tracking.
Retail & Ecommerce	`retail`	Ecommerce-optimized configuration with product string mapping, merchandising eVars, and purchase event handling.
Media & Entertainment	`media`	Media-focused configuration with Adobe Media Analytics heartbeat tracking for video and audio content engagement.

Each variant provides a tuned default blueprint. You can customise any setting after installation.

Event Mapping

Datafly Signal maps standard event names to Adobe Analytics server calls:

Datafly Event	Adobe Analytics Hit Type	Notes
`page` (page view)	`t()` page view	Maps to `pageName`, `pageURL`, `referrer`
`Product Viewed`	`s.events = "prodView"`	Product data mapped to `s.products` string
`Product Added`	`s.events = "scAdd"`	Product data mapped to `s.products` string
`Product Removed`	`s.events = "scRemove"`	Product data mapped to `s.products` string
`Checkout Started`	`s.events = "scCheckout"`	Cart value and items included
`Order Completed`	`s.events = "purchase"`	Revenue, order ID, product string populated
Custom events	`tl()` custom link	Sent as custom link tracking calls with event name as link name

Testing

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

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

Adobe Analytics data can take 30-90 minutes to appear in standard reports. Use Real-Time Reports or the Data Insertion API response codes for immediate verification.

Troubleshooting

Symptom	Cause	Fix
No data in reports	Incorrect report suite ID	Verify the report suite ID in Admin > Report Suites matches the config
`400` response from API	Malformed XML payload	Check the Datafly Signal delivery logs for payload details
Events rejected with timestamp error	Report suite does not accept timestamps	Disable `timestamp_enabled` or change the report suite’s timestamp setting
Visitor ID not stitching	Wrong visitor ID type selected	Ensure `visitor_id_type` matches your Adobe implementation (ECID recommended)
Revenue not appearing	Currency code mismatch	Set `currency_code` to match your report suite’s configured currency
`403` authentication error	Invalid or expired API key	Regenerate credentials in the Adobe Developer Console
Duplicate hits	Event processor retry after timeout	Adobe deduplicates by visitor ID + timestamp; no action needed if timestamps are enabled

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.

Visit the Adobe Analytics Data Insertion API documentation for full API reference and advanced configuration options.

Google Analytics 4 Adobe Experience Platform