Skip to content
RocketVerifierDOCS

Use cases

Keep your CRM clean

In short

Connect your CRM or email platform once, pick a source and a schedule, and RocketVerifier verifies the contacts and writes status, sub status, score, verified date and a Send, Review or Remove recommendation back to each one. Recently verified contacts are skipped for free, action rules tag, unsubscribe or move bad contacts, and destructive actions never touch catch-all or unknown results.

On this page

A CRM decays on its own: people change jobs, domains lapse and typos from old imports sit there until the next campaign bounces. A native connector verifies the contacts where they live and keeps them verified on a schedule, with no exports or imports.

How a sync works#

Each sync reads contacts from one source, verifies the ones that need it, and writes the results back.

  1. Read the source

    The connector reads the source you picked: all contacts, or one list, audience, segment, view or campaign, depending on the platform.

  2. Skip what is fresh

    Contacts verified within the skip window are left out and cost nothing. Contacts you verified recently anywhere else in RocketVerifier are written back from that result, also for free.

  3. Verify the rest

    The remaining contacts run as one bulk job, 1 credit per unique address. Unknown results are refunded when the job completes.

  4. Write back and act

    Results are written to fields or tags on each contact, then your action rules run. The run's report lands in the sync history, and an integration.sync.completed webhook fires.

Connect a platform#

Open Integrations in the dashboard and pick the platform. OAuth platforms send you to the platform to approve access; API key platforms validate the credentials against the platform before anything is saved. Then pick the source, the schedule and the write-back options, and click Sync now or wait for the schedule.

Each platform has its own page with the exact source types, field names and actions it supports:

Choose a schedule and sync mode#

The schedule decides how often the source is re-read; the sync mode and skip window decide which contacts are verified.

SettingOptionsRecommendation
ScheduleManual only, Daily, Weekly, MonthlyWeekly for active CRMs, Monthly for large, slow-moving lists
Scheduled sync modeFull (every contact, minus recently verified) or Incremental (changed since the last sync)Incremental for daily and weekly schedules, Full for monthly
Skip contacts verified in the last0 to 365 days, default 30Keep 30. 0 re-verifies everything and uses more credits.

Incremental syncs read only contacts created or changed since the last sync; the first incremental run reads everything. Under Re-checks and freshness you can also give each result type its own interval, for example re-checking valid contacts every 90 days and unknown ones every 7.

Quarantine uncertain contacts#

Turn on Quarantine and re-check uncertain contacts to re-verify risky, catch-all and unknown contacts automatically every few days (1 to 90, default 14). They carry the Review recommendation meanwhile, and each re-check moves them to Send or Remove once the answer is clear.

Alerts#

Alert me about spikes of bad emails sends an email when a sync, or the platform's new sign-ups, suddenly contain far more invalid addresses than usual. It is on by default.

Write results back#

Results land on each contact, where your team and your platform's own automations can use them.

Status fields hold the status, sub status, score, verified date and a recommendation. Field names depend on the platform: HubSpot properties such as rv_email_status are created automatically, and Salesforce uses RV_Email_Status__c style custom fields. You can map any of them to fields you already have.

RecommendationResults
SendValid
ReviewRisky, catch-all, unknown
RemoveInvalid, disposable

Status tags add a tag per result, with a prefix you choose, such as rv-status:invalid, on platforms that use tags.

Build segments and workflows on the recommendation field: one field, three values, the same on every platform.

Set action rules#

Action rules go beyond labels: for each result type (valid, invalid, disposable, risky, catch-all, unknown), choose what happens to the contact on the platform.

ActionEffect
Do nothingWrite fields and tags only
Add tagAdds the tag you name
Move to listAdds the contact to the list you pick
Pause in campaignsStops the lead in cold outreach sequences
UnsubscribeUnsubscribes or opts out the contact
Suppress (blocklist)Adds the contact to the platform's blocklist or suppression list
Delete permanentlyRemoves the contact from the platform

The actions offered depend on what each platform supports. Three safeguards apply to every rule:

  • Destructive actions are only for certain results. Unsubscribe, suppress and delete never apply to catch-all or unknown results, which are often real people or a timeout.
  • Preview before acting. With this on, results are written as usual but actions wait until you approve the run in the sync history. You get an email with the planned changes.
  • Undo and backups. Every run records each change it made. Undo this run reverses the actions the platform can reverse, and a CSV backup of each run's changes is kept for 90 days.

Start with Add tag for invalid and disposable contacts, check the tagged contacts once, then switch to unsubscribe or delete when you trust the rules.

Verify new contacts as they arrive#

On platforms that send new-contact events, such as HubSpot, Shopify, BigCommerce, Typeform, Jotform and Webflow, turn on Auto-verify new contacts. Each new contact is verified within moments of being created (1 credit each) and written back.

  • Also verify existing contacts once runs one full sync when you turn auto-verify on. Contacts verified recently are skipped.
  • Send an email.verified webhook for each new contact forwards each result to your own webhook, with source set to the platform.

Protect cold outreach campaigns#

On Instantly, Smartlead, lemlist, Apollo, Reply.io, Woodpecker and Outreach, the Campaign safety net checks campaigns every hour. It verifies leads newly added to campaigns, and every lead of campaigns not launched yet, and pauses or block-lists invalid and disposable leads before they are emailed. Each new lead costs 1 credit; leads already checked are free.

Feed bounces back#

Connect the platform you send through, SendGrid, Mailgun, Amazon SES or Postmark, and its hard bounces and complaints go straight onto your suppression list. With Import bounces daily, RocketVerifier also reads the platform's bounce feed once a day, in addition to real-time webhooks. With SendGrid, Mailgun and Postmark, every confirmed hard bounce of a deliverable result is refunded under the Bounce Guarantee.

Reuse settings across platforms#

Cleaning policies, on the Integrations page, save a schedule, sync mode, skip window, quarantine, alerts and action rules under one name. Apply a policy to several integrations at once, so every platform follows the same rules.

Next steps#

Frequently asked questions

Am I charged again for contacts that were verified recently?

No. Contacts verified within the skip window (30 days by default) are skipped, and contacts you verified recently in any other job are written back from that result for free. Unknown results are refunded.

Can a sync delete or unsubscribe a real person by mistake?

Destructive actions (unsubscribe, suppress, delete) only apply to results we are sure about, never to catch-all or unknown results, whatever rule you set. Turn on Preview before acting to approve each run's changes first.

Can I undo a sync?

Yes, for actions the platform can reverse. Every run records its changes, Undo this run reverses them, and a CSV backup of each run's changes is kept for 90 days, deleted contacts included.

Which platforms are supported?

More than 30, across CRMs, email marketing, cold outreach, sending platforms, ecommerce and forms, including HubSpot, Salesforce, Pipedrive, Mailchimp, Klaviyo, Brevo, Instantly, Smartlead, Shopify and Airtable. The integrations directory lists them all.

Updated 11 November 2026Suggest an edit