Sharing

Sharing a report

There are three ways to hand someone a Servoki report, and they differ on one thing that matters more than any other: who can see the data. Two of them require an account. One does not.

The three link types, side by side

Link Looks like Who can open it What it exposes
The address bar /app/sites/example.com/conversions/attribution?… Anyone with access to the site Nothing on its own — it is a route, not a token. Pasting it works only for people who could already open the report.
Report link /app/r/<token> Anyone with access to the site Nothing beyond that. The token is a pointer, never a grant: it resolves under the recipient's own login and their own site membership.
Public share link /app/shared/<token> Anybody holding the URL. No account, no login. A read-only dashboard for the site, pinned to one view. Treat the URL itself as the credential.

The one mistake worth avoiding. Report links and share links sit next to each other and read almost the same. A report link shown to someone without access shows them nothing. A share link shown to the same person shows them the dashboard. If you are not certain which you are creating, create a report link — the failure mode is a colleague asking for access, not a customer's analytics on the open internet.

Copying a link to what you are looking at

Every report has a Copy link control in the top bar. It offers three things:

  • Copy link — the report exactly as you see it, with the dates frozen. This is the default, and the one to reach for when you are discussing specific numbers.
  • Copy link with live dates — the same report, re-resolved every time it is opened: "last 7 days" stays last 7 days. Unavailable on a custom range, because there is no preset to keep up to date.
  • Copy short link — saves a /app/r/<token> bookmark, useful when the full URL is too long for a chat message. Short links are always pinned.

Why the two date modes exist

A link with no dates in it means "the last 7 days" — whenever it is opened. Sent on a Monday and read on the Friday, it shows a different week, and nothing on screen says so. So a copied link is always completed at copy time: either the dates you were looking at are written into it, or the preset is written into it. What never happens is a link that quietly means something different tomorrow than it did today.

Report days are UTC days. When your local date differs from the UTC date — late evening east of Greenwich, or early morning west of it — the copy confirmation says so, because "today" is then genuinely ambiguous.

What travels in a link

A copied link carries everything that decides which numbers you are looking at: the date range, the active view and segment, every filter chip, and any per-report setting such as the attribution model or the ecommerce tab. Open it anywhere and you get the same report.

When a shared link cannot be honoured

  • No access to the site — the recipient is told which site it is and to ask a workspace admin for an invitation. The link keeps working; it starts working for them once they are invited.
  • The view it pointed at was deleted — the report falls back to the site's default view and says so on the page. It never falls back to a wider scope without telling you.
  • A setting the report no longer has — for example an attribution model that was renamed. The page falls back to its default rather than failing.

Managing saved links

Short links you have created are listed under Admin → View → Report links, with who made each one and when it was last opened. Public share links live under Admin → View → Share links, where they can be revoked. Revoking a share link is the only one of the three that actually takes access away, because it is the only one that ever gave any.