Click-through rate in every direction: impressions and clicks give the CTR, a target CTR gives the clicks you need, and clicks plus CTR give the impressions behind them. Edit any two fields and the third is worked out for you (marked “Calculated”). Benchmarks and a what-if scenario sit below. Everything runs in your browser; the defaults are a worked example, so the results are already live.
The maths: CTR = clicks × 100 ÷ impressions · clicks needed = impressions × target CTR ÷ 100 · impressions = clicks × 100 ÷ CTR. A zero or empty divisor shows a dash, never NaN or Infinity.
Half a point sounds small; on real impression volumes it is often the cheapest traffic you can win — better titles, snippets and creative, not more spend.
Use these only to sanity-check a plan — they are broad planning ranges, not promises. Your own account history beats any benchmark: branded search, position, device mix and audience can move a channel’s CTR several-fold.
| Channel | Typical CTR range | What moves it most |
|---|---|---|
| Search ads | 2% – 5% | Match between query intent and ad copy; position |
| Display ads | 0.1% – 0.5% | Placement quality and creative; banner blindness is real |
| Social ads | 0.5% – 1.5% | Creative stopping the scroll; audience fit |
| Email (clicks ÷ delivered) | 2% – 4% | Subject line gets the open; offer and buttons get the click |
Click-through rate in every direction — with channel benchmarks and a CTR-improvement scenario.
100% free · No sign-up · No daily limits · No watermarks · Processed in your browser — files never leave your device
Calculate CTR from impressions and clicks, work backwards from a target CTR to the clicks you need or from clicks and CTR to the impressions behind them, sanity-check the result against channel benchmarks, and see what a +0.5-point CTR improvement is worth in clicks.
An ad was shown 10,000 times and clicked 350 times, so its CTR is 350 × 100 ÷ 10,000 = 3.5% exactly — comfortably inside the search-ads planning range. Working the other directions: 10,000 impressions at a 2.8% target CTR need 280 clicks, and 500 clicks at a 2.5% CTR must have come from 20,000 impressions. The scenario shows the prize for creative work: the same 10,000 impressions at 4.0% instead of 3.5% deliver 400 clicks — 50 extra clicks from zero extra reach.
CTR is computed as clicks × 100 ÷ impressions — multiplying before dividing keeps common values exact. The reverse directions use clicks = impressions × CTR ÷ 100 and impressions = clicks × 100 ÷ CTR. The scenario evaluates clicks at your CTR and at your CTR + 0.5 percentage points on the same impressions and subtracts. The benchmark table is a static set of broad planning ranges drawn from commonly published channel figures; nothing in it is editable because it is a reference, not an input.
CTR = clicks ÷ impressions × 100, expressed as a percentage. This tool multiplies first (clicks × 100 ÷ impressions), which is the same maths and keeps round numbers exact. 350 clicks from 10,000 impressions is a 3.5% CTR.
It depends entirely on the channel and the placement: search ads often plan around 2–5%, display around 0.1–0.5%, social around 0.5–1.5% and email around 2–4% of delivered messages. Your own past performance on the same placement is a better yardstick than any of these ranges.
Definitions differ: some platforms divide clicks by emails sent, others by delivered, and some report a click-to-open rate instead. The benchmark here uses clicks ÷ delivered. Match the definition before comparing numbers.
Multiply your impressions by the target CTR and divide by 100: 10,000 impressions at 2.8% need 280 clicks. Use the Clicks solve-for mode and the tool does it live as you type.
Not on its own. A misleading headline can raise CTR while tanking conversions and trust. CTR is a diagnostic — it tells you the ad or link earned attention; what happens after the click decides whether that attention was worth buying.
A dash means the maths had no honest answer: zero impressions cannot give a CTR, and a CTR of zero cannot give an impression count. Enter a non-zero divisor and the result appears — the tool shows a dash rather than NaN or Infinity.
What is missing, broken, or could be better on this tool? Tell us — we read every suggestion.
✅ Thanks — your suggestion has been received. Suggestions like yours shape what we build next.