Analytics by destination
Point a printed code somewhere new and its figures start again for the new place, with the old place's figures kept. On Business and Enterprise.
What it does
A dynamic QR code or a short link can be pointed somewhere new at any time. Without this, a code's figures are one long run: the spring menu and the summer menu, the old offer and the new one, all added together.
With it, every place the code has pointed has its own figures. Change the destination and the count starts again for the new one, while everything recorded for the previous one is kept, separate and still readable. The code's lifetime total is still shown beside them.
Where to find it
Open a QR code or short link, then its analytics. **Destinations** lists everywhere it has pointed, with the scans each one received. Choose one and the whole page, the map, the devices, the times of day, shows that destination alone. Choose **All destinations together** to see the lifetime figures again.
**Export CSV** follows the choice: with one destination chosen it holds that destination's scans, and every row says which destination it was sent to.
The same list is in the Lynkarr app, on a code's or a link's analytics.
It is on the Business and Enterprise plans. The record is kept on every plan, so the history is already there on the day you upgrade.
What counts as a new destination
A change to the address itself: the site, or the page on it. `example.com/spring` to `example.com/summer` starts a new one, and so does `example.com` to `example.org`.
A change only to what follows the question mark does not. Adding or editing a tracking tag such as `?utm_source=poster` keeps the same destination and the same figures.
Each scan is counted under the destination it was actually sent to, at the moment it happened. Nothing is worked out afterwards from dates.
Rules that send some people elsewhere (by country, device, language or time) are part of the code. When the code's main destination is new, the figures are new for the whole code, rule traffic included.
Going back, and merging
Point a code back at somewhere it has been before and a new destination starts: the second run is counted apart from the first.
If you would rather have them as one, use **Merge into...** on either row. Every scan of the one is moved to the other and the two become one. **This cannot be undone**: afterwards nothing says which scans came from which run.