Close search
 
Home | Tech Support | Usage-based pricing

Usage-based pricing

04 August 2026

We’ve received a question about our recently published best practice on reporting to multiple identities.

Publisher platforms often offer multiple authentication methods to end users. Multi-id is great when it allows a user to access content, but it has reporting drawbacks. We recommend that publishers link a user’s activity, and report all COUNTER metrics, to all relevant institutions. The fallback position is to restrict users to a single institutional identity. Single identities are easier for reporting, but restricted users might not be able to access everything they’re entitled to read.

So what’s the question? Put simply, the librarian asked us what happens when licence costs are based on usage that is reported to multiple institutions.

COUNTER sets the standard for usage metrics. We don’t think it is appropriate for us to specify business practices and/or pricing models. When it comes to pricing, transparency matters as much for usage-based pricing as for any other models. Publishers who allow users to have multiple identities they should explain how that affects their usage-based pricing calculations. Because transparency is important, we’ll add a flag for whether multi-id is in place when we develop new Registry features later this year.

This website uses cookies
This site uses cookies to enhance your browsing experience. We use necessary cookies to make sure that our website works. We’d also like to set analytics cookies that help us make improvements by measuring how you use the site. By clicking “Allow All”, you agree to the storing of cookies on your device to enhance site navigation, analyse site usage, and assist in our marketing efforts.
These cookies are required for basic functionalities such as accessing secure areas of the website, remembering previous actions and facilitating the proper display of the website. Necessary cookies are often exempt from requiring user consent as they do not collect personal data and are crucial for the website to perform its core functions.
A “preferences” cookie is used to remember user preferences and settings on a website. These cookies enhance the user experience by allowing the website to remember choices such as language preferences, font size, layout customization, and other similar settings. Preference cookies are not strictly necessary for the basic functioning of the website but contribute to a more personalised and convenient browsing experience for users.
A “statistics” cookie typically refers to cookies that are used to collect anonymous data about how visitors interact with a website. These cookies help website owners understand how users navigate their site, which pages are most frequently visited, how long users spend on each page, and similar metrics. The data collected by statistics cookies is aggregated and anonymized, meaning it does not contain personally identifiable information (PII).
Marketing cookies are used to track user behaviour across websites, allowing advertisers to deliver targeted advertisements based on the user’s interests and preferences. These cookies collect data such as browsing history and interactions with ads to create user profiles. While essential for effective online advertising, obtaining user consent is crucial to comply with privacy regulations.