Click-through rate is clicks divided by impressions: the share of people who saw the ad and clicked. Conversion rate is conversions divided by clicks: the share of visitors who did the thing that matters after landing. The two diagnose different problems. Weak CTR points at the ad; weak conversion rate points at the landing page or the offer.
Add ad spend and the 412 Freelancers calculator also returns cost per click and cost per acquisition from the same inputs, so one set of campaign numbers gives all four metrics at once.
Depends entirely on where the ad runs. In US search advertising, the median CTR is 6.64% with a median conversion rate of 8.18% and a $5.42 CPC, per WordStream's 2026 benchmarks across 13,474 campaigns. On Meta, Lebesgue's 2026 ecommerce data clusters most industries between 2% and 3%.
The gap is intent, not quality. Search ads answer a query someone just typed; social ads interrupt a feed. So never compare a Facebook CTR to a Google CTR, and never judge either without conversion rate next to it. A high CTR feeding a page that does not convert is just an expensive compliment. Pair this with your CPM and breakeven CPA to see the whole chain.
The 2026 median across US search campaigns is 6.64% per WordStream. Branded terms run far higher and competitive non-brand terms lower, so compare each campaign against its own keyword type, not the blended average.
Most ecommerce industries cluster between 2% and 3% in Lebesgue's 2026 benchmarks. Feed interruption earns fewer clicks than search intent, which is why a 2.5% CTR on Meta can outperform a 6% CTR on search once conversion is counted.
Neither matters alone. CTR measures whether the ad earns the click; conversion rate measures whether the page earns the sale. Multiplied against each other and spend, they produce CPA, the number the campaign actually lives or dies on.
In order of leverage: the offer, the creative hook in the first second, audience fit, then format and placement. Copy tweaks are the last five percent. If CTR is fine and results are not, the problem moved downstream to the landing page.