Skip to content
Marketing ⇄ Database

Bingads to Reltio integration — real-time, two-way sync

Keep Bingads and Reltio 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 Bingads and Reltio

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

Bingads 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 Performance Reports, Campaigns, Ad Groups, Ads from Bingads 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 Bingads to drive campaigns and ads, with Bingads 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 Mirror Accounts, Customers, and users from Customer Management into an internal database for agency/MCC-style hierarchy and access reporting.
  • 04 Two-way sync remarketing and customer-match audiences so audience lists stay aligned between a CDP or CRM and Microsoft Advertising.

Common sync patterns

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 Bingads like a database

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

Build audiences from your own data

Segments computed in Reltio from product usage, orders, or account status sync into Bingads as lists or audiences, so campaigns and ads target the people your data says they should.

What you can sync between Bingads and Reltio

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.

Bingads objects Reltio objects How this pairing syncs
Performance Reports Campaign, ad group, keyword, geographic, and audience performance via the asynchronous Reporting service (submit, poll, download); read-only spend and conversion data. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Performance Reports is specific to Bingads and Crosswalks to Reltio — each maps to any object or custom field on the other side.
Campaigns Search, Audience, Shopping, and Performance Max campaigns with budget, status, and campaign-type settings; full create/read/update/delete through the Campaign Management service (or Bulk for scale). Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Campaigns is specific to Bingads and Interactions to Reltio — each maps to any object or custom field on the other side.
Ad Groups Ad groups under a campaign with bids, network and audience targeting, and status; CRUD via Campaign Management, so structure can be pushed in from a database. 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. Ad Groups is specific to Bingads and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side.
Ads Responsive search ads, expanded text ads, image and responsive ads; created and updated through Campaign Management so ad copy is managed from a source of truth. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Ads is specific to Bingads and Activity Log to Reltio — each maps to any object or custom field on the other side.
Keywords & Negative Keywords Bidded keywords and account/campaign/ad-group negative keywords with match types; CRUD, and the Bulk service is recommended for large keyword changes. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Keywords & Negative Keywords is specific to Bingads and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side.
Budgets & Bid Strategies Shared budgets and automated bid strategies (e.g. Maximize Conversions, Target CPA); read and write so finance-approved spend and bids apply to live campaigns. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Budgets & Bid Strategies is specific to Bingads and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Bingads and Reltio

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.

Bingads Reltio Interval-based propagation

DetectionStacksync polls Bingads for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks or change-data-capture.

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

Reltio Bingads 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 Bingads through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Bingads: Service-specific throttling rather than one global limit. Ad Insight caps calls per user per minute with a 60-second sliding window at the customer level. The Bulk service caps download/upload calls and, once hit, returns 'no more bulk upload or download calls will be permitted for this account,' clearing after up to 15 minutes; Campaign Management caps entities per call, so large changes go through Bulk.
  • 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.
What ships with Bingads ⇄ Reltio

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Bingads and Reltio connectors work

Bingads

Integration surface
SOAP web services (Bing Ads API v13): Campaign Management, Bulk, Reporting, Customer Management, Customer Billing, and Ad Insight services, plus offline conversion import. SDKs for C#, Java, Python, and PHP; a Sandbox environment mirrors production.
Authentication
OAuth 2.0 (Microsoft identity platform / Azure AD) access tokens passed in the SOAP AuthenticationToken header, plus a Microsoft Advertising Developer Token that authorizes API access; calls are scoped by CustomerId and account (CustomerAccountId).
Change detection
No webhooks or change-data-capture. Reporting is asynchronous - submit a report request, poll until it completes, then download the file. Current campaign state is refreshed via scheduled Bulk downloads (full or by last-sync date) or entity list calls.
Capabilities
read · write
Rate limits
Service-specific throttling rather than one global limit. Ad Insight caps calls per user per minute with a 60-second sliding window at the customer level. The Bulk service caps download/upload calls and, once hit, returns 'no more bulk upload or download calls will be permitted for this account,' clearing after up to 15 minutes; Campaign Management caps entities per call, so large changes go through Bulk.

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.
How it works

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

    Choose tables

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

Bingads and Reltio 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 389 integrations available for Bingads and Reltio.

Popular · 7 of 389
All Bingads integrations All Reltio 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