Integrations
Connect the systems that own your customer facts so campaigns can use the same orders, subscriptions, accounts and product activity. The connection is only the first step: choose what will sync, understand the schema it creates, and verify the resulting records before building audiences on them.
Open Settings → Integrations to inspect the available providers, their setup information and connection state. For a custom source, use the Public API, webhooks, or an event collection source, depending on the direction and kind of data you need.
What you can connect
| Service | Data and workflow role |
|---|---|
| Shopify | Dedicated commerce schemas for customers, products, collections and orders, plus business events; initial-sync choices determine what history is brought across |
| Stripe | Enriched customer profiles and billing lifecycle events; subscription and invoice object backfill are optional settings, not an assumption for every connection |
| Attio | People and company data, with email and engagement actions integrated into the CRM |
| Supabase | A selected contact table and optional object tables; configured identity columns and mapped database columns determine the record shape |
| Segment | A destination for the calls and mappings configured in your Segment connection |
| Zapier | Selected triggers and actions, including record upserts, events, template sends and workflow enrollment |
A provider name does not mean every upstream object or historical event is imported. Check the connection's actual mapping, toggles and initial-sync scope. For example, Stripe's customer backfill and subscription/invoice object backfill have separate choices; Supabase requires a contact table and identifier mapping rather than choosing an arbitrary table automatically.
Connect one
From the integration's detail page, choose Connect to open the provider's connection flow. Some providers also begin from their own app directory. Follow that provider's setup and sign in to maxclicks when requested.
Choose the workspace you intend to connect; integration authorization requires administrative access. Complete any upstream authorization and mapping choices, then return to maxclicks to verify the resulting connection.
The detail page distinguishes Connected from Sync error and shows the connection date, Last synced or Never synced, and any last-sync error. “Connected” establishes that the connection exists; it does not prove a particular historical record has arrived. Inspect a known customer and related object, then compare its identity and business fields with the source.
A workspace has one connection entry per provider. Review the provider's account or store selection before connecting another account, and use the integration's setup information for supported account scope.
What the integration owns, and what stays yours
An integration can create dedicated schemas, attributes and other definitions such as segments, webhooks or a brand kit. Managed by and lock indicators identify those definitions. The owning integration maintains them; manual schema configuration and CSV import are restricted where they would conflict with that ownership.
You can add your own attributes to an integration-owned schema. Those fields have their own ownership and remain editable. Use them for context your team maintains, such as a campaign category or internal account note, instead of changing the meaning of a synced field.
Contacts and objects remain records you can inspect and use in audiences, emails and workflows. Manual edits to an upstream-owned value can be overwritten by the next sync. Deleting a record in maxclicks does not establish that the upstream system has deleted it or will stop supplying it.
Identity is still scoped to each schema. An integration's customer schema does not automatically merge its people into your existing default contact schema. Choose the right schema for the campaign and establish explicit relationships when information spans schemas.
Disconnecting, and the difference that matters
Use Disconnect on the integration detail page when you want to stop its sync while preserving its existing maxclicks data. The confirmation explains that managed definitions are handed back to you. The connection is removed, ownership locks are cleared, and the existing schemas and records remain.
Uninstall or provider erasure is a different operation. The integration's erasure flow requests deletion of the data it owns, including records in its schemas. That cleanup is durable and can continue asynchronously; workspace processing can be gated while it completes. Dependent campaigns and definitions can be affected by losing those schemas.
Choose based on the intended result: preserve the model and stop updates with Disconnect, or follow the provider's erasure flow when the owned data should be removed. Reconnecting later should be reviewed against the preserved schema and provider mapping rather than assumed to repair every previous campaign reference.
Pushing data in without an integration
Use the Public API when your backend owns record updates or business occurrences, and webhooks to receive supported notifications from maxclicks. For typed browser or server observations, configure collected events. Specify the identity, source authority, consent handling and retry contract before implementation; these interfaces do different jobs.