What is probably happening
Authentication is incomplete or not aligned
SPF, DKIM, DMARC, return-path and sender identity need to align with the domain reputation you are trying to build.
The list or sending pattern looks risky
Cold lists, sudden volume spikes, low engagement, bounces and complaints can damage deliverability even when DNS looks correct.
The message triggers filtering or low engagement
Generic offers, heavy links, poor personalization and weak reply intent can push campaigns toward spam or promotions folders.
Compliance signals are missing
Unsubscribe, sender identity, domain reputation and regional requirements matter more as mailbox providers tighten enforcement.
How to check it without breaking anything
Verify SPF, DKIM, DMARC alignment, return-path, bounce domain and one-click unsubscribe.
Separate authentication, reputation, list quality, content and sending cadence issues.
Check Gmail/Yahoo sender requirements, complaint rate, bounces and warm-up history.
Define the exact symptom and the date when it started.
Compare ad platform, analytics, CRM, ecommerce or backend data before assuming the cause.
Review status, eligibility, policies, budget, bidding, targeting, measurement and recent changes.
Check consent, tags, events, identifiers and deduplication when conversions are involved.
Separate what is confirmed by data from what is still a hypothesis.
How I would solve it step by step
Validate DNS and sender alignment first
Check SPF, DKIM, DMARC, return-path, tracking domain and From-domain alignment before changing copy or volume.
Segment the list by risk and intent
Separate verified high-fit contacts from older, cold or enriched records so warm-up and messaging can be controlled.
Reduce friction and increase reply intent
Use plain, relevant copy with a clear reason to reply instead of pushing every contact through the same promotional sequence.
Monitor deliverability as a system
Track bounces, spam complaints, opens, replies, domain reputation and mailbox placement together; no single metric is enough.
If it gets technical
You can follow this path yourself. If the diagnosis reveals a strange data mismatch, a delicate tracking setup, a risky bidding decision or a blocker that needs account access, Lia keeps this context and brings it to CreatikLab so you do not start from zero.
Take this context to LiaWhat I would not do
Changing budget or bids before understanding the cause.
Confusing missing data with a real absence of sales or leads.
Publishing or scaling a fix from one screenshot.
Ignoring recent changes in the website, CRM, checkout, feeds, consent or tracking.
Frequently asked questions
Can I solve this without help?
Yes, if you can follow the diagnostic sequence and validate each layer with data. If the case mixes tracking, bidding, feeds, CRM or policy, a specialist review is safer.
When should I talk to Lia?
When the symptom does not fit, the data contradicts itself or you need to turn several screenshots and metrics into a clear decision.
Why does this page exist?
This topic combines 4 source(s) or signal(s) already registered in AGOS. The page should help first, then route to Lia if the case needs specific context.
