NXT Embed Data Protection
This page describes what the NXT embed stores on a reader’s device and what it sends, in each identity-tracking mode. The mode is functional unless you set another one.
Where the embed sends data
The embed loads its script, content and images, and sends analytics events, votes and form submissions, all to your tenant host https://<tenant>.apps.tickaroo.com. As with any web request, the reader’s browser also sends technical data such as the IP address and the user agent.
Fonts load from your tenant host too, with two exceptions that can contact other websites:
- A custom font in your Brand loads from the address entered for it in NXT. If that address is on another website, the reader’s browser requests the font from there.
- Content your editors add to an article as HTML can load from other websites, as it would on any page.
Apart from these, the embed loads nothing from other websites.
Local Storage Entries (“Cookies”)
The embed sets no cookies. It uses the browser’s localStorage and sessionStorage. All its entries start with nxt1..
| Entry | Content | Storage | Written | Deleted |
|---|---|---|---|---|
nxt1.tika |
a random device id | localStorage and sessionStorage | full only: when the embed starts, or when the page switches to full |
when the page starts in or switches to functional or off |
nxt1.aid:<content id> |
a random id for one piece of content | localStorage and sessionStorage | functional only: when the reader first votes in that poll, answers that quiz or sends that one-per-reader form |
when the page starts in or switches to off |
nxt1.state:poll-submission:<content id>:<reader> |
the reader’s answer to a poll, and the id of the poll’s form if the reader sent it | localStorage | full and functional: when the reader votes |
when the page starts in or switches to off |
nxt1.state:poll-submission-results:<content id>:<version>:<reader> |
the poll results shown after the vote | localStorage | full and functional: when the reader votes |
when the page starts in or switches to off |
nxt1.state:form-submission:<content id>:<reader> |
a marker that the reader sent a one-per-reader form | localStorage | full and functional: when the form is sent |
when the page starts in or switches to off |
<reader> is anon, or user: followed by the id your page passed to setUserId. If you use setUserId, that id is therefore part of the entry’s name.
In off the embed writes nothing. In functional it writes nothing until the reader votes, answers a quiz or sends a one-per-reader form. If the browser blocks storage, the embed keeps the device id and the content ids in memory for the page load only, and keeps no poll answers.
Entries named nxt1.poll-submission…, written by earlier versions of the embed, are deleted in functional and off.
Analytics Events
The embed sends analytics events in every mode, for example when content is shown or a reader interacts with it. An event contains:
- a random event id and the time
- a session id and a mount id: random ids that live in memory for one page load and are never stored
- the origin and path of your page, and the referrer (at most 512 characters)
- the
utm_source,utm_medium,utm_campaign,utm_term,utm_content,gclid,fbclidandmsclkidparameters, if your page’s URL has them - the content the event refers to (content id, version, screen), the event type and its details, such as the action taken or the index of the answer picked
- only in
full: the device id fromnxt1.tika, and the id your page passed tosetUserId
Polls, Quizzes and Forms
A vote, a quiz answer and a form submission are sent with an identifier, so a reader can vote in a poll only once and send a one-per-reader form only once:
| Mode | Identifier sent |
|---|---|
full |
the device id (or the content’s id from nxt1.aid:, if the reader voted before switching to full) |
functional |
the random id for that piece of content (nxt1.aid:) |
off |
a random id held in memory for the page load |
If your page called setUserId, that id is sent as well, in every mode.
Forms that accept any number of responses are sent with no identifier at all. The answers a reader enters in a form are sent to your Organization; which fields a form asks for is up to your editors.