Placement Testing to Corrective Actions Workflow
Run a placement test that returns useful data, identify which failure type triggered the low score, execute the correct fix for that specific cause, and confirm with a re-test before the next campaign send.
Before You Start
What you will build and what you need first
Output: A repeatable placement test and corrective action loop: a test run on the actual campaign template, a result read against a four-type failure taxonomy (authentication, reputation, content, list hygiene), a specific fix executed per failure type, and a confirmation re-test before campaigns resume. The loop closes when the re-test returns Gmail and Outlook placement above 85%.
Time required: 15 to 20 minutes to run a test and read the result. Corrective actions range from 10 minutes (authentication record correction) to 7 to 14 days (reputation recovery through warmup). The re-test adds another 15 minutes. Plan the total time based on which failure type the first test reveals.
At least one placement testing tool account with test credits available (GlockApps, MailReach, or Folderly Inbox Insights). Access to the DNS records for the sending domain. Access to the sending platform to pause campaigns and adjust send settings. The actual email template planned for the campaign, including real subject line, body copy, signature, and any links. A log document to record test results and corrective actions taken over time.
Workflow Overview
The 6-step placement testing to corrective actions loop at a glance
| Step | Action | Tool | Output |
|---|---|---|---|
| 1 | Run placement test using actual campaign template | GlockApps / MailReach / Folderly | Gmail placement %, Outlook placement %, spam filter scores per provider |
| 2 | Classify the failure type from test results | Test result + failure taxonomy | One of four failure types identified: authentication, reputation, content, or list hygiene |
| 3 | Pause active campaigns on affected domain | Sending platform (Smartlead / Instantly) | All outbound sends on the failing domain cluster paused before next batch goes out |
| 4 | Execute the corrective action for the identified failure type | DNS editor / Warmup tool / Content revision | Root cause addressed; corrective action logged in placement record |
| 5 | Wait the required recovery period per failure type | Calendar | Sufficient time elapsed for the fix to propagate (minutes for auth, days to weeks for reputation) |
| 6 | Re-test and confirm placement above threshold before resuming | GlockApps / MailReach / Folderly | Gmail and Outlook placement confirmed above 85%; campaigns resume |
Step by Step
Complete placement testing to corrective actions workflow
- Run the placement test using the actual campaign template
Open GlockApps or MailReach and create a new test using the real email you plan to send: actual subject line, actual body copy, real links, real signature, and real sender domain. Do not substitute a clean test message. Send it from the inbox you intend to use for the campaign. Record the Gmail inbox placement percentage, Outlook inbox placement percentage, spam score per filter (Google, Barracuda, SpamAssassin), and any content warnings flagged by the content analysis module. Log all four data points in the placement record before moving to the next step.
- Classify the failure type using the four-type taxonomy
Every placement failure traces to one of four causes. Authentication failures show up as SPF, DKIM, or DMARC errors in the test result and often affect both Gmail and Outlook simultaneously. Reputation failures show high spam rates with no authentication errors and are often provider-specific (Gmail failing while Outlook passes, or vice versa). Content failures appear as high SpamAssassin or Barracuda scores with specific content flags (link count, HTML weight, subject line patterns). List hygiene failures are not visible in the placement test itself but appear as high bounce rates in the sending platform alongside the low placement score. Identify which type applies before choosing the corrective action.
- Pause active campaigns on the affected domain cluster immediately
In Smartlead or Instantly, pause all active campaigns sending from the affected domain before the next batch goes out. A placement score below 85% means a significant share of the emails already in the queue will land in spam. Continuing to send while diagnosing compounds the reputation damage. Pausing takes 30 seconds and prevents the problem from worsening while the corrective action is executed.
- Execute the corrective action matched to the failure type
For authentication failures: open the DNS editor at the domain registrar, verify the SPF record includes the sending platform's mail servers, confirm the DKIM TXT record matches the selector the platform is signing with, and check that the DMARC record is syntactically valid. Authentication changes propagate in minutes to a few hours. For reputation failures: increase warmup intensity on the affected inbox, reduce daily send volume by 50%, and check the domain against GlockApps' 50+ blocklist monitors or Bouncer's Deliverability Kit. If the domain is blacklisted, request removal from the relevant list before resuming. For content failures: revise the email template to reduce link count (maximum two to three links), reduce HTML weight, and simplify the subject line. Remove any phrases that GlockApps' content analysis or Mail-Tester flags as spam triggers. For list hygiene failures: run the contact segment through a verification tool, separate catch-all addresses into a lower-volume inbox cluster, and suppress any hard bounce addresses from previous sends before re-loading the campaign.
- Wait the required recovery period per failure type before re-testing
Authentication fixes propagate within minutes to a few hours. Re-test after 2 hours, not immediately. Reputation recovery through increased warmup takes 7 to 14 days of clean engagement signals before placement meaningfully improves. Blacklist removal takes 24 to 72 hours after the removal request is submitted and processed by the list operator. Content fixes apply immediately on the re-test because placement tests evaluate the template sent in the test, not historical emails. Do not resume campaigns until the re-test confirms the threshold is met.
- Re-test with the corrected template and confirm placement above threshold
Run a new placement test using the revised template after the recovery period. Gmail and Outlook inbox placement must both read above 85% before campaigns resume. If one provider passes and the other fails, the failure type for the second provider may differ from the first. Treat each provider's score as a separate diagnostic signal and check the failure taxonomy again for the failing provider. Log the re-test result and the date of the corrective action in the placement record so the pattern is visible if the same domain fails again in three to four weeks.
Teams identify the failure type, execute the fix, and then resume campaigns without running the confirmation re-test because the fix "should have worked." A 30-second authentication change may not have propagated yet. A warmup period may not have fully offset the reputation damage. The re-test is not optional. It is the confirmation that the corrective action was effective, not an assumption that it was. Resume campaigns only after the re-test result is logged and both provider scores are above threshold.
Failure Type Reference
Quick reference: failure type, diagnostic signal, corrective action, and recovery time
Each failure type has a distinct diagnostic signal in the test result and requires a different corrective action. Matching the action to the failure type is the step that most operators skip, defaulting to "increase warmup" as a generic response regardless of the actual cause.
| Failure type | Diagnostic signal in test result | Corrective action | Recovery time |
|---|---|---|---|
| Authentication | SPF / DKIM / DMARC error flagged in test output; often fails both Gmail and Outlook simultaneously | Correct the failing DNS record at the domain registrar; verify with a fresh auth check after 2 hours | Minutes to 2 hours (DNS propagation) |
| Reputation | High spam rate with no auth errors; often provider-specific (Gmail fails, Outlook passes, or vice versa); Sender Score low | Check blacklist status; request removal if listed; reduce daily send volume by 50%; increase warmup intensity | 24–72 hours for blacklist removal; 7–14 days for reputation recovery |
| Content | High SpamAssassin or Barracuda score; content analysis flags specific triggers (link count, HTML weight, subject line pattern) | Revise the template to remove flagged elements; reduce links to 2–3 maximum; simplify HTML; test subject line variants | Immediate on re-test (content changes apply to next test) |
| List hygiene | Placement test result may look clean but sending platform shows high bounce rate alongside the low engagement; catch-all segment sending at risk | Verify the contact segment; suppress hard bounces; route catch-all addresses to a separate lower-volume inbox cluster | Immediate for future sends; reputation recovery for affected domain takes 7–14 days |
A domain that appears on a major blocklist (Spamhaus, Barracuda) has near-zero inbox placement for recipients whose mail servers check that list. Increasing warmup volume on a blacklisted domain generates more sends into spam, which compounds the reputation damage. The correct sequence is: pause campaigns, confirm the blacklist entry using GlockApps or Bouncer's Deliverability Kit, identify and remediate the cause (bad list segment, authentication failure, spam complaint spike), submit a removal request to the relevant list, and wait for confirmation of removal before running the re-test and resuming sends.
Common Failures
Where this workflow breaks and how to fix each breakdown
The most common failure in this workflow is not a tool misconfiguration. It is applying the wrong corrective action to the failure type because the test result was not read carefully enough before the fix was chosen.
Tools
Tools that support the placement testing to corrective actions workflow
The testing layer (GlockApps, MailReach, Folderly) produces the result data. The authentication check layer (Bouncer Deliverability Kit, Mail-Tester) validates DNS records and blocklist status. The warmup layer (MailReach, Warmbox) executes the reputation corrective action. The sending platform (Smartlead, Instantly) is where campaigns are paused and volume is adjusted during the recovery period.
Workflow documented. Now compare the placement testing tools.
Compare the best inbox placement testing tools by seed list size, filter coverage, automation features, and pricing per test.