Marketo to Supabase integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Marketo and Supabase: authenticate both systems, choose the objects to sync (such as Marketo's Activities and Lead Changes and Static Lists), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Marketo: Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on createdAt/updatedAt. Marketo's Webhooks are Smart Campaign flow-step outbound HTTP calls to a URL, not a general record-change subscription, so there is no push feed of arbitrary CRUD. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Supabase side: Views, Schemas, auth.users, Row Level Security Policies, plus custom fields where Supabase exposes them. On the Marketo side: Custom Objects, Activities and Lead Changes, Static Lists, Programs and Program Members. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Marketo and Supabase: Build audiences from your own data; Engagement and results next to the customer; React to marketing changes as row changes. Segments computed in Supabase from product usage, orders, or account status sync into Marketo as lists or audiences, so campaigns and ads target the people your data says they should.

Marketo: Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages. Authentication: OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026). Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. Stacksync manages authentication, retries, and rate limits on both sides.