Skip to content
Database ⇄ Marketing

Reltio to Twitter Ads integration — real-time, two-way sync

Keep Reltio and Twitter Ads 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 Reltio and Twitter Ads

Give your team Twitter Ads's contacts, campaigns, and engagement in Reltio: query them with SQL, push audiences built from your own data back to Twitter Ads, and skip the marketing API.

Twitter Ads holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Reltio, hard to get into campaigns without manual exports.

Stacksync mirrors Promoted Tweets, Custom Audiences, Targeting Criteria, Funding Instruments from Twitter Ads into Relations, Crosswalks, Interactions, Matches (Potential Matches) in Reltio field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Reltio, from usage, orders, or account status, sync back into Twitter Ads to drive campaigns and ads, with Twitter Ads kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 03 Pause or update Promoted Tweets and Line Items automatically when an upstream system such as budget pacing or inventory flags a rule breach.
  • 04 Push Campaigns and Line Items from a planning database or spreadsheet into X Ads so media buyers manage budgets, bids, and targeting without hand-entering each one in Ads Manager.

Common sync patterns

React to marketing changes as row changes

A new lead, form fill, or list change in Twitter Ads arrives as a row change in Reltio, so scoring, jobs, and notifications run in the tooling your team already uses.

Keep contact attributes consistent

Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.

Query Twitter Ads like a database

Contacts, leads, audiences, and campaign metrics from Twitter Ads live in Reltio as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

What you can sync between Reltio and Twitter Ads

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.

Reltio objects Twitter Ads objects How this pairing syncs
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Line Items Ad groups holding the per-engagement bid, promoted entity, and targeting; written to set bids and targeting, read for account structure. Matches (Potential Matches) is specific to Reltio and Line Items to Twitter Ads — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Promoted Tweets Tweets promoted under a line item; created, paused, or updated through the API and read back for delivery status. Activity Log is specific to Reltio and Promoted Tweets to Twitter Ads — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Custom Audiences Match lists (formerly Tailored Audiences); written by uploading hashed emails or device IDs from a CRM or warehouse segment for retargeting and suppression. Data Change Requests (DCR) is specific to Reltio and Custom Audiences to Twitter Ads — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Targeting Criteria Location, keyword, interest, and device rules attached to line items; read and written to adjust who a line item reaches. Reference Data (RDM) is specific to Reltio and Targeting Criteria to Twitter Ads — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Funding Instruments Budget source (credit card, credit line, insertion order); read-only in the API and provisioned by an X account manager, referenced by campaigns. Entities is specific to Reltio and Funding Instruments to Twitter Ads — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Analytics (Stats) Performance metrics for campaigns, line items, and promoted tweets; read-only via asynchronous jobs and pulled into a warehouse for reporting. Relations is specific to Reltio and Analytics (Stats) to Twitter Ads — each maps to any object or custom field on the other side.

How changes propagate between Reltio and Twitter Ads

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.

Reltio Twitter Ads Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Twitter Ads Reltio Interval-based propagation

DetectionStacksync polls Twitter Ads for changes on an incremental schedule, reading only records changed since the previous pass. Polling only — the Ads API has no webhooks or change-data-capture.

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

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • Twitter Ads: Per-endpoint 15-minute windows exposed via x-rate-limit-remaining and x-rate-limit-reset headers; asynchronous analytics is capped by concurrent jobs per account and covers up to 90 days per request.
What ships with Reltio ⇄ Twitter Ads

Connect Reltio and Twitter Ads for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Twitter Ads connection.

Real-time

Two-way sync

Changes in Reltio or Twitter Ads instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or Twitter Ads 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 Reltio or Twitter Ads record.

Observability

Monitoring

Track your Reltio ⇄ Twitter Ads sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and Twitter Ads.

How the Reltio and Twitter Ads connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

Twitter Ads

Integration surface
REST Ads API (synchronous management + asynchronous analytics jobs)
Authentication
OAuth 1.0a signed requests (three-legged user context) from a developer app allowlisted for the Ads API; OAuth 2.0 bearer tokens are limited to some read paths, while campaign, line item, and audience writes require OAuth 1.0a signing
Change detection
Polling only — the Ads API has no webhooks or change-data-capture; sync engines re-read entities and their state on a schedule and submit asynchronous analytics jobs for stats
Capabilities
read · write
Rate limits
Per-endpoint 15-minute windows exposed via x-rate-limit-remaining and x-rate-limit-reset headers; asynchronous analytics is capped by concurrent jobs per account and covers up to 90 days per request
How it works

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

    Choose tables

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

Reltio and Twitter Ads 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 391 integrations available for Reltio and Twitter Ads.

Popular · 8 of 391
All Reltio integrations All Twitter Ads 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