Set up provider delivery callbacks
Use delivery callbacks to update notification history when your provider confirms delivery or a bounce.
How to use it
- In Notifications, select your channel and sending provider, then enter the required account and sender details.
- Expand Delivery callbacks. Enter the provider’s signing key, verification key or authentication token listed below, then choose Verify and connect.
- After saving, copy the current callback address shown by PrepMyGifts into the provider’s webhook settings. Use the same authentication value where the provider requires it.
- Send a test to a destination you control. Refresh Delivery history and check that a delivery or bounce event appears.
What to know
Saving a new connection changes its callback address. Copy the address after saving and update it with the provider whenever you reconnect. Keep signing keys and tokens private.
For Brevo or Postmark, use a token that you can configure as Authorization: Bearer in the provider’s webhook. Postmark also supports Basic authentication with username prepmygifts and that token as its password. If the account cannot set the required authentication, final-delivery callbacks are unavailable.
Klaviyo and Omnisend record event acceptance in the app. Check the sending platform for final email delivery; the app does not provide their native final-delivery confirmation.
Which authentication value to use
| Provider | Value for Delivery callbacks |
|---|---|
| Resend | Webhook signing secret |
| SendGrid | Event Webhook verification public key |
| Mailgun | Webhook signing key |
| Mailchimp Transactional | Mandrill webhook signing key |
| Brevo / Postmark | Your configured callback authentication token |
| Twilio | Your account auth token is used for verification |
What happens next
Authenticated events update the delivery status when the provider and connection support them.
Still need a hand? Contact support below.