Skip to content
Marketing ⇄ Database

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

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

Give your team Bingads's contacts, campaigns, and engagement in Citus: 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 Citus, hard to get into campaigns without manual exports.

Stacksync mirrors Accounts, Customers & Users, Performance Reports, Campaigns, Ad Groups from Bingads into Distributed tables, Reference tables, Local tables, Schemas in Citus 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 Citus, 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 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 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 Citus 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 Citus 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 Citus

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 Citus 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. Views Curated projections over distributed data, often used as read-only sync sources. Performance Reports is specific to Bingads and Views to Citus — 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). Sequences Key generators that matter when external writes must not collide with application inserts. Campaigns is specific to Bingads and Sequences to Citus — 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. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Ad Groups is specific to Bingads and Distributed tables to Citus — 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. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Ads is specific to Bingads and Reference tables to Citus — 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. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Keywords & Negative Keywords is specific to Bingads and Local tables to Citus — 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. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Budgets & Bid Strategies is specific to Bingads and Schemas to Citus — each maps to any object or custom field on the other side.

How changes propagate between Bingads and Citus

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

Citus Bingads Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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.
What ships with Bingads ⇄ Citus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Bingads ⇄ Citus 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 Citus.

How the Bingads and Citus 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.

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

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

    Choose tables

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

Bingads and Citus 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 390 integrations available for Bingads and Citus.

Popular · 7 of 390
All Bingads integrations All Citus 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