Map Extract
Free tool

Email personalisation checker

Paste a sales or prospecting template. You get a personalisation score out of 100, a count of merge tokens, and a comparison of how often the email talks about the reader versus about you, followed by specific suggestions for what to change.

Runs in your browser. Nothing you enter is uploaded.

Before and after: a signage company's template

The first version is the kind of template that gets written in a hurry. It has no merge tokens, opens with four stock phrases and uses we, our, us and my six times against two uses of you. It scores 0.

The rewrite adds the first name with a fallback, the company and the town, drops the stock openers and is written entirely about the reader. It scores 85 with no tips left.

Input
Version 1:
Dear Sir or Madam,
I hope this email finds you well. My name is Jo and we are a leading signage company. We have worked with many businesses and our team would love to help.
Let us know if you are interested.

Version 2:
Hi {{first_name|there}},
Saw that {{company}} has just opened a second site in {{town}}. When you fit out a new shop front, your signage is usually the last thing anyone has time for.
Would a mock-up of your fascia for the new site be useful?
Result
Version 1: score 0/100, merge tokens 0, "you" words 2, "we" and "I" words 6
Generic openers found: dear sir, dear sir or madam, hope this email finds you well, my name is

Version 2: score 85/100, merge tokens 3, "you" words 3, "we" and "I" words 0
Tokens found: first_name, company, town. Well personalised.

Checking a template

  1. Paste the template with its tokens

    The checker recognises four token styles: {{double}}, {single}, [square] and %percent%. A fallback written as {{first_name|there}} counts as part of the token.

  2. Read the four figures

    Score out of 100, number of distinct tokens, words addressing the reader (you, your, yours) and words about the sender (we, our, us, I, my, me).

  3. Work through the tips

    Each tip names what is missing: a name token, a company token, a detail such as town or industry, a generic opener to replace, or too much we.

  4. Edit until the tips stop

    When no tips remain the tool says "Well personalised". Then merge it against real rows with the template formatter to see the actual emails.

How the score is built

The score is a simple formula so you can see exactly what moves it.

PartEffect on the score
Starting value20
Each distinct merge token, up to four+15 each (so up to +60)
Each generic opener found-15 each
You words at least equal to we and I words+20
RangeNever below 0 or above 100

Tokens are not the same as personal

A template with four tokens and nothing else specific still reads like a mail merge, and recipients can tell. The tokens worth having are the ones that let the first sentence prove you looked at this business: its town, its category, a service on its website, or the fact it has just opened a second branch.

That is where the source of your list matters. If you collected businesses from Google Maps, the category, town and website are already columns in the export, so {{category}} and {{town}} are genuinely filled for every row. Inventing a personal detail you cannot fill reliably leads to the worst outcome, a raw token or an obviously wrong fact in the inbox.

  • Generic openers the checker looks for include: dear sir or madam, to whom it may concern, dear business owner, hi there, I hope you are well and my name is.
  • Hi there is flagged when typed as text. As a fallback inside {{first_name|there}} it only appears for rows without a name.

Questions people ask

What is a good personalisation score?

Aim for the point where no tips remain, which in practice means a name token, a company token, one specific detail such as town or industry, no stock openers and more you than we. That usually lands around 80 to 95. The number itself matters less than the tips: a score of 100 with tokens you cannot fill for every row is worse than 70 with honest ones.

Why does my email talk more about us than the reader?

Most first drafts explain who the sender is before they explain why they are writing. The checker counts we, our, us, I, my and me against you, your and yours. Turning "we help salons fill quiet slots" into "your quiet weekday slots" moves the focus to the reader without changing the offer.

Which merge token formats does it recognise?

Double braces such as {{company}}, single braces such as {company}, square brackets such as [Company] and percent signs such as %company%. Fallbacks after a vertical bar inside braces, like {{first_name|there}}, are read as part of the token. Your sending tool may support only one of these, so check its documentation before you send.

Is hi there always a bad opener?

As the opening of every email it signals that you did not know who you were writing to, which is why the checker flags it. Used as a fallback for the few rows where no name exists it is perfectly normal. The difference is whether it appears for some recipients or for everyone.

Where your data goes

Scoring happens in the page itself. Your template, including any sample names in it, is never sent to a server, and closing the tab discards it.

Checked against the tool on

Top