How to Integrate Wisepops with Omnisend

How do you connect Omnisend?

1. In Omnisend: Profile menu → Store settings → Integrations & API → API key → Create API key. Copy it.

2. In Wisepops, open the campaign and click the sign-up block.

3. Open Sync, choose Omnisend.

4. Paste the API key → Submit.

5. Add tags if you run more than one form and need to know which one fired.

6. Save.

Email comes from the Sign-up block. SMS numbers come from the Phone block. Use both on the same form if you want both identifiers.

What maps cleanly, and what doesn't?

Merge with default properties: City, Country, State. Notes from the help article:

• Region has no Omnisend property.
• Postal code: Wisepops calls it something Omnisend will not accept as postalCode. Treat as custom.
• Gender: Omnisend accepts only m and f. Radio buttons with those values, not "Male"/"Female".
• Phone: use the Phone block, not a "phone number" merge. Omnisend's property is phone.

Anything else: type a custom property name. Custom values are strings, max 2048 characters.

Omnisend's own write-up: integration with Wisepops.

More: Wisepops integrations, Mailchimp, Klaviyo.

Verify identifiers and properties separately

Official documentation checked September 6, 2026. This checklist is editorial guidance, not a client test report.

Submit a controlled entry on the published website and record the campaign and test time. Inspect the resulting Omnisend contact rather than relying only on the popup’s success message.

A phone value stored as a custom property is not the same validation result as a phone identifier. Check the actual destination field before relying on an SMS workflow. Likewise, a custom postal value does not prove the default postal field was populated.

Troubleshoot a partial sync

If no contact appears, check the saved connection and account before changing field mappings. If only one property is missing, compare its source input, destination name and accepted format. For long custom text, check the documented length limit and avoid silently truncating information needed by your workflow.

If the contact is present but a welcome message does not follow, inspect subscription state and automation conditions separately. Record any available error and the test time. Repeat-submission and existing-contact behavior should be tested as separate cases before handoff.