Configure Klaviyo or Mailchimp

Wavize syncs contacts to one specific audience

Klaviyo and Mailchimp have separate configuration pages. Each integration requires an API key, list/audience ID, sync mode and active status. During editing, leaving the key field blank preserves the stored secret.

Profile only creates or updates the profile without claiming marketing consent. Double opt-in triggers the provider confirmation process: the contact becomes subscribed only after the required action.

Shared security rule
Create a dedicated Wavize key, copy it once into the encrypted form, never email or screenshot it, and revoke immediately if exposed.

Configure Klaviyo with a private key

Wavize uses server endpoints: the six-character public key, called Site ID, is not suitable.

1. Create the key

   In Klaviyo: Settings > API keys > Private API Keys > Create Private API Key. Owner, Admin or Manager role is required. Name it Wavize and copy the pk_ value when created.

2. Choose scopes

   Verification reads accounts and list; sync creates/updates profiles and, in double opt-in, subscriptions. Grant at least matching accounts/lists read and profiles/subscriptions write scopes.

3. Find list ID

   Open Audience > Lists & Segments and the target list. Copy list ID from its settings or URL, not its display name. Wavize validates it with /lists/{id}.

Configure Mailchimp with key and Audience ID

A Mailchimp Marketing API key normally includes the data centre after a hyphen, such as -us21.

1. Create the key

   In Mailchimp: Profile icon > Profile > Extras > API keys > Create A Key. Name it Wavize, generate and copy immediately: Mailchimp later shows only its name and first characters.

2. Keep data-centre suffix

   Wavize extracts the suffix after the final hyphen to call the correct API host. A truncated key without -usXX cannot be routed correctly.

3. Find Audience ID

   Under Audience > All contacts > Settings > Audience name and defaults, copy Audience ID. It is neither the public name nor a campaign ID.

Choose profile-only or double opt-in

Mode must match your legal basis and widget wording.

• Profile only

  Klaviyo receives a profile; Mailchimp uses transactional status. Contact is not presented as a marketing subscriber and may support authorized non-promotional uses.

• Double opt-in

  Klaviyo starts a profile-subscription job; Mailchimp puts member in pending. The address must confirm with the provider before becoming active for marketing.

• Synced fields

  Valid email is mandatory, E.164 phone when present, first name, last name, organization, location and useful Wavize properties. Mailchimp FNAME/LNAME fields must exist or be compatible in the audience.

Verify and test a controlled contact

Wavize first tests account and audience before enabling synchronization.

1. Klaviyo verification

   Server calls /accounts then /lists/{id}. A 403 often means missing scope; a 404 may mean a list ID from another account.

2. Mailchimp verification

   Server calls /ping then /lists/{id}. A data-centre error often comes from key suffix; missing audience from an incorrect ID.

3. Acceptance contact

   Submit a team-owned address through the widget, verify Wavize creation and then provider arrival. In double opt-in, open and confirm the message before concluding.

Rotation and incident

A new key does not automatically replace the old one in Wavize.

• Create — New dedicated key with the same minimum permissions.
• Update and test — Enter new value, keep audience and mode, then verify.
• Revoke — Delete old provider key only after successful test.