Adobe Analytics
Send event and hit data to Adobe Analytics for web and app analytics reporting. SignalSmith uses the Bulk Data Insertion API to upload visitor interactions, pageviews, custom events, eVars, and props directly into your report suite.
Prerequisites
- An Adobe Analytics account with a valid report suite
- An Adobe Developer Console project with Server-to-Server OAuth credentials
- Your Adobe Analytics global company ID and report suite ID
- Your Adobe Analytics tracking server hostname
Authentication
Adobe Analytics uses OAuth 2.0 Server-to-Server (client credentials) authentication.
- Go to the Adobe Developer Console
- Create a new project (or use an existing one)
- Click Add API and select Adobe Analytics
- Choose OAuth Server-to-Server as the credential type
- Select a product profile that has access to your report suite
- Copy the Client ID and Client Secret
- Enter them in SignalSmith when creating the destination
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Global Company ID | Text | Yes | Your Adobe Analytics company identifier. Found in the Adobe Admin Console or the Analytics API. |
| Report Suite ID | Text | Yes | The report suite to send data to (e.g., mycompanyreportsuite). |
| Tracking Server | Text | Yes | Your Analytics tracking server hostname (e.g., mycompany.sc.omtrdc.net). Found in Adobe Analytics under Admin > Tracking. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Visitor ID Type | Select | Yes | How visitors are identified: Marketing Cloud Visitor ID (recommended), Visitor ID, Customer ID, or IP Address. |
| Timestamp Format | Select | No | Timestamp format for hit data: ISO 8601 (default) or Unix epoch. |
Supported Operations
Sync Modes: Insert
Adobe Analytics accepts append-only event data. Each sync inserts new hits into the report suite.
Features
- Field Mapping: Yes
- Schema Introspection: No
Default Destination Fields
reportSuiteID, timestamp, marketingCloudVisitorID, visitorID, pageURL, pageName, userAgent, ipAddress, eVar1–eVar3, prop1–prop3, events, products, channel, campaign, referrer
Required Mapping Fields
| Field | Description |
|---|---|
| timestamp | The timestamp of the hit event |
| userAgent | The visitor’s browser user agent string |
At least one page identifier is also required: pageURL, pageName, or linkType + linkName + linkURL.
How It Works
- SignalSmith reads event data from your warehouse model
- Data is formatted as a CSV file with the mapped fields
- The CSV is compressed (gzip) and uploaded to the Adobe Analytics Bulk Data Insertion API
- Adobe processes the file and the hits appear in your report suite (typically within 30–60 minutes)
Rate Limits
- Maximum 100 MB compressed (1 GB uncompressed) per file
- Maximum 1 file upload per second
- Rows must be chronologically sorted per visitor for accurate session stitching
Troubleshooting
Authentication failed
Verify your Client ID and Client Secret in the Adobe Developer Console. Ensure the OAuth Server-to-Server credential is active and the product profile has access to the target report suite.
Report suite not found
Check that the Report Suite ID matches exactly (case-sensitive). Verify the Global Company ID is correct — you can find it in the Adobe Admin Console or by calling the Analytics discovery API.
Missing required fields
Every hit must include a timestamp, a visitor identifier (based on your Visitor ID Type selection), a user agent, and at least one page identifier (pageURL, pageName, or link fields).
Hits not appearing in reports
Processing can take 30–60 minutes. Ensure timestamps are within the report suite’s configured timezone and that rows are sorted chronologically per visitor.