Roblox creator campaign brief: scope, rights and a useful report

Write the decision before the deliverable

Finish this sentence first: “After this placement, we will decide whether to ___.” A useful first campaign might test whether a cooperative mechanic can be explained in a short video, whether a creator’s audience is interested enough to try the first session, or whether a live event format is practical. “Make the game viral” cannot tell a creator what to deliver or a developer what to accept.

Choose one question, one audience and a capped test. Record the game version, onboarding state and competing promotions before launch. If the first session is broken, fix it before paying to expose more people to it. Use public comparison to choose relevant references, while recognising that another game’s public growth does not reveal its creator spend, private retention or acquisition mix.

Qualify a creator using relevant evidence

Check the last few relevant posts rather than the biggest lifetime hit. Does the creator actually cover Roblox? Does their language and style match the experience? Can the game be played on the device they use? Ask for examples close to your proposed format, a dated audience summary if available, and a clear statement of who will produce the content.

Followers are context, not a buying unit. Keep each channel separate because audiences overlap. Label statistics supplied by the creator and note the date range; missing demographics remain unknown. If the audience or reporting cannot be checked, reduce the scope of a first test instead of inventing a precise expected conversion rate. A good reason to decline is more useful than a large but irrelevant follower count.

A worked campaign brief you can adapt

The following example is fictional. “Lantern Crew” is an illustrative cooperative game, not a MARPLA client or a campaign result. Replace the details with your actual game, scope and constraints. The budget field is a request for a quote, not an assumed market price.

Share only the access needed for a playtest. Never send a Roblox account password, API key or private analytics export as part of an introductory brief. Put access instructions and embargoed information in the appropriate private conversation after the creator agrees to the project.

Negotiate scope rather than a vague view promise

If a quote exceeds the test cap, remove a deliverable or narrow usage rights before asking for the same work at an arbitrary discount. A video, a live session and a community event create different production and reporting work. Ask what changes the quote: recording time, revision rounds, exclusivity, paid-ad rights, translation or an urgent date.

Write down the number of revisions, what counts as a factual correction and who approves it. Separate creative judgement from inaccurate product claims. Define when a delay becomes cancellation and what happens to work already produced. Specify whether a missed publication slot is rescheduled, cancelled or remedied with another agreed deliverable. Do not imply that a low player count automatically means the creator failed to deliver.

Prepare a measurement handoff before publication

Agree the destination link and the person responsible for access before recording. Test it on the intended device. Roblox Share Links support channel-specific links; management requires the owner or the relevant group permission. Agree who supplies the link and reads its report. The creator does not need the developer’s account credentials.

Keep a platform report, link activity and game analytics as separate evidence. Native Share Links can support Roblox-side acquisition and engagement analysis; an ordinary UTM-tagged click is not evidence that a person played. Note the reporting window, other campaigns, game updates and missing coverage. This is a recommended measurement setup, not a claim that MARPLA already joins a creator’s audience to individual Roblox players.

Review delivery and learning separately

Before publication, check factual claims, the destination link, game access and disclosure. On YouTube, creators must tell the platform when content includes paid promotion; the platform’s disclosure tool does not replace other applicable requirements. Agree the disclosure obligation in the brief instead of treating it as an optional late correction.

At review, first decide whether the agreed content and report were delivered. Then assess the test question using the available evidence. Record “unknown” where attribution or audience data is missing. Continue only if the format, audience fit and operational cost justify another test. A seven-day snapshot can support a follow-up question; it cannot prove a repeatable revenue outcome by itself.

1. Save the final brief and any changes accepted by both parties.
2. Check the public URL, publication timing, link and agreed disclosure.
3. Record the source, dates and limitations beside every performance figure.
4. Decide: repeat a bounded test, change the format, or stop with a stated reason.

Use MARPLA to prepare the conversation

Use a developer profile and studio portfolio to show what you build. Explore relevant creator channels and format examples, then send a brief that names the actual game and decision. Publishing a profile does not guarantee responses or campaign performance.

The network is still growing. Built-in payments, held funds and escrow protection are unavailable; paid fulfilment through MARPLA is blocked until payments are connected. Free and barter collaborations have their own supported workflow. Check the current product guide before agreeing how the work will proceed. Open the developer overview or compare public game context.

Primary sources

• Roblox Creator Hub — Share Links
• Roblox Creator Hub — Acquisition analytics
• YouTube Help — Paid promotion disclosure