External email integrations (Mailchimp, SendPulse, HubSpot, etc.)

Instead of sending sequences from web2wave, you can sync leads and customers to external email platforms and run campaigns there.

Supported providers include:

SendPulse

SendGrid

Mailchimp

Braze

MailerLite

CleverTap

HubSpot

Klaviyo

Reteno

Configuration

(Example: SendPulse), this is applicable for all email integrations:

Go to Project settings → Emails → Integrations.
Select SendPulse.

Enabling SendPulse
Provide:
- Sendpulse client id from the ID field at SendPulse Account settings - API link
- Sendpulse client secret from the Secret field at SendPulse Account settings - API.
  
  SendPulse dashboard account settings illustration
- Sendpulse User List ID - list where web2wave should add users. Mailings Lists tab. Direct link to SendPulse.
  
  How to retrieve the list ID
Optionally configure:
- Sendpulse User tag and Sendpulse Buyer tag to apply.
- Sendpulse send properties - quiz answers or user properties to send as custom fields (e.g. last_quiz_id, utm_source, utm_campaign, gender).

Setup Mailchimp guide

Tags should be added in Mailchimp https://mailchimp.com/help/create-add-remove-tags/
In web2wave Project settings → Email:

Mailchimp User Tag:
- User tags are labels you can use to categorize or group contacts in your audience.
- You can define or find existing tags under Audience > All contacts > select a contact > Tags.
Mailchimp Buyer Tag:
- Similar to the User Tag, this is a custom tag used to identify "buyers" specifically.
- Add or find it in the same way as above.
Mailchimp Send Properties:
- This field is typically used to define properties or custom data you want to send to Mailchimp for your contacts.
- These properties depend on how you configure your integration or workflow. For example, they might include custom fields like purchase history, preferences, or signup source.

Behavior:

When a user leaves an email or purchases, web2wave creates or updates a contact in the external system.
If the custom field does not exist yet, most providers create it automatically on first write.

Use Reteno integration when you need both:

In Project settings → Emails → Integrations → Reteno:

Enable Reteno.
Fill Reteno API Key.
(Optional) Fill segment IDs:
- Every user Segment ID - segment for all synced users.
- Buyer Segment ID - segment for buyers.
(Optional) Enable Send Events to Reteno.
Configure Send user properties.

Use one property per line:

Examples:

amplitude_device_id=EXTERNAL_ID
user_country_code=COUNTRY
age=AGE
gender=GENDER
last_quiz_id=COHORT

Notes:

When syncing a contact to Reteno, web2wave uses:

web2wave also sends system fields (when available), including:

If Send Events to Reteno is enabled, web2wave sends:

Standard properties sent in event payloads:

Common (when available):
- externalCustomerId
- user_id
- user_email
- language
- project_id
RegistrationInWeb:
- externalCustomerId, user_id, email, date, created_at
CompleteRegistration:
- externalCustomerId, user_id, email, language, date, created_at
- mapped user properties from Send user properties
Subscription events (SubscriptionPurchased, SubscriptionRenewed, SubscriptionRefunded, SubscriptionCancelled):
- subscription_id, status, payment_system, pay_system_id
- price_id, plan_id, amount, currency
- total_revenue, charges_count
- cancel_at_period_end, canceled_at
- next_charge_date, last_charge_date
- quiz_id, paywall_id
- created_at, updated_at
- for invoice-based events (SubscriptionRenewed, SubscriptionRefunded) also invoice fields such as invoice_id, invoice_status, invoice_amount, invoice_amount_usd, invoice_date, is_refund

Reteno events are queued and sent asynchronously with a short delay after trigger, so they may appear in Reteno slightly after the user action.