Skip to main content
Creating an email proof

You can send an HTML email from any email marketing system (e.g Mailchimp, Emma, Ontraport etc) into PageProof as a proof. Here’s how.

Gemma avatar
Written by Gemma
Updated over a month ago

Did you know, that instead of sending a test email from your email marketing system to yourself and your colleagues, you can simply send it to create a proof in PageProof? Email proofing is quick and easy, and as long as your email marketing tool can send a test email to any email address, you can then send a test email into PageProof.

Email marketing systems such as: Mailchimp, Emma, Ontraport, Sender, Zoho Campaign, Brevo, Campaign Monitor, Active Campaign, Salesforce etc are all supported – just to name a few.

To create an email proof

Step 1

Click the file dropper icon and select Email.

File dropper icon showing the file location options

Step 2

In the set-up screen, click copy next to the email address. You will need this email address to send your test email to.

Copy the unique email address

Go to your email marketing tool of choice, and send the test email to this email address. PageProof will then receive this email and the setup screen will update with a thumbnail, and the subject line of the email as your proof name.

Step 3

Complete all the details as you usually would to set up the proof:

  • Proof name

  • Adding any additional tags (for example a job number, project name or client name)

  • Setting a due date and time that you want to receive the feedback by

  • Adding an optional message to reviewers

Then choose a workflow or create a workflow from scratch – whichever you prefer and click send proof.

Tip: If you forget to copy the email address and have sent out your proof, click the i icon on the proof tile in your outbox and copy the email address from the proof’s info pane.

To see the ‘to’ and ‘from’, subject line, and use the automatic link checker – click the dimension pill details to the left of the proofing screen.

Learn more about email proofing with PageProof.

Did this answer your question?