Earlier quoted context omitted.
That's a standard practice for a lot of webfont vendors isn't it? I know it was for Typekit/Adobe Fonts (which requires a Creative Cloud subscription).
I'm sure it is standard practice. That still doesn't make commercial web font licenses more reasonable for anything except advertising and marketing campaigns.
I had one client that started getting their product catalog scraped aggressively, and the invoice for their licensed font usage that month was an order of magnitude higher than they expected (low six figures, vs. low five figures).
They slapped the site behind an aggressively configured enterprise WAF[1] in response to that bill specifically. It made for an abrasive visitor experience, fundamentally broke server logging data (due to header mangling), and constantly broke third party integrations.
It was such a pain to service the client that I ended up convincing their network security team to let me pilot Cloudflare in front of the WAF (that they insisted remain). Ended up using a Worker function to tidy up after the janky WAF header mangling, got them to remove the explicit challenge page, and just swapped out the licensed font for a generic/free one for suspicious activity.
All because of that stupid pageview based font licensing model and its susceptibility to abuse.