-
Notifications
You must be signed in to change notification settings - Fork 133
docs(platform:actors): Actor quality score #2005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 6 commits
8ec071e
da4fbfa
087ab0c
f445d90
c0e63d9
79b3591
6c46580
bbb6655
1aa50ed
86df989
a730ee7
7dc76b8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,86 @@ | ||||||
| --- | ||||||
| title: Actor quality score | ||||||
| description: The Actor quality score tells you how well your Actor is doing in terms of reliability, ease of use, popularity and other quality indicators. The score ranges from 0 to 100 and influences your visibility in the Store. | ||||||
| slug: /actors/publishing/quality-score | ||||||
| sidebar_position: 5 | ||||||
| --- | ||||||
|
|
||||||
| The Actor quality score is a metric that evaluates your Actor's performance across multiple dimensions, including reliability, ease of use, popularity, and other quality indicators. Scores range from 0 to 100 and influence your Actor's visibility and placement in the Apify Store. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
| ## How to view your score | ||||||
|
|
||||||
| Navigate to **Console >Insights > Actor Quality**, and then select your Actor. | ||||||
|
|
||||||
|  | ||||||
|
|
||||||
| ## Overview | ||||||
|
|
||||||
| The Actor quality score aggregates multiple performance and quality metrics into a single numerical rating. This score indicates your Actor's health and user satisfaction. A higher score improves your Actor's discoverability in the Apify Store. | ||||||
|
|
||||||
| The platform provides in-app recommendations to help you identify improvement opportunities and optimize your Actor's quality score. | ||||||
|
|
||||||
| :::note Score updates are not immediate | ||||||
| Changes to your Actor may take time to reflect in your score and improvement recommendations. For more information, see [Score update frequency](#score-update-frequency). | ||||||
| ::: | ||||||
|
|
||||||
| There are eight quality categories: | ||||||
|
|
||||||
| - Reliability | ||||||
| - Popularity | ||||||
| - Feedback and community | ||||||
| - Ease of use | ||||||
| - Pricing transparency | ||||||
| - Trustworthiness | ||||||
| - History of success | ||||||
| - Congruency of texts | ||||||
|
|
||||||
| The following section provides detailed guidance on each quality category. | ||||||
|
||||||
|
|
||||||
| ## Quality score categories | ||||||
|
|
||||||
| ### Reliability | ||||||
|
|
||||||
| Reliability measures your Actor's operational stability and consistency. A reliable Actor maintains high run success rates and passes automated quality assurance tests. Poor reliability significantly impacts your quality score. For more information on testing requirements, see [Automated Testing](https://docs.apify.com/platform/actors/publishing/test). | ||||||
|
|
||||||
| Implementing an [input schema](https://docs.apify.com/platform/actors/development/actor-definition/input-schema) helps prevent runtime failures by validating user input before execution begins, reducing errors caused by invalid or malformed inputs. | ||||||
patrikbraborec marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
| ### Popularity | ||||||
|
|
||||||
| Popularity reflects user engagement and adoption of your Actor. This metric considers factors such as the number of users running your Actor, save counts, and return usage patterns. Building an Actor that addresses a clear use case and provides a seamless user experience is fundamental to achieving strong popularity metrics. | ||||||
|
|
||||||
| ### Feedback and community | ||||||
|
|
||||||
| Users who have run your Actor multiple times are invited to provide reviews and ratings. User feedback significantly influences your quality score, making it essential to deliver a positive experience from the first run. Focus on creating clear onboarding flows and intuitive interfaces. Negative reviews impact your score, so prioritize addressing critical issues promptly and maintaining active communication with your user base to foster long-term success. | ||||||
|
|
||||||
| ### Ease of use | ||||||
|
|
||||||
| Ease of use evaluates how quickly users can understand and successfully run your Actor. Provide clear, concise titles and descriptions that accurately convey your Actor's functionality. Input field descriptions should be self-explanatory and guide users toward correct usage. A [well-structured README](https://docs.apify.com/academy/actor-marketing-playbook/actor-basics/how-to-create-an-actor-readme) is equally important, particularly for Actors with complex use cases or configuration options. Strong ease of use facilitates user onboarding and improves retention rates. | ||||||
|
|
||||||
| ### Pricing transparency | ||||||
|
|
||||||
| Pricing transparency evaluates how clearly users can understand and predict the costs of running your Actor. Transparent pricing models help users make informed decisions and budget accordingly. The [Pay Per Event (PPE)](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) monetization model provides predictable, event-based pricing that makes costs explicit and easier to estimate. | ||||||
|
||||||
| Pricing transparency evaluates how clearly users can understand and predict the costs of running your Actor. Transparent pricing models help users make informed decisions and budget accordingly. The [Pay Per Event (PPE)](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) monetization model provides predictable, event-based pricing that makes costs explicit and easier to estimate. | |
| Pricing transparency evaluates how clearly users can understand and predict the costs of running your Actor. Transparent pricing models help users make informed decisions and budget accordingly. The [Pay per event (PPE)](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) monetization model provides predictable, event-based pricing that makes costs explicit and easier to estimate. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Consider offering Store Discounts for Bronze, Silver, and Gold subscription tiers. These incentives reward committed platform users and can increase your Actor's adoption among engaged customers. | |
| Consider offering discounts for Bronze, Silver, and Gold subscription tiers. These incentives reward committed platform users and can increase your Actor's adoption among engaged customers. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the admonition near the top is enough, this does not provide much more information than admonition itself. So no need to double the information
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does. I want to implicitly let them know if they fix something, the improvement recommendations are still going to be visible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case I would remove the admonition and put whole ## Score update frequency section where admonition was. This way it makes more sense, it's at the top instead of being stuck at the end of doc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
applied