Applies to: the Send Test and Export buttons in the template builder
Ampemail builds the email; your own sending platform sends it. This article covers checking a template and getting it out of Ampemail.
Interactive components only behave properly in a real inbox. A browser preview cannot show you whether the AMP version renders, so always send a test before a campaign.
Click Send Test in the builder.
Enter one or more email addresses, separated by commas, semicolons or new lines.
Send.
Saved email groups. If you always test to the same handful of people, save the list as a group and pick it from the dropdown next time instead of retyping.
Test email allowance. Each plan includes a number of test emails per billing period. If a send would exceed it, you will be told how many you have used and how many remain — reduce the number of recipients or upgrade. See Account and billing.
What to check in the test
Does the AMP version render, or do you see the fallback? If your domain is not yet approved you will see the fallback — that is expected, not a bug.
Do the interactive parts work — can you actually rate, submit, spin?
Do all the links go where they should?
How does it look on a phone?
AMP has strict rules, and inboxes silently refuse to render an email that breaks them. Ampemail validates your template when you export and reports anything wrong.
Two kinds of problem are reported:
Errors must be fixed. The email will not render as AMP with them present.
Warnings are worth reviewing but will not stop the email working.
The most common errors come from links and images, and all of them are quick to fix:
Message | What it means |
|---|---|
Missing URL for button n | A button has no destination — add one or remove the button |
Missing image source for image n | An image slot is empty |
Insecure URL … is not allowed | The link uses |
Relative URL … is disallowed | The link is a path like |
Invalid URL … | The address is malformed — check for typos and stray spaces |
Invalid URL (add https://) … | The address has no scheme — put |
If you need to get a template out while a warning is still outstanding, you can choose to export with errors. Do this knowingly: recipients will get the fallback version.
Click Export to open the export dialog.
Copy AMP HTML — the interactive version, for pasting into the AMP or "AMP HTML" field of your sending platform.
Copy Fallback HTML — the standard HTML version, for the normal HTML body field.
Use View Code Before Copying if you want to inspect the output first.
Most platforms want both: the AMP part in the AMP field and the fallback in the HTML field. Sending only the AMP version means recipients without AMP support get nothing.
Sends the template straight into your Klaviyo account as a template, with both the AMP and HTML versions attached. You must connect Klaviyo first — see Integrations. Give the template a name in the dialog; that is the name it will carry in Klaviyo.
If the export fails with a connection error, your Klaviyo authorisation has probably expired. Reconnect it in Integrations and export again.
Downloads a single .html file, named after your template. Suitable for platforms where you paste or upload the HTML body yourself.
Downloads an archive containing the template's files. Use this when your platform wants a package rather than a single file, or when you are handing the template to a developer.
Template saved.
Test email sent and opened on both desktop and mobile.
Every interactive component tried at least once.
Every link clicked.
Validation clean, or you have knowingly accepted the warnings.
Both the AMP and fallback versions loaded into your sending platform.
Your sending domain approved for AMP, if you expect the interactive version to render — see AMP approval.
