
SapotaCorpEmail content is great, personalization is perfect, design is clean. Subscribers read it. Nobody clicks. The CTA didn't tell them what to do clearly enough. Here's the five-factor rule we apply to every button.
Client emails we audit regularly have strong content, personalized copy, and low click-through rates. The reason is usually the CTA - either buried, buried under siblings, or so generic ("Click here") that it doesn't tell subscribers what they're about to do.
Every CTA we approve for production hits five factors. Here's the rule.
Factor
Good
Bad
Urgent
"Buy now - ends in 2 hours"
"Purchase"
Short (≤ 5 words)
"Claim your discount"
"Click here to view our products and offers"
Verb-led
"Download / Subscribe / Explore"
"Special offer for you"
Clear, no surprise
"View your order" → order page
"See more" → random category
Few and prominent
1-2 main CTAs, big, contrasting color
6 tiny text links across the email
Apply all five. Skipping any weakens the CTA.
Urgency language lifts conversion. Not every email needs it, but where it applies:
Don't fake urgency. Subscribers learn to distrust "limited time" when it appears on every email.
Buttons with text longer than five words get scanned past. Mobile buttons with five-word text wrap awkwardly.
Pattern: imperative verb + object.
Good: "Claim discount"
Good: "View sale"
Good: "Register free"
Bad: "Click here to view our amazing new collection"
Bad: "Special offer available today - don't miss out"
Start with an action verb. The subscriber's eye is scanning for "what do I do?"
Noun-led CTAs ("Special offer for you") describe what the CTA is but don't tell subscribers what action to take. Slower to parse, lower CTR.
Button text should match the destination. Trust is expensive to rebuild.
Every surprise click costs goodwill. Subscribers remember, and CTR drops on future sends.
The #1 failure mode we see: clients want to promote six things at once, email ends up with six CTAs.
Subscribers can't decide. Everyone clicks nothing.
Rule: one email, one primary purpose, one primary CTA.
Secondary CTAs can exist - they must be visibly smaller and less prominent. Text link in the footer, not another button competing with the hero.
Example of bad:
[Shop All] [Shop Men's] [Shop Women's] [View Sale]
[Read Blog] [Follow Us] [Refer a Friend]
Seven CTAs. Subscriber's eye bounces. Click rate: 0.8%.
Same content, restructured:
[Shop the Collection] (primary, big button)
... email body ...
Also: [Read latest blog] (text link, footer)
Two CTAs. Primary is obvious. Click rate: 2.4%.
Minimum 44 x 44 pixels tap target. Text links are too small for fingers - most mobile users skip them.
Padding inside the button matters as much as text size. 12px vertical padding, 24px horizontal padding, 16px font = a comfortable tap target on any phone.
With mobile-heavy audiences, place the primary CTA above the fold - visible without scrolling.
Subscribers decide whether to engage in the first few seconds. If the primary action is buried at the bottom, half the audience never sees it.
Pattern:
Two instances of the same CTA - one early, one late. Subscribers who decide quickly tap the first; subscribers who read then decide tap the second.
Button color should contrast strongly with surrounding content. Brand colors often don't contrast enough - beige button on beige email is invisible.
Accessibility floor: 4.5:1 contrast ratio between button text and button background. Test with a contrast checker.
Common pattern: white background, brand-dark text, one accent color used only for CTAs. Over time subscribers learn "orange button = the action to take."
CTAs are the conversion lever in email. Five factors - urgent, short, verb-led, clear, prominent - separate clicked CTAs from skipped ones. One primary CTA per email, above the fold, big enough for fingers. Five seconds of CTA review per send produces compounding CTR improvement.
Optimizing email CTA strategy on client SFMC accounts? Our Salesforce team runs CTA audits and conversion rate optimization on production engagements. Get in touch ->
See our full platform services for the stack we cover.