Skip to content
Business productivity ⇄ Developer tools

Customer.io to Newrelic integration — real-time, two-way sync

Keep Customer.io and Newrelic 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 Customer.io and Newrelic

Connect the tickets, records, and events in Customer.io to the systems engineering runs in Newrelic, kept current in real time and in both directions.

Customer.io is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Newrelic is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.

Stacksync syncs Events, Segments, Campaigns, Broadcasts in Customer.io with Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.

Common use cases

  • 01 Push CRM segments and lead status into Customer.io so messaging respects sales stage.
  • 02 Land delivery and engagement events (sent, opened, clicked, bounced) from reporting webhooks into a warehouse for attribution analysis.
  • 03 Provision and update Dashboards and Alert Policies from a config repository or database through NerdGraph so definitions stay versioned and consistent across accounts and environments.
  • 04 Push custom business or pipeline Events and Metrics into New Relic through the Event and Metric APIs so they appear alongside APM data in dashboards and NRQL.

Common sync patterns

Where Newrelic tracks engineering work: requests become issues

A ticket or request raised in Customer.io opens or updates a matching issue in Newrelic, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.

Where Newrelic moves messages between services: activity lands on the stream

Records created or changed in Customer.io publish to the queue or topic in Newrelic as they happen, so downstream services react to real events rather than polling for them.

Where Newrelic is the directory or identity source: one set of users

People and accounts in Customer.io stay matched to the users in Newrelic, so access, provisioning, and org changes propagate instead of being keyed in twice.

What you can sync between Customer.io and Newrelic

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.

Customer.io objects Newrelic objects How this pairing syncs
Newsletters Recurring email sends with performance metrics available for reporting syncs. Entities The entity catalog of APM applications, hosts, services, and monitors searched via NerdGraph entitySearch; read for inventory, with tags added or replaced through taggingAddTagsToEntity so ownership and environment metadata stay in sync. Newsletters is specific to Customer.io and Entities to Newrelic — each maps to any object or custom field on the other side.
People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. People is specific to Customer.io and Workloads to Newrelic — each maps to any object or custom field on the other side.
Objects Non-person entities such as accounts or companies, related to people for account-level messaging. Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. Objects is specific to Customer.io and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side.
Events Behavioral events sent via the Track API that trigger campaigns. Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. Events is specific to Customer.io and Custom Events to Newrelic — each maps to any object or custom field on the other side.
Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. Segments is specific to Customer.io and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side.
Campaigns Automated workflows whose membership and metrics can be read via the App API. Dashboards Dashboard definitions and widgets via NerdGraph dashboardCreate/dashboardUpdate/dashboardDelete mutations and entity queries, with full CRUD; exported for backup and audit or provisioned and updated programmatically from a source of truth. Campaigns is specific to Customer.io and Dashboards to Newrelic — each maps to any object or custom field on the other side.

How changes propagate between Customer.io and Newrelic

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.

Customer.io Newrelic Sub-second propagation

DetectionCustomer.io notifies Stacksync of record changes through webhook events. Reporting webhooks push message and delivery events.

DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.

Newrelic Customer.io Sub-second propagation

DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).

DeliveryEach detected change is written to Customer.io through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Customer.io: Subject to per-API rate limits documented by Customer.io.
  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
What ships with Customer.io ⇄ Newrelic

Connect Customer.io and Newrelic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Customer.io–Newrelic connection.

Real-time

Two-way sync

Changes in Customer.io or Newrelic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Customer.io or Newrelic 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 Customer.io or Newrelic record.

Observability

Monitoring

Track your Customer.io ⇄ Newrelic sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Customer.io and Newrelic.

How the Customer.io and Newrelic connectors work

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io

Newrelic

Integration surface
NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
Authentication
User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
Change detection
NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
How it works

How to connect Customer.io to Newrelic — 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 Customer.io and Newrelic 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
    Customer.io connected
    Newrelic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Customer.io and Newrelic 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 · Customer.io ⇄ Newrelic
    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
    Customer.io Newrelic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Customer.io and Newrelic 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 296 integrations available for Customer.io and Newrelic.

Popular · 6 of 296
All Customer.io integrations All Newrelic integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own