Skip to content
Analytics ⇄ Database

Adobeanalytics to InterSystems IRIS integration — real-time data sync

Keep Adobeanalytics and InterSystems IRIS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Adobeanalytics and InterSystems IRIS

Give Adobeanalytics the users, events, and records that live in InterSystems IRIS in real time, and sync the cohorts and scores Adobeanalytics computes back into InterSystems IRIS where your applications read them.

Adobeanalytics is a read-only source: Stacksync reads its data in real time and delivers it into InterSystems IRIS, so InterSystems IRIS always reflects the current state of Adobeanalytics — without exports, scripts, or schedulers.

A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Adobeanalytics is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from InterSystems IRIS into Adobeanalytics usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.

Common use cases

  • 01 Mirror Dimensions, Metrics, Calculated Metrics, and Segment definitions into a catalog database to document the Adobe Analytics reporting model.
  • 02 Load report data on a schedule into a reporting database for executive dashboards without manual Analysis Workspace exports or Report Builder pulls.
  • 03 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 04 Consolidate IRIS data with other databases in an analytics warehouse for cross-system reporting

Common sync patterns

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in InterSystems IRIS land in Adobeanalytics as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

One version of each user or account

A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.

Filter and grouping dimensions kept fresh

Attributes teams slice by, such as plan, region, or account owner, stay current in Adobeanalytics because they sync from InterSystems IRIS as they change, instead of going stale after a one-time import.

What you can sync between Adobeanalytics and InterSystems IRIS

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Adobeanalytics objects InterSystems IRIS objects How this pairing syncs
Users Users in the Analytics company, read via GET /users and /users/me; loaded for access, entitlement, and identity reconciliation reporting. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Users is specific to Adobeanalytics and Tables to InterSystems IRIS — each maps to any object or custom field on the other side.
Usage and Access Logs Admin audit and usage logs of report and tool activity, read via the usage/audit-log endpoints; loaded for security, governance, and adoption reporting. Views SQL views expose curated slices of data for outbound replication. Usage and Access Logs is specific to Adobeanalytics and Views to InterSystems IRIS — each maps to any object or custom field on the other side.
Reports Core reporting endpoint (POST /reports on analytics.adobe.io); returns ranked or trended report data for chosen metrics broken down by dimensions over a date range, with optional segment filters. The main dataset Stacksync reads out. Schemas Schema organization scopes which tables a sync connection can see. Reports is specific to Adobeanalytics and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side.
Dimensions Available report dimensions (eVars, props, and standard dimensions) per report suite, read via GET /dimensions; pulled as reporting metadata to build report requests and mirror the model. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Dimensions is specific to Adobeanalytics and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side.
Metrics Standard metrics available for a report suite, read via GET /metrics; read as metadata to construct report requests and document available measures. Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Metrics is specific to Adobeanalytics and Globals to InterSystems IRIS — each maps to any object or custom field on the other side.
Calculated Metrics User-defined derived metrics, read via GET /calculatedmetrics; mirrored so downstream tools reference the same calculated-metric definitions. Namespaces Namespaces partition databases and determine the connection context for integrations. Calculated Metrics is specific to Adobeanalytics and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side.

How changes propagate between Adobeanalytics and InterSystems IRIS

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Adobeanalytics InterSystems IRIS Interval-based propagation

DetectionStacksync polls Adobeanalytics for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based over a date range: reports are requested for a from/to window and re-queried on a schedule.

DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

InterSystems IRIS Adobeanalytics Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

DeliveryAdobeanalytics does not accept inbound record writes, so this direction carries requests rather than records: Adobeanalytics's output flows back as field updates on the originating InterSystems IRIS records.

Rate-limit considerations

  • Adobeanalytics: The Analytics 2.0 API enforces 12 requests per 6 seconds (about 120 per minute) per user; exceeding it returns HTTP 429 with error_code 429050. A separate per-report-suite reporting-engine throttle can slow large requests without returning an error.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Adobeanalytics ⇄ InterSystems IRIS

Connect Adobeanalytics and InterSystems IRIS for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adobeanalytics–InterSystems IRIS connection.

Real-time

Real-time sync

Changes in Adobeanalytics or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adobeanalytics or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Adobeanalytics or InterSystems IRIS record.

Observability

Monitoring

Track your Adobeanalytics ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Adobeanalytics and InterSystems IRIS.

How the Adobeanalytics and InterSystems IRIS connectors work

Adobeanalytics

Integration surface
Analytics 2.0 REST API on analytics.adobe.io for reporting and components; Data Feeds and Data Warehouse for raw hit-level export; Data Insertion and Bulk Data Insertion (CSV) APIs for inbound server-side collection.
Authentication
OAuth Server-to-Server via the Adobe Developer Console (JWT service-account auth was deprecated January 1, 2025). The company's global company ID is sent in the x-proxy-global-company-id header, and the integration needs at least the Report Suites, Metrics, and Dimensions permission groups.
Change detection
Pull-based over a date range: reports are requested for a from/to window and re-queried on a schedule. No change-data-capture feed or report-data webhooks; Adobe recommends not polling for new data faster than every 30 minutes and caching results.
Capabilities
read
Rate limits
The Analytics 2.0 API enforces 12 requests per 6 seconds (about 120 per minute) per user; exceeding it returns HTTP 429 with error_code 429050. A separate per-report-suite reporting-engine throttle can slow large requests without returning an error.

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits
How it works

How to connect Adobeanalytics to InterSystems IRIS — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Adobeanalytics and InterSystems IRIS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Adobeanalytics connected
    InterSystems IRIS connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adobeanalytics and InterSystems IRIS objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Adobeanalytics ⇄ InterSystems IRIS
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Adobeanalytics InterSystems IRIS
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Adobeanalytics and InterSystems IRIS integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.