Notifications
See how many of the people who saw the prompt subscribed, and how far each notification reached and how many clicked. Break down click rate by day and time sent, by sending route, and by device and browser.
Notification statistics available now, the rest in preparation
Page views alone cannot tell you. See on one screen which content was read, which notifications brought users in and what users wanted to know.
This is an example of the screen layout, not real figures.
Its place in the user's journey
Analytics shows four steps, from the visit to the return, in numbers.

Tools like Google Analytics tell you how many times a page was opened and where visitors came from. Keep using them. publish.link analytics fills in the part those tools cannot see.
Because publish.link is what sent the notification, you can follow through to whether the user who got it actually came back and what they read. Questions that came in to the AI navigator are on the same screen. Product clicks will be added when shop partnerships open.
Return visits are shown in two kinds: visits that came in by clicking a notification, and visits where the user got a notification and came separately within a day. The two are not added together to inflate results.
Some browsers delete the user code on their own when there has been no visit for a while. So return visit figures can come out lower than the real number, and the screen says so.
Notifications, reading and questions come together on one screen.
←See what brought users back, and decide the next notification.
Records from push, personalized notifications and the AI navigator come together in one place.
See how many of the people who saw the prompt subscribed, and how far each notification reached and how many clicked. Break down click rate by day and time sent, by sending route, and by device and browser.
See the read rate and completion rate for each piece of content, and which pieces led users on to the next one.
On sites with reading history turned on, see how users' interests are distributed and which topics were read most.
See separately whether returning users came by clicking a notification, came on their own after getting one, or came from search.
See which questions came up on which content in the AI navigator. Questions that could not be answered because the content had no answer, and questions users rated as not helpful, are collected separately and used as leads for what to publish next.
See how many times Linky was opened out of the screens where its button was shown and how many of those led to a question, and how many questions were example questions clicked versus typed in. Only daily totals per site are counted.
See a week's notifications, subscribers, Linky usage and questions on one page, compared with the week before. You can create a read-only address that opens without login and pass it around inside the company.
See how often products linked to content were clicked and how much revenue came in, together with settlement records.
Questions that came in to the AI navigator are collected for each piece of content. Questions that could not be answered because the content had no answer are marked separately.
This is an example of the screen layout, not real figures. "Not in the content" is a lead for what to publish next.
We collect neither names nor contact details. Only the content read is kept under an anonymous code, and only that publisher sees the record.
Users are told apart only by one random code. No login or sign-up is needed.
One publisher's records are not mixed with those of other publishers or shops.
Download the numbers you see on screen as a file and use them as they are in internal reports.
Page views tell you what was read. Analytics tells you who came back and why.
Tell us your site address and daily visitor count, and we will send you installation steps and a schedule.
Received. We will reply to the contact you left.
That did not go through. Fill in all three fields and send again.