Skip to content

docs: explain monetization change flow and remove PPR from creator docs#2333

Draft
Priban wants to merge 4 commits intodocs/ppr-cleanup-followupfrom
docs/25889-creator-monetization-flow
Draft

docs: explain monetization change flow and remove PPR from creator docs#2333
Priban wants to merge 4 commits intodocs/ppr-cleanup-followupfrom
docs/25889-creator-monetization-flow

Conversation

@Priban
Copy link

@Priban Priban commented Mar 12, 2026

Summary

  • Expanded the "Change monetization" section in monetize/index.mdx with structured subsections covering significant vs non-significant changes, the 14-day notice period, inability to cancel planned changes without admin help, and the ~1 month restriction cycle
  • Mirrored the expanded monetization flow info in the academy guide (how_actor_monetization_works.md)
  • Removed PPR (pay per result) references from all three creator-facing docs: monetize/index.mdx, how_actor_monetization_works.md, and how_store_works.md
  • Reordered comparison table to lead with PPE as the recommended model

Note

Low Risk
Low risk documentation-only changes; main risk is confusing creators if any pricing-model wording or internal links are incorrect.

Overview
Updates creator-facing monetization docs to remove Pay-per-result (PPR) and consistently present monetization as Pay-per-event (PPE) or Rental (including updated page descriptions and a simplified comparison table).

Expands and aligns the “Change monetization” guidance across docs by clearly separating significant vs non-significant changes, documenting the 14‑day notice flow, the once-per-month restriction, and the need to contact support to cancel a planned significant change.

Written by Cursor Bugbot for commit 81da1b5. Configure here.

@Priban Priban marked this pull request as draft March 12, 2026 15:37
@github-actions github-actions bot added the t-c&c Team covering store and finance matters. label Mar 12, 2026
@apify-service-account
Copy link

Preview for this PR was built for commit 81da1b5 and is ready at https://pr-2333.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 3ce4eba and is ready at https://pr-2333.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 2c6c0c8 and is ready at https://pr-2333.preview.docs.apify.com!

@Priban Priban force-pushed the docs/25889-creator-monetization-flow branch from 2c6c0c8 to df90f8b Compare March 16, 2026 09:42
Priban and others added 4 commits March 16, 2026 10:45
Expand the "Change monetization" section with details on significant vs
non-significant changes, the 14-day notice period, inability to cancel
planned changes, and the ~1 month restriction cycle. Remove PPR references
from creator-facing documentation.

Closes #25889

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The waiting period is simply that the next change also takes 14 days,
not an additional waiting period on top.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add TODO comment about incorrect profit math in PPE example
- Use "significant" instead of "major" in why_publish.md
- Use "once per month" instead of "once every 30 days" in pay_per_result.mdx
- Update rental marketing copy to flag sunset instead of promoting it

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Priban Priban force-pushed the docs/25889-creator-monetization-flow branch from df90f8b to a3b1be5 Compare March 16, 2026 09:45
@apify-service-account
Copy link

Preview for this PR was built for commit df90f8b8 and is ready at https://pr-2333.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit a3b1be55 and is ready at https://pr-2333.preview.docs.apify.com!

@Priban Priban changed the base branch from master to docs/ppr-cleanup-followup March 16, 2026 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-c&c Team covering store and finance matters.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants