Move GlockApps seed testing to Bird
Recreate a campaign placement test in Bird while keeping the sending conditions comparable. GlockApps uses its own test identity and seed addresses; start a new Bird test instead of reusing those values.
1. Keep a reference test
Retain the campaign content, sending domain, sending route, test time and provider-level results. Note the selected filters and any separate link or content checks you used. The receiving workflow must satisfy the decisions those checks supported, not just produce another overall percentage.
In GlockApps' manual workflow, the test ID goes in the message and the seed list reflects the selected providers. Save the report and original message before changing either. Keep spam-filter and link-check results labelled separately from mailbox placement.
2. Create the Bird seed test
Verify the domain, open Inbox Insights and choose Seed tests. Select New test, then choose an available seed pool, engagement profile and regions. Obtain the addresses and include them in the same kind of send you use for customers, before the displayed send-by date.
Creating the test registers it; there is no separate run command. The test observes the message sent to its addresses. Use the test's own addresses and settings rather than carrying GlockApps identifiers into the Bird workflow.
3. Compare the measurements
| Observation | How to compare it |
|---|---|
| Inbox or spam placement | Compare the same mailbox provider and explain differences between the seed populations. |
| Gmail categories | Inspect the measured category split separately from SMTP acceptance. |
| Authentication | Review the SPF, DKIM and DMARC results on the actual tested send. |
| Missing result | Check that the seed was included, the message was sent and the observation window is appropriate. |
Keep any required content-filter or link-checking workflow until you have verified its replacement. A placement measurement alone does not prove those separate checks ran.
4. Diagnose before changing the sender
If the provider result worsens, inspect Bird delivery and deferral records, domain authentication and the Reputation view. Keep an unsent or unobserved test separate from an observed spam placement.
Change one diagnosed factor, then repeat the controlled test. Record the campaign and test references so another operator can reproduce the investigation.
5. Switch the campaign review process
Move the team to the new pre-send checklist once a representative campaign and a failing case have been investigated successfully. Retain the old reports for comparison. Changing the test platform does not require moving the production sender at the same time.
References and next steps
- Inbox Insights
- Domain authentication
- Dedicated-IP warmup
- GlockApps documentation
- Compare Bird and GlockApps
- 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