🚧

THIS DOCUMENT IS UNDER CONSTRUCTION. DETAILS SUBJECT TO CHANGE.

What Is Adobe Analytics?

Adobe Analytics is an enterprise digital analytics platform for tracking and analyzing user behavior across web and mobile properties. It provides insights into customer journeys, conversion rates, and marketing performance. The Data Insertion API allows for direct server-to-server event ingestion, bypassing client-side tracking.

Product Type: Analytics
Integration Type: Starter Kit
Event Source Type: Web & Mobile
Event Scope: Full-Funnel Events

Capabilities

• Direct server-side event ingestion using Adobe’s Data Insertion API 1.4, without requiring an Adobe Experience Platform (AEP) license

• Full-funnel analytics without client-side JavaScript

• Compatible with both web and mobile event sources

• Removes the typical GET character limitation by form-encoding query string parameters into the POST body (Content-Type: application/x-www-form-urlencoded), preserving GET semantics while allowing for larger payloads

Considerations

• Adobe requires a unique visitorID to track users
• Some features (e.g., Real-Time reports) may be unavailable with server-side ingestion
• Adobe 1.4 Per-parameter/field limits apply; Adobe may truncate payloads server-side.
• Silent failures: Mis-encoded fields may be dropped without explicit error. Strict encoding parity is essential.

Limitations

• Does not support on-site personalization or client-side A/B testing
• Cannot use dynamic tag-based features or client-side JavaScript variables
• No bulk ingestion (Data Insertion 1.4 uses single-hit semantics)

Starter Kit Setup Guide

1. Gather Credentials

• Ask Adobe representatives for the following credentials:
  • Report Suite ID (RSID)
  • Tracking Server URL

2. Add an Adobe Analytics Integration

• From the integration library, add an Adobe Analytics integration. Then, fill out the Connection Parameters:

3. Configure Event Mapping

MetaRouter provides all of the event mappings that Adobe Analytics integrations typically require. You may add custom events, parameters, or mappings in accordance with Adobe’s Data Insertion API documentation.

4. Deploy to Pipeline

• In Pipelines, add your Adobe Analytics integration
• Select the correct integration revision
• Click Add Integration to finalize deployment

Event Mappings

Global — WORK IN PROGRESS

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Event-Specific — WORK IN PROGRESS

Event-level mappings (e.g., product_added, order_completed) will be published as implementation proceeds.

Required & Recommended Identifiers

These identifiers must be mapped for successful user stitching in Adobe Analytics.

Validation & Monitoring

Example Request

POST https://<trackingServer>/b/ss/<RSID>/0
Content-Type: application/x-www-form-urlencoded
User-Agent: <original UA if available>
X-Forwarded-For: <client_ip_if_proxied>  ; optional, if you preserve client IP

# Body (form-encoded; keys mirror GET params)
pageName=Checkout%20Complete&
events=purchase&
pe=lnk_o&
pev2=order_completed&
visitorID=abc123xyz&
timestamp=1724937600&
pageURL=https%3A%2F%2Fexample.com%2Fcheckout%2Fcomplete&
referrer=https%3A%2F%2Fexample.com%2Fcart&
userAgent=Mozilla%2F5.0%20...&
c1=SKU-12345&c2=199.99

Replace c1, c2, etc., with your mapped eVars/props as appropriate for your suite.

Transport Validation

1. Parity Tests: For a sample event (e.g., order_completed), send:
   • A canonical GET request
   • An equivalent POST-via-GET body
     Confirm identical processing in Adobe (hit arrives, fields set identically).
2. Encoding Checks: Verify URL-encoding of all values in the POST body. Watch for:
   • Special characters (spaces, &, =, ?, %, UTF-8)
   • Arrays/multi-values (send as Adobe expects for that param)
3. Headers: Ensure Content-Type: application/x-www-form-urlencoded. Preserve User-Agent and client IP when possible.

Adobe Acceptance Signals

• HTTP 2xx with no error message generally indicates acceptance (Adobe’s 1.4 responses can be terse).
• Use debug logging to capture request/response pairs and Adobe error payloads (when present).
• Cross-verify via data feeds or workspace after processing windows.

Monitoring & Guardrails

• Schema guards: Validate required fields (visitorID, rsid, minimal hit fields).
• Size guards: Alert if body size or key/value lengths approach known limits.
• Drop/Retry policy: On transport failures (5xx/timeouts), retry with backoff. On 4xx due to validation, surface to logs and do not retry blindly.
• Sampling checks: Periodically compare event counts between source and Adobe to detect silent truncation or parameter loss.

Additional Adobe Analytics Documentation

• Adobe Data Insertion API Guide
• Adobe Analytics Implementation Guide