Skip to content
MARPLA / Help center

Connect your game

Connect your game

Connecting a game opens its analytics and management tools.

How to use it

  1. Open My games, add your game and open its connection settings.
  2. Select the modules you need and follow the connection form's steps.
  3. Check the access status. If a module needs more permissions, grant them and check again.

Advice and practical context

Connection boundary

A connection authorizes selected resources and operations; it does not prove ownership. Modules use different scopes, and missing write access can leave reads working. Granting the minimum required permissions reduces the impact of credential compromise.

Key safety

Create a separate task-specific key, restrict it to the game where supported, and store it like a password. Never paste the secret into chat or source control. After changing permissions, recheck the module without broadening access to every resource unnecessarily.

A scope status confirms a declared permission, while a particular operation still depends on the key owner's rights and target resource. Perform a safe read in the intended module after setup. Verify writes only through the product's confirmed action.

Technical detailsCalculations, permissions and behavior

Connection & availability

Enter keys only in the protected connection form, never in contact fields or Discord. Analytics requires universe.analytics:read for the selected game. For 401/403 check key and permissions; 429 indicates rate limiting.

Repeated clicks do not make data arrive sooner. Stored values remain available during source failures. Historical days, breakdowns and individual metrics may arrive late; D30 needs a mature cohort.

Connections: status and action

The colored indicator on each game card opens key settings if your role can manage integrations. Green means all current modules have required grants, the key has been checked and there are no known access failures. Yellow means missing permissions, an outdated check or temporary Roblox unavailability.

Red means Roblox rejected connected access. Hover for the color meaning; the indicator also has a screen-reader label. Role-based access does not imply anything about the owner's key.

Paste the key at the top and choose Apply key. Each module below has its own card with Granted, Add, Check or Unavailable statuses. Expand API names and setup steps below.

You can check a saved key without entering it again; repeat checks within a minute reuse the saved result. Status is stored on the server, not just in this browser; after a day without verification, green changes to yellow. Verification does not create test ads, upload images or edit products: write access and access to each specific resource are finally checked when you perform an action.

Limits & secure setup

The experience owner or a group member with appropriate permissions creates the key. A key does not combine privileges from different accounts: advertising needs the same key owner's access to the ad account and experience; Assets needs access to the selected creator. Limit grants to the relevant experience and group.

IP restrictions must match MARPLA server egress, not your computer's address; cloud hosting has no promised fixed egress IP. Check expiry and Enabled. The secret is encrypted on the server and is excluded from URLs, instructions and verification results.

Roblox grants and MARPLA roles are independent: a key alone does not authorize a service member to edit prices or advertising.

If permissions are missing

Report, section and chart refresh buttons share one icon style; the investor header places it below the date. Ordinary errors turn the arrows red, with a retry hint instead of a large technical notice. Clicking requeues a request without bypassing Roblox backoff.

Missing-key and confirmed access-denial actions remain visible. After saving, MARPLA shows the key's declared grants, not a guarantee that every operation will succeed. Write access is checked on your action; no test campaigns, purchases or uploads are created for verification.

For 401 check the key, enablement and expiry. For 403 check the named scope and resource access. Rate limits (429) and outages do not call for additional grants.

Analytics, advertising, creatives and the product catalog link to the shared key setup for the relevant module. Add the specific grant in Roblox and save the same key again in MARPLA; use the new secret if Roblox issued one. History is retained.

What another Roblox key cannot unlock

Public data & contacts · available

Current players, the public catalog and monitoring do not require a personal Roblox API key. Discord contact fields, invitations and investor links use MARPLA permissions, not Roblox scopes.

P50/P90 & history

Exact daily Creator Dashboard ranges are requested and stored separately from game metrics. Roblox may deny the benchmark endpoint to a regular API key; MARPLA then shows the latest finalized game metric without a stale gauge instead of mixing it with an old P50/P90 snapshot. A new key cannot create pre-connection data, immature cohorts or a complete purchase ledger.

SDK · available

Extra events require the SDK and a separate MARPLA secret in server-side game code. This is not an additional Roblox Open Cloud scope.

Roblox OAuth · shared account

Sign-in and profile use one Roblox consent flow. By default it requests permissions for current modules: analytics, ads, Assets, passes and products. Advertising reuses the integration owner’s account analytics grant.

Game API keys still power background collection and other Open Cloud operations; OAuth does not replace per-Universe or advertising-account authorization. The MARPLA administrator configures the client secret.

Discord / Telegram / AI · coming soon

Preview interfaces exist. Real delivery and chats will need separate bot or webhook connections with minimal permissions; AI needs a server-side provider. Never paste those secrets into the Roblox API Key field.

Developer support · links available

External payment links and Roblox pass-purchase links are available. MARPLA does not implement payment processing, automatic donation verification or direct Robux transfers; Analytics and Products scopes do not provide those features.

Useful articles: examples and decisions

The guide covers the steps in the service. These articles explain the metrics, examples, techniques and how to evaluate results.

Action essentials and individual concepts (1)