Loxo email deliverability: check pacing, tracking and the route

Find the affected account and message type

Record the mailbox, campaign or automation and the message time. Keep expected correspondence separate from broad outreach. Check whether the symptom is an error, a pause, recipient-confirmed spam placement or simply low replies.

Those distinctions help you choose between investigating the connection, sending controls, message authentication or campaign relevance. Don’t change all of them before saving the starting evidence.

Review sending safety with an administrator

Loxo’s email preferences documentation describes account-level email settings and requires administrative permission for the safety controls. It explains a range of pacing/risk options and warns that the higher-volume options can harm domain health.

Ask the administrator which setting was active when the affected campaign ran and whether it changed recently. Record any pause or throttling message. Don’t move a control towards higher volume just to make a queue disappear.

If a campaign needs to resume, understand its queue and recipient data first. A repeat of the same burst may be a poor verification step.

Treat tracking as a measurement choice

Loxo’s current preferences guidance warns about tracking accuracy and potential deliverability implications. That is a reason to understand the setting and compare evidence, not proof that tracking caused your particular problem.

Record whether open, click or download tracking was enabled. If you make a controlled comparison, change one relevant setting and keep the route, message and time recorded.

Don’t use a high recorded open rate as proof that candidates saw and ignored the message. Read what delivery and open metrics mean before drawing that conclusion.

Inspect the original evidence

For a bounce, save the whole non-delivery report. For a confirmed spam-folder message, ask for the original received-message header. Have the responsible administrator identify the actual sending route and trusted authentication results.

Our header explainer reads the reported outcomes locally. It does not connect to Loxo, verify a signature or check your current DNS records.

Do not assume that every sending account uses a generic record you found online. Use the configuration issued for the actual connection and feature.

Review the contact list and sending pattern

An old candidate database can contain addresses that no longer work or people for whom the message is no longer relevant. Review the source, age and purpose of the segment before resending.

Keep opt-outs and suppression rules intact. A valid address is not the same as an interested recipient. Authentication, pacing and contact relevance answer different questions.

If the problem follows a recent campaign change, record that observation. If it affects every expected message too, tell support that the scope is wider.

Use a test for the remaining question

A controlled placement test can help compare how a particular message is treated in the test service’s accounts. Use the actual affected route and avoid real candidate details. Read the testing guide before treating a score as an audience-wide outcome.

For support, provide the mailbox, campaign or automation, time, relevant settings, exact error if any and one example. The IT handoff builder creates a useful brief without uploading it.