Frequently Asked Questions About Serpstat Credits: Customer Support Digest #5
In the analytics section, 1 credit = 1 request.
In API, you spend 1 credit for each received request result (for example, when receiving information using the keyword_top method, in most cases, you will spend 100 credits since in the response we will receive the top 100 domains for the selected key)
Number of lines - this definition is only used in our export credits.
Requests per second is the number of simultaneous API threads per second.
Lines are the number of results in the returned query response.
The number of credits removed per request is 1 per line with the response (the method removes as many credits as lines received in the API response).
For an example of a method response, see the API documentation.
Credits in the Search Analytics module are spent on:
- Request for the site/keyword;
- Refreshing the page;
- Using filter/sorting;
- Switching to another report;
- Changing the search database;
- Changing the type of tracking;
- For batch analysis of domains. In the batch analysis tool, it is essential to remember that the number of spent credits directly depends on the number of domains and the number of search bugs. For each additional base, 1 credit will be spent.
For each update of information on a keyword, 1 credit is removed. For each region, 1 extra credit is also removed.
10 keys for 1 region = 10 credits;
10 keys in 2 regions = 20 credits;
20 keys in 2 regions = 40 credits, etc.
Learn how to get the most out of Serpstat
Want to get a personal demo, trial period or bunch of successful use cases?
Send a request and our expert will contact you ;)
Cases, lifehacks, researches and useful articles
Don’t you have time to follow the news? No worries!
Our editor Stacy will choose articles that will definitely help you with your work. Join our cozy community :)