-
Notifications
You must be signed in to change notification settings - Fork 129
docs: Improvements of PPE docs #1875
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
Merged
Merged
Changes from 17 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
a5f8fda
docs: PPE refactor - first draft
patrikbraborec bf43145
docs: PPE pricing improvements
patrikbraborec 7145a17
Fix lint errors
patrikbraborec 4500938
Fix lint errors
patrikbraborec 196e832
Fix build errors
patrikbraborec 7fd6f77
Add correct python method
patrikbraborec 5280723
Fix stylistic issue
patrikbraborec 3508d8b
docs: Pay per result PR comments fixes
patrikbraborec 951b444
docs: Fix PR comments in PPR
patrikbraborec 65ce975
docs: Fix event name
patrikbraborec 707fc4f
docs: Edit PPR python example
patrikbraborec d532341
docs: First round of reviews
patrikbraborec ed58c59
Apply suggestions from code review
patrikbraborec ea3cc39
docs: Fix lint errors
patrikbraborec 4870c1b
docs: PR review comments
patrikbraborec 2f7a9c6
docs: Fix another PR comments
patrikbraborec 347a605
docs: Fix PR comments
patrikbraborec bcde319
docs: Fix PR comments
patrikbraborec 4decc54
Apply suggestions from code review
patrikbraborec 3096c2f
Apply suggestions from code review
patrikbraborec 99ff118
Apply suggestions from code review
patrikbraborec File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
--- | ||
title: Monetize your Actor | ||
description: Learn how you can monetize your web scraping and automation projects by publishing Actors to users in Apify Store. | ||
slug: /actors/publishing/monetize | ||
sidebar_position: 2 | ||
--- | ||
|
||
**Learn how you can monetize your web scraping and automation projects by publishing Actors to users in Apify Store.** | ||
|
||
--- | ||
|
||
import Tabs from '@theme/Tabs'; | ||
import TabItem from '@theme/TabItem'; | ||
|
||
Apify Store allows you to monetize your web scraping, automation and AI Agent projects by publishing them as paid Actors. This guide explains the available pricing models and how to get started. | ||
|
||
## Pricing models | ||
|
||
Actors in Apify Store can be published under one of the following pricing models: | ||
|
||
1. _Free_: Users can run the Actor without any additional charges beyond the platform usage costs generated by the Actor. | ||
2. _Rental_: Users pay for the platform usage costs. However, after a trial period, they need to pay a flat monthly fee to the developer to continue using the Actor. | ||
3. _Pay per result (PPR)_: Users don't pay for the platform usage costs. Instead, they pay the developer based on the number of results produced by the Actor. | ||
4. _Pay per event (PPE)_: Users don't pay for the platform usage cost the Actor generates. Instead, they pay based on specific events that are programmatically triggered from the Actor's source code. These events are defined by the developer and can include actions such as generating a single result or starting an Actor. | ||
patrikbraborec marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
For a detailed comparison of pricing models from the perspective of your users, refer to [Actors in Store](/platform/actors/running/actors-in-store) page. | ||
|
||
## Key benefits | ||
|
||
The following table compares the two main pricing models available for monetizing your Actors: | ||
|
||
| Feature/Category | Rental pricing | Pay-per-result (PPR) | Pay-per-event (PPE) | | ||
patrikbraborec marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|-------------------------|-------------------------------|-------------------------------|-------------------------------| | ||
| Revenue scalability | Capped at monthly fee | Unlimited, scales with usage | Unlimited, scales with usage | | ||
| AI/MCP compatibility | ❌ Not compatible | ✅ Fully compatible | ✅ Fully compatible | | ||
| User cost predictability| Confusing (rental + usage) | Clear, transparent pricing | Clear, transparent pricing | | ||
patrikbraborec marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| Store discounts | ❌ Single price only | ✅ Store discounts available | ✅ Store discounts available | | ||
| Marketing boost* | Standard visibility | Priority store placement | Priority store placement | | ||
patrikbraborec marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| Commission opportunities| Standard 20% | Standard 20% | Promotional 0% periods | | ||
| Custom event billing | Not available | Not available | ✅ Charge for any event | | ||
| Per-result billing | Not available | ✅ Charge per dataset item | Optional (via event) | | ||
|
||
## Setting up monetization | ||
|
||
Navigate to your [Actor page](https://console.apify.com/actors?tab=my) in Apify Console, choose the Actor that you want to monetize, and select the Publication tab. | ||
 | ||
Open the Monetization section and complete your billing and payment details. | ||
 | ||
Choose the pricing model for your Actor. | ||
 | ||
Follow the monetization wizard to configure your pricing model. | ||
<Tabs> | ||
<TabItem value="Rental" label="Rental"> | ||
 | ||
</TabItem> | ||
<TabItem value="Pay-per-result" label="Pay-per-result"> | ||
 | ||
</TabItem> | ||
<TabItem value="Pay-per-event" label="Pay-per-event"> | ||
 | ||
</TabItem> | ||
</Tabs> | ||
|
||
## Changing monetization | ||
|
||
You can change the monetization setting of your Actor by using the same wizard as for the setup in the **Monetization** section of your Actor's **Publication** tab. Any changes made to an already published Actor will take _14 days_ to come into effect, so that the users of your Actor have time to prepare. | ||
patrikbraborec marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
:::important Frequency of monetization adjustments | ||
|
||
Be aware that you can change the monetization setting of each Actor only once per month. For further information and guidelines, please refer to our [Terms & Conditions](https://apify.com/store-terms-and-conditions) | ||
patrikbraborec marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
::: | ||
|
||
## Monthly payouts and analytics | ||
|
||
Payout invoices are automatically generated on the 11th of each month, summarizing the profits from all your Actors for the previous month. | ||
In accordance with our [Terms & Conditions](https://apify.com/store-terms-and-conditions), only funds from legitimate users who have already paid are included in the payout invoice. | ||
|
||
:::note How negative profits are handled | ||
|
||
If your PPR or PPE Actor's price doesn't cover its monthly platform usage costs, it will have a negative profit. When this occurs, we automatically set that Actor's profit to $0 for the month. This ensures a single Actor's loss never reduces your total payout. | ||
|
||
::: | ||
|
||
You have 3 days to review your payout invoice in the **Development >Insights > Payout** section. During this period, you can either approve the invoice or request a revision, which we will process promptly. | ||
If no action is taken, the payout will be automatically approved on the 14th, with funds disbursed shortly after. Payouts require meeting minimum thresholds of either: | ||
|
||
- $20 for PayPal | ||
- $100 for other payout methods | ||
|
||
If the monthly profit does not meet these thresholds, as per our [Terms & Conditions](https://apify.com/store-terms-and-conditions), the funds will roll over to the next month until the threshold is reached. | ||
|
||
## Actor analytics | ||
|
||
Monitor your Actors' performance through the [Actor Analytics](https://console.apify.com/actors/insights/analytics) dashboard under **Development > Insights > Analytics**. | ||
|
||
The analytics dashboard allows you to select specific Actors and view key metrics aggregated across all user runs: | ||
|
||
- Revenue, costs and profit trends over time | ||
- User growth metrics (both paid and free users) | ||
- Cost per 1,000 results to optimize pricing | ||
- Run success rate statistics | ||
- User acquisition funnel analytics | ||
- Shared debug runs from users | ||
|
||
All metrics can be exported as JSON for custom analysis and reporting. | ||
|
||
## Promoting your Actor | ||
|
||
Create search-engine-optimized descriptions and README files to improve search engine visibility. Share your Actor on multiple channels: | ||
|
||
- Post on Reddit, Quora, and social media platforms | ||
- Create tutorial videos demonstrating key features | ||
- Publish articles about your Actor on relevant websites | ||
- Consider creating a product showcase on platforms like Product Hunt | ||
|
||
Remember to tag Apify in your social media posts for additional exposure. Effective promotion can significantly impact your Actor's success, differentiating between those with many paid users and those with few to none. | ||
|
||
Learn more about promoting your Actor in the [Apify's marketing playbook](/academy/actor-marketing-playbook). | ||
|
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.