Skip to content
Analytics ⇄ Data warehouse

Adobeanalytics to Starburst Enterprise integration — real-time data sync

Keep Adobeanalytics and Starburst Enterprise 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 Starburst Enterprise

Flow Adobeanalytics data into Starburst Enterprise in real time — no exports, no schedulers, no custom scripts.

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

Adobeanalytics is where teams explore, visualize, and report; Starburst Enterprise is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Common use cases

  • 01 Pull ranked and trended Reports (metrics by dimension) into Postgres or a warehouse so web and marketing analytics join with CRM, ad-spend, and revenue data in SQL.
  • 02 Mirror Dimensions, Metrics, Calculated Metrics, and Segment definitions into a catalog database to document the Adobe Analytics reporting model.
  • 03 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 04 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Adobeanalytics matches the Starburst Enterprise table it was built from instead of drifting between refreshes.

Where Starburst Enterprise holds the source tables: live data in the reporting layer

Records maintained in Starburst Enterprise flow into Adobeanalytics as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between Adobeanalytics and Starburst Enterprise

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 Starburst Enterprise objects How this pairing syncs
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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Reports is specific to Adobeanalytics and Catalogs to Starburst Enterprise — 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Dimensions is specific to Adobeanalytics and Schemas to Starburst Enterprise — 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. Tables Queryable relations; writes pass through to sources whose connectors support them. Metrics is specific to Adobeanalytics and Tables to Starburst Enterprise — 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. Views Engine-level SQL views used to shape federated data before syncing it out. Calculated Metrics is specific to Adobeanalytics and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
Segments Saved segment definitions used to filter reports, read via GET /segments; cataloged and reused so downstream systems target the same audiences. Materialized views Precomputed results that make repeated sync reads cheaper. Segments is specific to Adobeanalytics and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
Date Ranges Saved relative or rolling date ranges, read via GET /dateranges; read as reusable reporting components for report requests. Columns Typed per the Trino type system, mapped from each source's native types. Date Ranges is specific to Adobeanalytics and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Adobeanalytics and Starburst Enterprise

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 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Adobeanalytics Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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 Starburst Enterprise 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Adobeanalytics ⇄ Starburst Enterprise

Connect Adobeanalytics and Starburst Enterprise for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adobeanalytics or Starburst Enterprise 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 Starburst Enterprise record.

Observability

Monitoring

Track your Adobeanalytics ⇄ Starburst Enterprise 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 Starburst Enterprise.

How the Adobeanalytics and Starburst Enterprise 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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Adobeanalytics to Starburst Enterprise — 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 Starburst Enterprise 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
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adobeanalytics and Starburst Enterprise 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 ⇄ Starburst Enterprise
    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 Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Adobeanalytics and Starburst Enterprise 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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 367 integrations available for Adobeanalytics and Starburst Enterprise.

Popular · 6 of 367
Coworkers laughing in front of a laptop in a casual office setting

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