Integrations

Where captured emails, phones, consent and quiz answers flow. Connect a provider once with an API key; every campaign syncs to it automatically, with per-campaign overrides when you need them.

Connecting a provider

Click Connect, paste the API key, Save. Janus verifies the key live against the provider before storing it, so a typo fails at connect time, not at your first signup. Connected cards offer ⚙ Configure and Disconnect (nothing already synced is ever deleted).

Klaviyo

• Key: a Private API Key (pk_…). Config: your email list, picked from a live Load lists dropdown. Set that list to Single Opt-In in Klaviyo if you're revealing codes on-screen.
• What syncs: profile create-or-update, list subscription with explicit marketing consent (email consent syncs email, SMS consent syncs SMS, never crossed), and every quiz answer as a profile property for segmentation.
• The flow trigger: each issued reward fires a Popup Reward Issued event carrying the campaign, code and reward. Build your welcome flow on it, including the code-delivery email for double opt-in.
• Targeting hookup: Klaviyo lists and segments become targeting conditions, and the onsite cookie powers Identified by Klaviyo.

Postscript & Attentive

• Postscript: Private API Key (sk_…), optional keyword; supports on-site opt-in. Phone numbers sync only with SMS consent.
• Attentive: API key plus your API-enabled sign-up unit ID.
• Both pair naturally with double opt-in: Janus withholds the code, your SMS flow delivers it after confirmation.

Omnisend, Sendlane, Mailchimp, Privy

Same pattern: paste the key (Sendlane wants a v2 token; Mailchimp keys look like …-us1), pick a list/audience where applicable via the built-in picker, done. Consent and answers travel with each contact.

Shopify

Connected by the app install itself, no key. It powers discount minting, order webhooks for attribution, and optionally customer sync: the Tag customers toggle creates/updates the Shopify customer, tags them, and writes quiz answers to metafields. The store domain field is what auto-apply links use.

Per-campaign overrides

The builder's Where signups go panel controls destinations per campaign: a different Klaviyo list for a VIP popup, a Postscript keyword for one campaign, or the opt-in type switch. A warning dot appears if a campaign captures contacts that no connected provider would receive.

Reliability

• Your popup never waits on a provider. Syncs run after the signup completes; a provider outage can't break the visitor experience.
• Failures retry. A failed sync is recorded on the subscriber and retried automatically; Settings → Maintenance → Retry failed syncs re-queues everything pending on demand.
• Everything is exportable. Contacts, consent and answers stay queryable in Janus and export as CSV, no provider lock-in.