Learn Mokapen

Klaviyo

Connect Klaviyo to Mokapen contacts for email marketing. Sync is bidirectional: data goes both ways, field mapping is ready, history enters on the first connection and updates follow after. On the page the name appears as klaviyo, lowercase: it is the same integration.

Overview: Integrations.

Requirements

• Klaviyo account with which to authorize OAuth access.
• Mokapen Large plan.
• Permission on contacts in Mokapen.

Connect

User menu → Integrations → Klaviyo and authorize the account. You do not paste an API key on this card: if authorization is refused or expires, disconnect and repeat the access, accepting the permissions Klaviyo shows.

The first sync brings existing contacts. Then a change in one system arrives in the other. Before leaving the direction toward Klaviyo on, look at the mapping: an empty Mokapen field mapped to a property you use in Klaviyo for flows (consent, language, list) clears it on the next sync. Klaviyo here aligns contacts. It is not the place where you read a flow’s performance, and it does not send Mokapen sequences: those go out from the CRM’s SMTP mailboxes.

When to stop

If Klaviyo is the source of new subscribers from the site and Mokapen is the source of clients already in a deal, decide who creates the contact. Leaving both free to create produces two cards for the same email. Historical sync does not merge duplicates already present on its own: those are fixed with the duplicates tool in the address book, after the first import.