Repository navigation
docs: add monetization guide #15
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
Open
resenhadobar
wants to merge
2
commits into
Jaabaali:main
Choose a base branch
from
resenhadobar:codex/monetization-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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 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,118 @@ | ||
| --- | ||
| title: Add Jabali Ads to Your Game | ||
| description: Choose ad placements with Bali, implement Jabali ads, and verify rewards, cooldowns, and gameplay recovery in Preview and after publishing. | ||
| sidebar: | ||
| label: Monetization | ||
| --- | ||
|
|
||
| **Before you start:** Jabali must whitelist your creator account. Jabali handles this. | ||
|
|
||
| ## 1. Choose Your Ad Placement | ||
|
|
||
| An ad placement is a specific moment when your game requests an ad. Start with the player experience, not a target number of ads. | ||
|
|
||
| ### Good Placement Practices | ||
|
|
||
| - **Use natural breaks.** Reward shops, results screens, and between-round transitions are good candidates. Avoid interrupting movement, aiming, boss fights, tutorials, or timed challenges. | ||
| - **Make rewarded ads optional.** Clearly explain what players receive before watching. Normal gameplay must remain available without ads. | ||
| - **Avoid early interruptions.** As a starting recommendation, wait at least 5 minutes before showing the first automatic interstitial. | ||
| - **Limit interstitial frequency.** Use a minimum 3-minute interval between automatic ads as an initial guideline. Longer intervals may be appropriate. | ||
| - **Offer meaningful rewards.** Avoid rewards that are useless in the current situation or undermine normal progression. | ||
| - **Be transparent.** Clearly label ads and their rewards. Do not disguise ads as Continue buttons or promise a duration you cannot control. | ||
| - **Handle unavailable ads.** Players must never lose progress or become stuck because an ad fails, is dismissed, or is unavailable. | ||
| - **Pause gameplay during ads.** Freeze simulation, timers, enemies, and input. Mute game audio and restore the previous state afterward. | ||
|
|
||
| These timing recommendations are starting points, not universal requirements. Ask Bali to assess your game's actual gameplay loop. | ||
|
|
||
| ### Prompt: Ask Bali for Placement Recommendations | ||
|
|
||
| > Inspect my current game and design documents. Do not change anything yet. Recommend up to three ad placements suited to its actual gameplay loop. | ||
| > | ||
| > For each, explain the exact trigger, rewarded or interstitial format, player benefit if any, interruption risk, frequency rule, and what happens when no ad is available. | ||
| > | ||
| > Flag effects on difficulty and progression. Rank the options, recommend the smallest sensible first integration, and explain where you would NOT place ads. | ||
| > | ||
| > Tell me if no placement is a good fit. Ask me to choose before implementing. | ||
|
|
||
| ### Prompt: Challenge a Placement Idea | ||
|
|
||
| > I'm considering [describe the ad placement and reward]. Inspect how this would fit my game. | ||
| > | ||
| > Critique it honestly: could it interrupt play, feel compulsory, mislead players, or undermine progression? | ||
| > | ||
| > Identify any missing limits or failure behavior. Recommend keeping it, changing it, or rejecting it, and explain why. | ||
| > | ||
| > Do not edit the game until I approve. | ||
|
|
||
| ## 2. Ask Bali to Implement the SDK | ||
|
|
||
| Tell Bali which placement you selected and ask it to connect that placement, not merely install a package. | ||
|
|
||
| ### Prompt: Implement the Chosen Placement | ||
|
|
||
| > Implement the Jabali ads SDK for the placement we agreed on: [trigger], [format], [reward if any], [frequency rule], and [fallback]. | ||
| > | ||
| > Explain what you implemented, what is synthetic versus live, and what still requires manual verification. | ||
| > | ||
| > Then give me simple Preview testing steps for this exact game. | ||
|
|
||
| ## 3. Verify in Preview | ||
|
|
||
| A successful build proves that code compiles. It does not prove that ads appear or that monetization works. | ||
|
|
||
| ### Preview: Start With These Three Tests | ||
|
|
||
| #### Test 1: Enable Monetization | ||
|
|
||
| 1. Make sure **Enable Monetization** is selected in **Preview Settings**. If it isn't, click the checkbox to enable it. | ||
| 2. When monetization is enabled, select **Reload with monetization**. Preview will load with Jabali SDK mock ads. | ||
|
|
||
| #### Test 2: Complete an ad | ||
|
|
||
| Choose an eligible reward and complete the synthetic ad using its completion control. | ||
|
|
||
| Expected result: | ||
|
|
||
| - The reward is granted exactly once. | ||
| - The game remains usable afterward. | ||
| - The intended cooldown begins. | ||
| - Audio and controls return to their previous state. | ||
|
|
||
| #### Test 3: Dismiss an ad | ||
|
|
||
| Trigger a different eligible ad and dismiss it before completion. | ||
|
|
||
| Expected result: | ||
|
|
||
| - No reward is granted. | ||
| - No new reward cooldown begins. | ||
| - Gameplay remains available. | ||
| - No progress is lost. | ||
|
|
||
| Finally, disable Preview monetization and verify that the game remains playable. | ||
|
|
||
| ### Prompt: Get Preview Testing Instructions | ||
|
|
||
| > Read the ad integration you just implemented. | ||
| > | ||
| > Give me a short, numbered Preview checklist using the actual button labels and controls in my game. | ||
| > | ||
| > For each test, tell me what to do, what should happen, and what to report if it does not. | ||
|
|
||
| ## 4. Verify After Publishing | ||
|
|
||
| Preview testing and published-game testing are separate requirements. | ||
|
|
||
| ### Published Game Checklist | ||
|
|
||
| 1. Publish the updated build. | ||
| 2. Open the normal Jabali player page. | ||
| 3. Test each placement. Verify completion, dismissal, reward amounts, cooldowns, and gameplay recovery. | ||
|
|
||
| ### Prompt: Published Game Testing | ||
|
|
||
| > Prepare a short checklist for testing this exact ad integration after publishing. | ||
| > | ||
| > Tell me which placements and outcomes to repeat on the published game's normal Jabali player page. | ||
| > | ||
| > Include availability, completion, dismissal, pause/audio/input recovery, mobile layout, and reload/navigation. |
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
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.
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.
1. Monetization guide goes live for a feature not yet confirmed
🐞 Bug≡ CorrectnessAgent Prompt
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation toolsDismiss ↗ | View ↗