Skip to content →
Verifier
  • Integrations
  • Security
  • Pricing
Log inGet started

From a raw listto a safe send.

Get started free

No email is sent during a check. The free plan includes 100 checks a month.

Verifier

Product

Email verificationWeb workspacePricingIntegrationsChangelog

Features

Single checksFind emailList cleaningScores and reasonsDelivery feedbackSuppression listOngoing re-checksAPI and SDKsTeam workspace

Use cases

Email marketingMarketing operationsSignup formsPlatforms and agencies

Resources

Resource hubGuidesBlogSecurity

Company

ContactPrivacyTermsResponsible disclosure
Verifier

© 2026 Oppulence Engineering · Verifier

Features/05 of 09/Delivery feedback

Learn from what actually bounced

Connect SendGrid, Mailgun, Postmark, or Amazon SES. Bounces, complaints, and unsubscribes come back and update your suppression list.

Get started freeSuppression list
Fig. 1A day of delivery events
0006121824BOUNCE · SENDGRIDCOMPLAINT · MAILGUNUNSUBSCRIBE · POSTMARKLAST 24 H
Platforms
SendGrid, Mailgun, Postmark, Amazon SES
Any other platform
POST /v1/outcomes
Suppressed
Bounces, complaints, unsubscribes
Delivery
A private webhook URL

§ 1

Why it matters

Bounces repeat when nobody closes the loop

When a bounce stays inside the email platform, the same bad address comes back in the next import.

A check tells you what should happen. Delivery feedback tells you what did happen.

Fig. 2Without and with Verifier
WithoutWith Verifier
  1. ×Without: Bounces stay in the email platform.→✓With Verifier: Bounces, complaints, and unsubscribes come back to one workspace.
  2. ×Without: The same address comes back with the next import.→✓With Verifier: Each of these events adds the address to the suppression list.
  3. ×Without: Each platform needs its own cleanup step.→✓With Verifier: One endpoint takes events from any platform.

§ 2

How it works

Your email platform reports back

Add a webhook in your email platform that points to your workspace. Each delivery event is matched to the address and recorded.

  1. 2.1Create a delivery endpoint in your workspace.
  2. 2.2Paste its private URL into your email platform's webhook settings.
  3. 2.3Bounces, complaints, and unsubscribes update your suppressions.
Fig. 3Events from any platform

POST /v1/outcomes

{  "provider": "custom",  "outcomes": [    { "email": "[email protected]", "event_type": "bounced" },    { "email": "[email protected]", "event_type": "delivered" }  ]}

Response

{  "ingested": 2,  "auto_suppressed": 1,  "ignored": 0}
Bounces, complaints, and unsubscribes are suppressed
Fig. 4Delivery feedback

6.1 Email platform

  • SendGrid
  • Mailgun
  • Postmark
  • Amazon SES

6.2 Verifier

  1. 01Bounce events
  2. 02Complaints
  3. 03Unsubscribes
  4. 04Suppression list
  5. 05Scheduled re-checks
  6. 06Clean export files

6.3 Next send

1,447

Addresses skipped

Sent · 46,766

Skipped · 1,447

Your platform reports the bounce · the address goes on your suppression list · your next send skips it

§ 3

What you get

What you get.

  1. 3.1Signed and privateEach endpoint has its own private URL. SendGrid, Mailgun, and Amazon SES events are signature-checked.
  2. 3.2Any other platformSend delivery events from any tool through the outcomes API on Professional and Enterprise. On every plan, you can add an event in the app.

Table 3 · Delivery events

EventRecorded in historySuppression
deliveredYes—
bouncedYesAdded, reason bounce
complainedYesAdded, reason complaint
unsubscribedYesAdded, reason unsubscribe
openedYes—
clickedYes—

§ 4

In practice

Typical uses.

  • Case 4.1

    Stop repeat bounces

    An address that bounced last month is suppressed before the next campaign.

Works with the tools you send from.

All integrations
  • SendGrid
  • Mailgun
  • Postmark
  • Amazon SES
  • CSV files
  • REST API

Questions

Before you start.

Which events are suppressed?

Bounces, spam complaints, and unsubscribes.

Continue reading

  1. 01Suppression list
  2. 02All integrations
  3. 03Start free