Skip to content
Marketing ⇄ Accounting and finance

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

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

Put revenue reality behind every campaign: Recurly and Bingads share the same customers, contacts, and billing status in real time, in both directions.

Recurly records the money — who pays, how much, and whether they are current; Bingads decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.

Stacksync syncs Invoices, Transactions, Line Items, Coupons and Redemptions in Recurly with Accounts, Customers & Users, Performance Reports, Campaigns, Ad Groups in Bingads field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Push campaign structure - campaigns, ad groups, ads, keywords, and negative keywords - from a planning database into Microsoft Advertising through the Campaign Management or Bulk service.
  • 04 Sync shared budgets and automated bid strategies so finance-approved spend and bids in an internal tool apply to live Microsoft Advertising campaigns.

Common sync patterns

Consent and contact details stay aligned

Email, phone, address, and opt-out flags kept in either system stay consistent in the other, so every send and record honors the latest preferences.

Revenue and billing signals reach the audience

Plan tier, spend, or payment status from Recurly lands on the matching record in Bingads, so segments and targeting reflect who actually pays and how much.

One customer and contact list

Where both systems keep customer or contact records, an edit on either side propagates to the other, ending dual maintenance and the drift it creates.

What you can sync between Bingads and Recurly

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 Recurly objects How this pairing syncs
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. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Budgets & Bid Strategies is specific to Bingads and Line Items to Recurly — each maps to any object or custom field on the other side.
Audiences & Remarketing Lists Remarketing, customer-match, in-market, and similar audiences; read and create/associate to keep audience lists aligned with a CDP or CRM. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Audiences & Remarketing Lists is specific to Bingads and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Conversion Goals & Offline Conversions Conversion goals (read/create) plus ApplyOfflineConversions, which imports offline conversion events (closed deals, qualified leads) back into Microsoft Advertising to inform bidding. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Conversion Goals & Offline Conversions is specific to Bingads and Billing Info to Recurly — each maps to any object or custom field on the other side.
Ad Extensions (Assets) Sitelink, callout, image, call, and other extensions/assets associated to campaigns and ad groups; CRUD via Campaign Management. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Ad Extensions (Assets) is specific to Bingads and Measured Units and Usage to Recurly — 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. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Accounts, Customers & Users is specific to Bingads and Accounts to Recurly — 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. Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Performance Reports is specific to Bingads and Subscriptions to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Bingads and Recurly

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

Recurly Bingads Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Bingads ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

Bingads and Recurly 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 459 integrations available for Bingads and Recurly.

Popular · 8 of 459
All Bingads integrations All Recurly 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