After changing link or image domains in Elastic Email messages, inspect a fresh generated copy and test the affected behavior separately from mailbox placement. A verified tracking domain does not prove that every image uses that domain, and a working image does not establish primary Inbox delivery. Keep the changed hostnames explicit in the comparison.
Inventory the domains by purpose
List the visible sender domain, authentication identities, tracked-link hostname, final landing-page host and image hosts. Include logos, product pictures, background images and any tracking pixel. These serve different purposes and may be configured in different places.
Elastic Email documents rewriting links for click tracking and using an image pixel for open tracking. Its domain-verification guide describes branding rewritten links through a tracking domain. Do not infer from that setting alone that externally hosted content images were moved or that old links were updated.
Preserve the old configuration and copy
Save the old template's rendered HTML and text alternative with a known send time. Retain safe DNS and account configuration references, and record which domain change is authorized. Avoid logging recipient-specific tracking tokens in a public report.
Define the comparison clearly. Replacing both the tracking host and all product-image hosts at once evaluates a package of changes. If the hypothesis concerns only the tracking host, keep image URLs stable. If several changes are operationally required, document them and limit causal claims accordingly.
Verify links and assets before placement
Check the intended hostname resolution and secure connection, then inspect a freshly generated message. Follow representative links to confirm the correct final page and examine image URLs for accessibility and expected content. A browser-cached image is not sufficient evidence that an unauthenticated recipient can load the asset.
Review alternative text and the message with remote images unavailable. Required meaning and essential action instructions should remain understandable. A broken image can reflect an asset or client setting rather than a spam classification, so keep visual findings separate from folder observations.
Consider existing messages that still contain old URLs. Do not remove old infrastructure without understanding how recipients will reach those links and images. A new message test does not verify every previously sent message after a domain migration.
Observe a fresh original through the actual route
Create an LDM test for the intended sender and use the current recipient addresses for that run. Generate an original through the affected Elastic Email campaign or application path, with the same safe data, subject, sender, signature and tracking switches except for the intended change.
Record the template version, actual hostnames, submission timestamp and available message references. Keep temporary recipients outside continuing campaigns, scheduled jobs and unrelated automations, then stop the bounded test. This article changes no setting, sends no email and assumes no native LDM connection.
Compare the right outcomes
Record asset loading, final navigation, available tracking evidence and observed folder independently. Open events depend on tracking behavior and image handling; they do not directly measure primary Inbox placement or prove human readership. A missing open event is not proof that a copy reached Spam.
For mailbox observations, preserve recipient, location and measurement time. Keep missing copies separate from confirmed Spam and reconcile them with sender evidence. A small panel cannot establish that a new domain universally improves placement or reproduce every recipient's cached assets, rules and history.
Frequently asked questions
Does changing the tracking domain move my product images?
Do not assume so. Inspect the actual source URLs in a fresh generated message and verify each affected asset host.
Can I validate the new domain using an old email?
That examines the old copy's stored URLs. Use a fresh message to establish new-generation behavior, while separately checking compatibility for old links.
Does no open event mean no delivery?
No. Image and privacy behavior can affect tracking. Use transport evidence and mailbox observation to investigate delivery and placement separately.
Official references
Reviewed 2026-11-05; no domain migration or placement improvement is claimed.