Agree and accept a placement
A deal holds the brief, terms, conversation and report.
How to use it
- Send a brief naming the game and expected deliverables. After agreement, the creator submits the publication link and report.
- Accept or request changes. A dispute records the issue but does not promise a decision or refund.
Advice and practical context
A verifiable brief
Name the game, target language, format and concrete deliverables in the brief. Specify the publication date and how both parties will verify delivery. For example, a video link and the demonstrated gameplay moment can be checked separately from view counts. Do not replace deliverables with a promise of concurrent players: game retention, other advertising sources and publication timing also affect results. Agree changes before work begins.
Report and acceptance
Keep work messages and the report inside the request so both parties see the same history. After publication, check that the link works and the content matches the agreed format. Describe a specific mismatch when requesting changes. A dispute records the problem and stops ordinary acceptance, but is not an automatic decision in either party’s favour. Never share Roblox passwords or secret API keys for a placement. Agreed public materials are sufficient to demonstrate the game.
Technical detailsCalculations, permissions and behavior
Request, conversation and acceptance
Send the creator a brief with the game, goal, format and expected result. Connected games require ad management permission; a direct Roblox game link can also be used. Offer terms are frozen in the request.
Only the two participants can see the conversation, status history and report. The creator accepts a free or barter request, publishes and submits a link and report. The developer accepts or requests explained changes.
A dispute records the issue and stops ordinary acceptance; it is not a decision in either party’s favour. Offers can be reported separately. Do not promise guaranteed online players or income.