Services
An email deliverability audit before your next campaign.
Find the data and sending risks that should shape your next email decision. EngageMKTG reviews the evidence across list health, permission, authentication and suppression, then organizes the findings into a practical next-step plan.
Updated
Who this is for
Email operations teams facing a sudden change. An open-rate drop after a campaign to an old segment is a reason to investigate, rather than immediately change every template. Bring the sending history, recent changes and provider error messages so the review can separate authentication failures, audience quality and measurement noise.
Lifecycle teams with a failing Compliance status. Passing SPF or DKIM somewhere is different from passing and aligning across every stream. A support tool, CRM or legacy automation may send from the same domain. The audit considers the actual From domain, sending systems, unsubscribe mechanics and available provider evidence together.
Teams preparing a dormant-list program. An old address can be technically valid while permission, relevance or delivery history makes it unsuitable for revival. Before asking how much revenue might be recovered, establish which records remain eligible and which must stay suppressed. A planning estimate is useful only when its assumptions are visible.
What you get
The free List Health Audit and the paid Data & Deliverability Audit answer different questions. The free offer on List Revival provides an initial list-risk and opportunity view. The paid review adds the agreed sending, authentication, consent and suppression scope; it is not a promise that every account will require the same work.
Scroll for more →
| Deliverable | Format | When |
|---|---|---|
| Bounce, trap-risk and dead-domain findings | List-health findings and risk map | Initial data review |
| Dormancy map and domain risk score | Cohort and domain summary | Baseline review |
| Recoverable-revenue estimate | Scenario with explicit assumptions | After eligibility review |
| Authentication and alignment review | SPF, DKIM and DMARC findings by sending stream | Technical review |
| One-click unsubscribe review | Header and visible opt-out findings | Technical review |
| Spam-rate exposure by segment | Available provider and campaign evidence | Risk review |
| Consent and suppression reconciliation | Gaps, conflicts and recommended exclusions | Before a sending recommendation |
| Prioritized next-step plan | Health score, readiness assessment and actions | Read-out |
These deliverables establish a baseline for the agreed review. The paid audit's delivery formats and turnaround are agreed during discovery; no fixed paid-audit turnaround is published here. A trap-risk scan cannot certify every address as safe, and missing campaign or consent evidence remains a documented gap.
How it works
- Define the question and data boundary. Identify the affected brands, domains, systems and audience. Agree which records and evidence are needed, who can supply them and what the review is meant to decide. Avoid expanding a narrow incident into an unnecessary migration.
- Establish the baseline. Review address risk, dormancy, recent sending, permission records and suppression state. Keep the original cohort available for comparison so removing records does not make every later percentage appear to improve automatically.
- Inspect the sending path. Check authentication and alignment, marketing unsubscribe headers and available Gmail, Yahoo and Outlook responses. A provider rejection and an inbox-placement concern are different findings and call for different next actions.
- Prioritize remediation. Separate issues that require a pause from issues that need monitoring or better measurement. Assign an owner to each action. The report should explain which evidence supports the recommendation and what cannot yet be concluded.
- Choose the next bounded step. That may be repairing authentication, reconciling suppressions, improving data mapping or testing an eligible revival cohort. A paid audit does not automatically enroll a list in a sending program.
The public 72-hour timing belongs to the free List Health Audit. If an eligible list proceeds to the Revival Sprint method, its separate scope uses a 30-day stream and a 45-day read-out. Those numbers do not establish a paid audit delivery promise; the paid review's schedule must be agreed in its scope.
What it costs
Scoped after a discovery call. Scope depends on list size, the number of ESPs and the systems supplying consent and suppression records. The free List Health Audit is a separate $0 offer; the agreed paid scope covers the additional sending-path review and prioritized remediation plan.
What we don't do
We do not use an audit as permission to send to purchased lists, bypass an unsubscribe or blast an old database. Findings do not guarantee inbox placement, a lower complaint rate or recoverable revenue. A valid address is not proof of consent, and a lower denominator is not proof of a successful campaign. Any later revival or managed operations work needs its own eligibility checks, scope and published terms.
FAQ
What's the difference between the free List Health Audit and the paid audit?
The free audit is an initial view of list health, dormancy and potential opportunity. The paid review includes the agreed authentication, alignment, unsubscribe, consent and suppression checks and a prioritized remediation plan. The scope should state which systems and evidence are included.
Do I need to give you ESP access?
The required evidence and access are agreed before the review. Do not send account passwords through a form; identify the platform and the problem first. A data or access gap should be recorded rather than filled with an assumption.
Does the audit cover Outlook and Yahoo as well as Gmail?
The review considers the sender requirements and available response evidence for all three providers. Google Postmaster Tools is Gmail-specific, so it cannot independently establish Yahoo or Outlook delivery. Provider errors, message headers and the sending history remain part of the investigation.
How long does it take?
The free List Health Audit has the published 72-hour timing. The paid audit schedule is agreed after its data and system scope is known. It should not be presented as a 72-hour paid engagement without an approved delivery commitment.
What happens if you find a 550 5.7.515 or spam-rate problem?
An authentication rejection calls for authentication and alignment repair before another send. A complaint problem calls for pausing risky traffic and checking cohort quality against the provider guidance. The next action follows the actual failure, rather than a generic instruction to warm up faster.
Will you send a reactivation campaign during the audit?
An audit is a review and recommendation step. Sending is a separate decision after eligibility, consent, suppressions and stop conditions have been checked. A revenue estimate is a planning scenario until a controlled program measures the result.
Read before you buy
- Sender requirements side by side: compare authentication, unsubscribe and complaint requirements across providers.
- Emails suddenly going to spam: work through the diagnostic tree before changing the wrong part of the system.
- Google Postmaster Tools v2: understand what Gmail's dashboards show and where their evidence stops.