Support without the scavenger hunt

Start with what
actually happened.

RoTrail compares public profile data on a browser schedule. These fixes cover the common failure points: a private field, a sleeping browser, an upstream API error, or an account-linking problem.

01 / INSTALL

The icon is missing

Open Chrome's Extensions menu, pin RoTrail, and confirm the extension is enabled.

Open the checklist ↓
02 / TRACKER UPDATES

A change was not instant

RoTrail is scheduled monitoring, not a live Roblox event stream. Chrome may delay background alarms.

Understand timing ↓
03 / DATA

A field shows unavailable

Private inventory, an API failure, or a permission mismatch can make one category unavailable.

Check the cause ↓

Install and pin

  1. Install only from the official Chrome Web Store listing linked on this site.
  2. Open chrome://extensions and confirm RoTrail is enabled.
  3. Open Chrome's puzzle-piece menu and pin RoTrail.
  4. Select a public Roblox profile, then add it by username or stable user ID.

RoTrail never needs your Roblox password or browser cookie. If any copy or prompt asks for either, stop.

Tracker update timing

Profile checks run hourly on Free, every 30 minutes on Plus, and every 15 minutes on Pro. Inventory reads have a separate cadence: Free reads them three times a day, while Plus and Pro read them during each profile cycle. Chrome alarms do not wake a sleeping device and can run late under load, so a closed browser, sleeping computer, or temporary Roblox/proxy error can move a tracker update beyond the nominal schedule.

  • Keep Chrome running if timing matters.
  • Confirm notifications are allowed for Chrome in your operating system.
  • Make one known public change and allow at least one full check cycle.
  • Do not treat the absence of a tracker update as proof that nothing changed.

Public data limits

RoTrail can compare only what a public endpoint returns. Private inventory cannot be revealed. Counts can change without an accessible list explaining exactly who changed. Roblox may also change or retire legacy endpoints.

A temporary fetch failure should be reported as unavailable, not interpreted as a deletion. If one category repeatedly fails while others work, email the category name, Chrome version, extension version, and approximate time. Never send an account password or cookie.

Paid-plan account linking

Google sign-in is optional and used only to link a paid RoTrail entitlement to the extension. The generated key is a RoTrail credential, not a Roblox credential.

If you already paid and cannot link the extension, email [email protected] with the purchase email and receipt ID. Do not send full card details or identity tokens.

Still stuck?

Email [email protected]. Include the extension version, Chrome version, the failing feature, what you expected, and what appeared instead. Screenshots are useful after you crop out private information.