Skip to content

Commit 5f99f3a

Browse files
mhamasTC-MO
andauthored
feat: improve monetization docs (#990)
Co-authored-by: Michał Olender <[email protected]>
1 parent 04e9d88 commit 5f99f3a

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

sources/academy/platform/get_most_of_actors/monetizing_your_actor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ At the end of each month, we will then add up all rental fees collected in that
3131
3232
## Pay-per-result pricing model {#pay-per-result-pricing-model}
3333

34-
If you make your Actor pay-per-result instead, you will set the price per 1,000 results, and users will be charged for your Actor solely based on the number of results your Actor produces. That's your **revenue**. The underlying [platform usage](https://docs.apify.com/platform/actors/running/usage-and-resources) the Actor generates is your **cost**. Your profit which is then paid to you is computed as 80% of the revenue minus the costs, i.e. `(0.8 * revenue) - costs = profit`. This profit is also paid out monthly.
34+
If you make your Actor pay-per-result instead, you will set the price per 1,000 results, and users will be charged for your Actor solely based on the number of results your Actor produces. That's your _revenue_. The underlying [platform usage](https://docs.apify.com/platform/actors/running/usage-and-resources) the Actor generates, using the free plan unit pricing, is your _cost_. Your profit which is then paid to you is computed as 80% of the revenue minus the costs, i.e. `(0.8 * revenue) - costs = profit`. This profit is also paid out monthly.
3535

3636
Note that only revenue and cost for Apify customers on [paid plans](https://apify.com/pricing) are taken into consideration when computing your profit. Users on free plans are not reflected there, although you can see statistics about the potential revenue of users that are currently on free plans in Actor insights in the Apify Console.
3737

@@ -74,7 +74,7 @@ Also, note that you are allowed to adjust the monetization settings of the Actor
7474

7575
## How you will be paid out {#payouts}
7676

77-
Payout invoices are created automatically at the beginning of the new month. You will be notified and can access the new payout invoice, and any historical invoices, in the [**Settings > Payouts**](https://console.apify.com/account/payouts) section in Apify Console. Once the new invoice is ready, you will need to review and approve it in order for the payment to be processed. Note that if you do not approve the invoice, or let us know of any discrepancies, by the 9th of the month, the invoice will be auto-approved by the system on the 10th.
77+
Payout invoices are created automatically on 14th of each month. You will be notified and can access the new payout invoice, and any historical invoices, in the [**Settings > Payouts**](https://console.apify.com/account/payouts) section in Apify Console. Once the new invoice is ready, you will need to review and approve it within a week in order for the payment to be processed. Note that if you do not approve the invoice, or let us know of any discrepancies, by the 20th of the month, the invoice will be auto-approved by the system on the 21st. If you have multiple Actors, the total profit is the sum of individual profits, and any losses and gains cancel out.
7878

7979
## Tracking profit and user statistics {#analytics}
8080

sources/platform/actors/publishing/testing.mdx

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,27 +10,30 @@ sidebar_position: 3
1010
---
1111

1212
### Why we test
13+
1314
We want to make sure that all Actors in Apify Store are top-notch, or at least as top-notch as they can be. Since there are many of them, we have an automated testing procedure in place that tests all Actors daily.
1415
This helps us to flag Actors that temporarily don't work as expected `under maintenance`, and to automatically `deprecate` Actors that have been broken for more than a month.
1516

1617
### How we test
18+
1719
The test runs the Actor with its default input (defined by the **prefill** option in the input schema file)
18-
and expects it to finish with a **Succeeded** status within 5 minutes of the beginning of the run.
20+
and expects it to finish with a **Succeeded** status and non-empty default dataset within 5 minutes of the beginning of the run.
1921

2022
![Actor page](./images/actor-test.webp)
2123

2224
If the Actor fails to complete successful runs for three consecutive days, the developer will be notified,
2325
and the Actor will be labeled `under maintenance` until it is fixed. After another 14 days of failing runs, you will receive another notification. Finally, if the runs continue to fail after yet another 14 days, the Actor will be `deprecated`.
2426

2527
### How can I make my Actor healthy again?
28+
2629
The best course of action is to fix the Actor and rebuild it. The automatic testing system will pick this up within 24 hours
2730
and mark it as healthy. In some cases, your Actor might break because of issues with the target website. In such a case, if your Actor
2831
passes the majority of test runs in the next 7 days, it will be marked as healthy automatically.
2932

3033
## What if my Actor cannot comply with the test logic?
3134

3235
Actors that require some sort of authentication will always fail the tests despite being fully functional. Also, some Actors inherently run for longer than 5 minutes.
33-
If that's the case with your Actor, please contact support at **[email protected]** and explain your specific use case that justifies why the Actor should be excluded from the automated tests.
36+
If that's the case with your Actor, please contact support at [[email protected]](mailto:[email protected]) and explain your specific use case that justifies why the Actor should be excluded from the automated tests.
3437

3538
## Advanced Actor testing
3639

0 commit comments

Comments
 (0)