Analyze6 min read
Sharing: public links, live maps, and embeds
Sharing turns a private dashboard into a small set of public URLs you control: a read-only dashboard, a live visitor map, a counter widget you can embed, and an auto-generated privacy page. Each is switched on independently.
The public dashboard link
A public mirror of your Overview page: the KPI row, chart, sources, pages, geo, devices, campaigns, entry/exit pages, and new-vs-returning split, all read-only. It has no range picker and no filters: the window defaults to 30 days and can only be changed by appending ?days=N to the URL yourself before sharing it. There's no period-comparison view either.
The live map
A public version of Realtime: the live visitor map or list, with no dashboard chrome around it, meant to be linked or embedded on its own, for example on a status page.
The counter embed
A small widget showing a live visitor count and your most recent visitor's country and a generated avatar. It polls every 15 seconds while its tab is visible and pauses while it's hidden, so an embedded widget on a page nobody's looking at doesn't keep polling in the background.
The privacy page
An auto-generated statement describing your actual tracking setup (cookieless or cookie mode, whether session replay is enabled, sample rate) meant to be linked from your own site's privacy policy. It's derived from your live configuration, so flipping a setting under Configure updates the page on its next request; there's nothing to keep in sync by hand.
The generated page describes Mrkr's configuration for your site. It cannot describe what your own URLs contain, and Mrkr stores the path with its query string attached (minus about thirty known campaign and click-id parameters). If your routes carry tokens, emails, or customer ids in the query string, that is a disclosure the generated page does not make for you: exclude those routes, and say what you collect in your own policy. See Excluding traffic.
Turning artefacts on and off
A single switch enables or disables sharing entirely for a site; turning it off clears the link so nothing at that URL resolves anymore. With sharing on, each of the four artefacts above (dashboard, realtime, privacy, counter) has its own toggle, so you can share the live map without exposing the full dashboard, for instance. You can also set a memorable custom slug in place of the random token: a handful of reserved words (demo, api, dashboard, and similar) aren't available, and a slug must be unique across every site on Mrkr.
What a recipient can and can't see
A recipient of any of these links sees exactly the artefact it points to and nothing else: no filters, no Funnels, Events, Cohorts, Engagement, or Visitors list, and no session replay.
Access is controlled entirely by the token (or slug) in the URL: anyone who has the link can view whatever artefacts are enabled for it. Treat a share link the same way you'd treat a bearer credential: don't post it somewhere public unless you mean for the data to be public, and turn an artefact off if a link you shared needs to stop working.