Mailvio
Integrations › Mailvio

Mailvio Integration

Add ad leads to Mailvio subscriber groups automatically with email and custom fields mapped -- keeping your email lists growing without manual work.

Available Integrations

Connect Mailvio with 4 lead sources

Start Free Trial No credit card required · 14-day free trial
Trusted by
1,000+ businesses
Leads synced
2M+
Integrations
37+
Free trial
14 days, no card

How It Works

1
Connect Your Ad Account
Link your Facebook, Google, LinkedIn, or TikTok ad account to LeadSync in one click.
2
Choose Mailvio
Select Mailvio as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to Mailvio and start syncing leads instantly.

How LeadSync Adds Subscribers to a Mailvio Group

Mailvio organises contacts into groups rather than lists, and the API at apiv2.mailvio.com uses a single long-lived x-access-token header for authentication. LeadSync stores the access token you paste into the connection settings, calls GET /group to enumerate every group on your account, and POSTs each new Facebook, Google, LinkedIn, or TikTok lead to /group/{groupId}/subscriber with the email address and any mapped custom field values.

Setup is a single API token from your Mailvio account. Once it's pasted in, the LeadSync connection settings show a live dropdown of every Mailvio group you can write to -- pick the destination group per lead source and the integration is wired. No webhook URLs to manage, no per-group provisioning step.

Required vs Optional Custom Fields

Mailvio distinguishes required custom fields from optional ones, and surfaces the distinction directly in the Mailvio admin. LeadSync respects this: when it calls GET /customField to enumerate the field schema for the field mapping screen, required fields are flagged with an asterisk (e.g. First Name*) so you can see at a glance which questions on your lead form must have a mapping for the subscribe call to succeed.

Hidden fields (Mailvio admins can flag custom fields as hidden) are skipped entirely -- they don't appear in the LeadSync mapping dropdown, so you can't accidentally route lead form data into a field that's not active. The Email field uses a special internal ID (DEFAULT:Email) and is hoisted to the top-level emailAddress property on the subscribe payload, while everything else lands in the customFields object keyed by field ID.

Triggering Mailvio Automations on Group Add

Mailvio's automation builder uses contact added to a group as a trigger condition, so any automation you have set up against the destination group fires the moment LeadSync adds the new subscriber. Build a "Facebook leads welcome" automation in Mailvio, point it at the group LeadSync writes to, and every paid-social lead enters the cadence within seconds of submitting the ad form.

For multi-channel attribution, the cleanest pattern is one Mailvio group per ad source: Facebook leads go to Paid Social - Facebook, LinkedIn leads to Paid Social - LinkedIn, TikTok leads to Paid Social - TikTok. Each group has its own automation and its own engagement reporting, so attribution back to the originating ad platform stays clean across the lifecycle.

Frequently Asked Questions

In Mailvio, open Account > Settings > API and either copy the existing access token or generate a new one. Paste it into LeadSync when you create the Mailvio connection. LeadSync stores the token encrypted and uses it as the x-access-token header on every API call.
Groups. Mailvio's primary contact organisation unit is the group (rather than the list terminology used by Mailchimp / Brevo). LeadSync calls Mailvio's /group endpoint to enumerate every group on your account so you can pick the destination for each lead source.
In the LeadSync field mapping dropdown, required custom fields are flagged with an asterisk (e.g. "First Name*"). LeadSync reads the isRequired flag from Mailvio's customField endpoint and surfaces it in the UI so you can see which lead form questions must be mapped for the subscribe call to succeed.
They are excluded from the LeadSync mapping dropdown entirely. If a Mailvio admin marks a custom field as hidden, LeadSync skips it when enumerating the field schema, so you cannot accidentally route lead form data into an inactive field.
Yes. Build a Mailvio automation with a "contact added to group" trigger and point it at the group LeadSync writes to. Every new lead enters the automation within seconds of submitting the ad form, so welcome emails, multi-step nurture sequences, and segment-based branching all fire automatically.
The Email field uses a special internal ID (DEFAULT:Email) and is hoisted to the top-level emailAddress property on the subscribe payload that Mailvio expects. All other mapped fields land in the customFields object keyed by Mailvio's field ID. You won't see the DEFAULT prefix in the UI -- LeadSync handles the conversion automatically.
Yes. Each LeadSync connection points at one Mailvio group, so create separate connections per source if you want them isolated. Facebook leads can land in your paid-social-Facebook group with one automation, LinkedIn leads in a B2B group with a different one. Both connections share the same Mailvio access token but write to different groups.
Mailvio upserts subscribers by email address within a group, so a repeat submission updates the existing subscriber's custom field values rather than creating a duplicate. Your subscriber count and group reporting stay accurate.
Yes. LeadSync supports Mailvio as a destination for lead forms across Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own LeadSync connection but they all use the same Mailvio API helper writing to the /group/{id}/subscriber endpoint.

Start Syncing Leads to Mailvio

Set up your Mailvio integration in under 60 seconds. Free 14-day trial, no credit card required.

Start Your Free Trial
No credit card required • Set up in 60 seconds • Cancel anytime