Move Validity Engage deliverability monitoring to Bird
Move the placement and reputation workflow while keeping the evidence your team uses to investigate a sending problem. Validity now presents these capabilities through Engage; include reports and workflows still named Everest in your inventory.
1. Map the monitoring responsibilities
List the sending domains, IPs, mailbox providers, reporting windows and alerts the team reviews. Separate placement testing, reputation monitoring, authentication and any other services in the existing agreement. This migration covers the monitoring work you can reproduce in Bird; retain other services until their requirements are addressed.
| Current responsibility | Receiving Bird workflow |
|---|---|
| Investigate placement by provider | Open Inbox Insights, choose the domain and inspect Placement by provider. |
| Review a sender reputation change | Open Reputation and inspect the available complaint, blocklist and authentication observations. |
| Test a particular campaign | Create a seed test using the domain, content and sending route under investigation. |
| Explain a delivery issue | Join the placement observation to Bird delivery, bounce and deferral records. |
Retain the original Sender Score reports with their provider and dates; Bird's reputation observations are not a conversion of that score. Inventory Engage's separate capabilities too: live link/image monitoring, rendering tests and Sender Certification need their own acceptance criteria. A successful placement test does not establish that those workflows have moved.
2. Establish the domain baseline
Verify each sending domain and enable it in Tracked domains. Use the same date window as the retained report. Record missing measurements explicitly; the absence of a measured problem does not establish a healthy sender.
The placement view separates seed and panel observations from your actual sending data. Keep that distinction in any report you share with the business.
3. Reproduce a campaign investigation
Choose a campaign for a domain whose placement changed. In Seed tests, create a new test, choose the available pool, engagement profile and regions, then obtain its addresses. Include them in the controlled send before the displayed expiry.
Compare the affected provider, cohort and time window. Different panels can produce different aggregate rates, so record the populations alongside the result instead of setting an acceptance target based only on matching the old headline percentage.
4. Move the team's operating process
Assign an owner for the Placement and Reputation review and record the investigation in the team's existing incident or campaign process. Validate each alert or report requirement separately before retiring the corresponding old workflow.
Retain prior reports for trend context. Review any certification, consulting or other contracted service independently; establishing the Bird measurement baseline does not transfer those services.
References and next steps
- Inbox Insights
- Domain authentication
- Dedicated-IP warmup
- Validity Engage documentation
- Compare Bird and Validity Engage
- All migration guides
- Email deliverability resources
- Email pricing
- Start now
- Talk to sales
Recursos relacionados
Continúa con la documentación, guías y ejemplos sobre este tema. Los recursos están en inglés.
Ver la guíaGetting started with emailExplorar la funcionalidadEmailSeguir la ruta de aprendizajeBuild your first integrationGuía de implementaciónSend your first email
Prueba el ejercicio y obtén un resumen de implementación