> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/reseller-hub/usage-and-live-map.md). # Reseller Usage, Live Map & Activity Log See which RTKdata licenses are actually connected, watch live RTK sessions and GPS tracks on the map, and read the activity log of license and billing events. Three views answer "is what I sold actually being used": **Usage** for consumption and limits, **Usage > Live Map** for what is happening right now, and **Usage > Activity** for what has happened. *** ## Usage ![The usage page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-292e782b0125d6ed3f7fbaacea6f03cbc2a424bf%2Freseller-hub-usage.png?alt=media) | Card | What it tells you | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | **Total Licenses** | Everything provisioned | | **Connected Now** | Licenses with a live connection this moment | | **Not Connected** | Active licenses without a live connection | | **Avg Auth Failures** | Average failed sign in attempts per active license over the last 30 days | | **Parallel Connections** | Connections beyond what your licenses allow. Anything above 0 means some customers run more devices at once than they have data streams | | **Active Trials** | Trials running right now | The **Used vs Unused** bar under the cards shows the share of your active RTKdata Caster licenses that is connected right now. A large unused share is either a churn warning or an onboarding problem, and both are worth a phone call. Its **not connected** count is a link that filters the table below to exactly those licenses. **Usage by Customer** charts weekly connections for your top customers over 12, 6 or 3 weeks. **Composition** charts the mix of active, inactive and trial licenses over 12, 6 or 3 months. Both also take a **Custom** range. The **Licenses** table below breaks it down per license: mountpoints, customer, product, connected, last used, auth failures, GGA received, streams, and parallel connections shown against the stream count (highlighted when over). Search covers customer, license and mountpoint, and **Connected**, **Product** and **GGA Received** filter it. Each row links to its sessions on the Live Map. **Export CSV** downloads every license, regardless of the current filter. *** ## Live Map ![The live map](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-4bc1c34ce5e1f5cfb6efbb260cc0857b69581506%2Freseller-hub-live-map.png?alt=media) Every customer session across your fleet, live ones and each license's last known position. | Marker | Meaning | | ------------------------- | --------------------------------------------------------- | | Green - **Live (Fixed)** | Connected and holding RTK FIX | | Orange - **Live (Float)** | Connected but not converged | | Grey - **Offline** | Not connected right now, shown at the last known position | The cards above the map give **Live Now**, **Sessions (6h)**, **Avg Fix Rate** and **Avg Session** duration. The dropdown (**All customers** by default) narrows the map and the session log to a single license. Select a session, on the map or with **View on map** in the **Session Log** underneath, and the **Positions** panel plots its recorded path, coloured by **RTK fixed**, **RTK float** and **No fix**. That is what turns "the customer says it does not work" into "the track shows float only in that one corner of the site". Sessions of licenses still on the Legacy Caster have no recorded track. The **Session Log** lists every session with its start time, customer, license, mountpoint, fix rate, duration, outcome and caster, and filters by outcome (**Fix achieved**, **Float only**, **Auth failed**, **Connection timeout** and others). *** ## Activity ![The activity log](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-b750a99ff7b5fc3ed13f208ac30e575f6ff3c877%2Freseller-hub-activity.png?alt=media) A chronological log of what happened to your licenses and bills, newest first, searchable and filterable by **Type**: | Event type | Example | | ---------------------------------------- | --------------------------------------------------------------------------------- | | **License provisioned** | A license was activated for a customer | | **Trial started** / **Trial converted** | A trial began, or became a paid license | | **License renewed** | A term was extended | | **License upgraded** | Data streams or term were increased | | **License suspended** | Stopped, by you or through the payment reminder ladder | | **Invoice generated** / **Invoice paid** | A monthly bill was issued, or its payment arrived | | **Customer login** | A customer signed in to their [customer portal](/reseller-hub/customer-portal.md) | Events about a license link to that license. *** ## Reading fix rates The fix rate is the share of a session that reached RTK FIX. A consistently low figure for one customer is almost never a network problem: * Check **GGA received**. Without the receiver's position the caster cannot select a correction stream. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). * Check **Parallel connections**. Two devices sharing one data stream knock each other off every few seconds and neither will converge. * Check the sky view at the site. Trees, buildings and metal structures all cost convergence. More detail in [Troubleshooting](/reseller-hub/troubleshooting.md) and [Common Connection Issues](/support/common-connection-issues.md). *** ## Next * [Troubleshooting](/reseller-hub/troubleshooting.md) * [Licenses & Provisioning](/reseller-hub/licenses.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rtkdata.com/reseller-hub/usage-and-live-map.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.