How to reduce spam placement with Zalify Reach

Open Email settings → Sender domain, then open the domain you actually use to send.

1. Add the DNS records shown on that page at your DNS provider. Copy their exact types, names, and values instead of borrowing records from another store or tutorial.
2. Check DKIM and MAIL FROM separately. Reach uses both for sending verification; a successful DKIM check alone can leave setup incomplete.
3. If the page provides tracking or branded-link records, configure those too and review their separate verification status. Sending verification and branded-link verification are distinct.
4. After updating DNS, use the page's verification action to check again. Preserve records needed by your other email services.

Ask your domain administrator to check DMARC as well. Google's bulk-sender requirements include SPF, DKIM, DMARC, and alignment of the From domain with SPF or DKIM. A Reach verification badge does not replace checking the authentication of an actual message. Google sender requirements.

Send a small live broadcast to subscribed test addresses you control. In Gmail, use Show original to inspect SPF, DKIM, and DMARC results. A live broadcast helps check the actual sending identity and headers; an editor test is primarily useful for reviewing content and layout.

Use a recognizable brand name, a consistent address for the same kind of marketing, and a reply address someone monitors. Resolve authentication problems before expanding the audience.

A purchase, site visit, or imported email address does not establish marketing consent. Start with people who expect this message.

In Reach's customer lists and segments area, create a segment using Email subscribers who viewed a product. Name it “Subscribed · viewed product in 30 days” and check that these conditions are combined with AND in the same group:

Save, inspect the members and sendable count, then select this segment as your broadcast audience. Thirty days is an example window, not a deliverability standard. Adjust it to your buying cycle and usual cadence.

This segment depends on product-view events being collected and associated with contacts. A migration may not include historical activity. If membership is empty, check the event data instead of removing the consent condition. Without activity data, start with a small list of recent, explicit signups from a known source.

Do not put consent and activity into separate OR groups: that can admit people who do not satisfy both. See Lists and segments.

For a new sending domain, a platform change, or a restart after a long pause, avoid making your entire historical database the first audience.

1. Validate internally. Send a small live broadcast to subscribed Gmail, Outlook, and other test addresses you control. Check authentication, folder placement, links, and unsubscribe behavior.
2. Send to recently active subscribers. Use the segment above. If it is much larger than your normal audience, narrow the activity window or limit membership to a relevant source list.
3. Review before expanding. For example, review the report after 24–48 hours. That is an operational checkpoint, not a promise that all complaints have arrived. Expand only after checking bounces, complaints, and recipient feedback.
4. Stop expanding when problems appear. Reschedule broadcasts that have not sent while you investigate. Repeatedly resending is not a recovery strategy.

This is a manual broadcast and review workflow, not an automatic Reach warm-up setting. There is no universal “double every day” schedule. Include welcome emails, other automations, and campaigns from other platforms when planning how much mail the same people receive.

In the Reach editor, check whether recipients can recognize you, understand the offer, and act on it.

• Match the subject to the content. A new-collection announcement should lead to that collection. Do not disguise promotions as receipts or use a fake Re: to imply an existing conversation.
• Keep essential information in live text. Offer terms, expiry dates, and instructions should remain understandable when images do not load.
• Check every destination. Open product links and buttons, including their redirects and mobile pages. Avoid unnecessary short links and redirect chains.
• Show your brand and address clearly. Check that {{ company_address }} renders correctly, and maintain the address in Brand Kit.
• Review desktop and mobile. Inspect the subject, preview text, personalization, and missing values so raw template tags do not reach customers.

There is no guaranteed image-to-text ratio or single “spam word” whose removal repairs a sending reputation. Review content alongside authentication and audience quality.

Keep a visible unsubscribe link in the footer. Use *|UNSUBSCRIBE_URL|* as its link destination, rather than simply displaying the tag as text.

Reach's marketing sending flow generates a recipient-specific unsubscribe URL and adds one-click unsubscribe headers. The footer link and header-based unsubscribe are separate mechanisms. Keep the footer link and check the headers in a live test message. The mailbox provider decides whether to show a top-level unsubscribe button.

Complete an unsubscribe with a dedicated test contact, then inspect its subscription status. Do not test with a real customer's link, or delete, re-import, or move contacts between lists to bypass unsubscribes or suppression.

Remove long-inactive contacts from frequent promotions. Consider a low-frequency preference check only when consent remains clear and the source is trustworthy; stop routine marketing to those who do not respond. An unknown old list is not a suitable audience for a repermission blast.

Open the sent broadcast's report and use the Email Activity feed to investigate individual contacts. Compare with recent campaigns sent to similar audiences.

Privacy preloading can affect opens, and security scanners can generate clicks. Interpret both alongside site behavior; do not repeatedly resend to everyone labeled “unopened.”

For Gmail, also investigate in Google Postmaster Tools. Google recommends a user-reported spam rate below 0.1%, avoiding 0.3% or higher. That metric is not interchangeable with a Reach campaign complaint ratio, and a low or missing value does not guarantee inbox placement. Google's official guidance.