Skip to main content

Connectors

Launchpad has two connector contracts that must not be confused:

  • Directory status comes from src/lib/marketing/connector-specs.ts. It controls what admins can configure and which credential/setup fields the UI shows.
  • Ingestion support comes from SUPPORTED_BINDING_PLATFORMS in src/inngest/marketing-functions.ts. A connector can appear in the directory while its scheduled ingestion path is still unavailable.

This page reflects source as of 2026-10-20 (origin/main at 1396eab0). It does not prove that a connector is credentialed, healthy, or production-verified for a particular client; check Admin → Sync health for that operational state.

Capability matrix​

CategoryConnector keyDirectoryScheduled ingestionAuthentication / binding
Ad platformFacebook Ads (facebook)LiveSupportedMeta system-user/OAuth token + ad account ID
Ad platformInstagram Ads (instagram)LiveSupported through MetaMeta token + ad account ID
Ad platformGoogle Ads (google)LiveSupportedOAuth refresh token + developer token + customer ID
Ad platformTikTok Ads (tiktok)LiveSupportedMarketing API token + advertiser ID
Payments & CRMKonnektive (konnektive)LiveSupportedAPI login ID + password
Payments & CRMCheckout Champ (checkout_champ)LiveSupportedAPI login ID + password
Payments & CRMSticky.io (sticky_io)LiveSupportedMerchant API credentials + base URL
E-commerceUltraCart (ultracart)LiveSupportedSimple API token
E-commerceClickBank (clickbank)LiveSupportedDeveloper key + clerk key
E-commerceShopify (shopify)LiveSupportedAdmin token, or client ID + client secret
AttributionHyros (hyros)LiveSupportedWorkspace API key
AttributionConverge (bigquery_converge)LiveSupportedBigQuery service account + dataset pointer
AttributionCAKE (cake_sheet)LiveSupportedGoogle service account + Sheet pointer
Payments & CRMNorthbeam (northbeam)LiveSupportedData client ID + API key
Product analyticsPostHog (posthog)LiveSupportedPersonal API key + project ID
Payments & CRMChargeBee (chargebee)LiveSupported through the commerce syncSite name (subdomain) + API key
Payments & CRMSamCart (samcart)LiveSupported through the commerce syncAPI token + ad-ID order property and revenue format
Payments & CRMVrio (vrio)LiveOwn hourly function (sync-vrio-reports); syncs as a shadow source until the client's CRM source is switchedAPI key + base URL
Ops monitoringPostman Monitors (postman)LiveSupportedAPI key + workspace/monitor IDs
Payments & CRMStripe (stripe)PendingNot supportedRestricted API key fields can be captured
Payments & CRMBraintree (braintree)PendingNot supportedMerchant ID + public/private keys
Payments & CRMNMI (nmi)PendingNot supportedSecurity key
FulfillmentShipStation (shipstation)PendingNot supportedAPI key + secret
FulfillmentShipBob (shipbob)PendingNot supportedPersonal access token + channel ID
FulfillmentExtensiv (extensiv)PendingNot supportedOAuth client credentials + warehouse identifiers
FinanceFreshBooks (freshbooks)PendingNot supportedOAuth client + refresh token + account ID

“Live” above means the directory registry marks the connector live; “Supported” means the scheduled sync dispatcher accepts the binding. Neither is a production-health claim.

Data destinations​

  • Ad-platform rows land in the paid-acquisition analytics path.
  • Commerce and CRM connectors land transaction/order facts in the commerce ledger. Vrio is report-grain (purchases, revenue and leads per campaign or ad) rather than order-grain.
  • Hyros, Converge, CAKE, and Northbeam provide attribution inputs with connector-specific grain and latest-state rules.
  • PostHog and Postman are operational/product overlays rather than ad-spend sources.

Use Data model, Ingestion, and the connector setup drawer in Marketing Settings for exact fields and limitations.

Adding or changing a connector​

Update the directory registry, credential-vault resolver, dispatcher/fetcher, migrations, tests, and this matrix in the same change. A directory-only connector must remain clearly marked pending until the ingestion path and destination-table tests exist.