Skip to content
Marketing ⇄ CRM

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

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

Keep the people you sell to and the people you market to in one shared view: Salesforce and Bingads sync contacts, accounts, and engagement in real time, in both directions.

Salesforce owns the customer relationship and the pipeline; Bingads runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Leads, Opportunities, Cases, Campaigns in Salesforce with Budgets & Bid Strategies, Audiences & Remarketing Lists, Conversion Goals & Offline Conversions, Ad Extensions (Assets) in Bingads field by field, in real time, and in both directions. You decide which system owns which fields — Salesforce can own account and opportunity status while Bingads owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 02 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • 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

Lead and lifecycle status agree

Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.

Segments and audiences follow the CRM

Where Bingads builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Salesforce, so who receives a campaign reflects current pipeline reality instead of a stale export.

Where Bingads generates leads: hand-off without re-keying

New leads or responders captured in Bingads flow into Salesforce assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

What you can sync between Bingads and Salesforce

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 Salesforce objects How this pairing syncs
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). Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Ad Extensions (Assets) Sitelink, callout, image, call, and other extensions/assets associated to campaigns and ad groups; CRUD via Campaign Management. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Ad Extensions (Assets) is specific to Bingads and Opportunities to Salesforce — each maps to any object or custom field on the other side.
Accounts, Customers & Users Customer Management hierarchy - accounts, customers, and users - read and managed to mirror agency/MCC-style structure and access into an internal database. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Accounts, Customers & Users is specific to Bingads and Cases to Salesforce — each maps to any object or custom field on the other side.
Performance Reports Campaign, ad group, keyword, geographic, and audience performance via the asynchronous Reporting service (submit, poll, download); read-only spend and conversion data. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Performance Reports is specific to Bingads and Tasks and Events to Salesforce — 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. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Ad Groups is specific to Bingads and Products and Price Books to Salesforce — 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. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Ads is specific to Bingads and Custom Objects to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Bingads and Salesforce

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

Salesforce Bingads Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Bingads ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

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

    Choose tables

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

Bingads and Salesforce 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 495 integrations available for Bingads and Salesforce.

Popular · 8 of 495
All Bingads integrations All Salesforce 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