Adobe Experience Cloud
A Marketo template preview needs an email and a test profile
Restore a reliable proofing path in the new Marketo Email Designer when a template cannot send a sample directly.
November 8, 2026
A Marketo user building in the new Email Designer asked where the old template-level Send Sample action had gone. Replies describe a longer route: make an email from the template, simulate content with a database test profile, then send a proof to a chosen inbox. The recipient address and the profile supplying personalization are separate things. A screenshot of the template alone will not test either.
Separate template review from delivered proof
Keep the reusable template under design review, but create a disposable email asset for the actual proof. Use a controlled test profile whose fields exercise ordinary and missing-data paths. In Simulate content, inspect both the default and personalized variants before entering the proof recipient. Adobe's Email Designer guidance places proofing inside email authoring, while its feature comparison lists send sample or proof support; it does not establish that the old template shortcut is still present.
Make the extra steps auditable
Record the template version, derived email asset, selected test profile, proof inbox, and received message. Check rendered content, links, unsubscribe handling, and tokens in the delivered email. The community thread says proof addresses are added one by one and not retained for the next test; verify that behavior in your own tenant and keep a small checklist rather than relying on memory. Do not send a live campaign just to test a template.
Decide what to standardize
If teams build many templates, designate a test program or naming convention for temporary proof emails and clean them up after approval. Capture the time spent per proof and submit a product idea if the missing shortcut materially delays release. The acceptance criterion is an actual message received under representative personalization, not a green preview screen.
Adovo’s view
Proof is an operational contract: the recipient sees what the system will send, under a known profile. If the designer adds steps, make those steps repeatable. Speed matters, but a fast preview that misses personalization is false confidence.
