This article will cover the following frequently asked analytics questions:

The total number of times a Turtl Doc was opened and the reader explored beyond the first page. If they don’t turn the first page within 30 minutes, they are counted as a bounce. If they come back after 30 minutes and take an action, this is counted separately as a read.

Session is umbrella

What constitutes a reader when there is a public personalisation form?

Anyone who completes the form and lands on the doc itself, then explores beyond the first page.

Following the above definition of a read, if you have 100 readers open a Doc, 30 "read" it by taking an action and 70 take no action before closing, then your bounce rate is 70%.

Turtl can block analytics data for certain IPs. This means that the data is not tracked or recorded anywhere in our system for the time during which IPs are blocked. By blocking IPs, we also filter the analytics data that was generated by the same IPs before they were blocked.

Please turn to support@turtl.co or your customer success manager with a list of IPs you wish to block and they will arrange it for you.

Unblocking IPs will retrieve the data that was generated before blocking. However, the data that may have been generated during blocking will be lost forever.

The Reads Report data export is pulled from a database that gets refreshed every 24 hours. This means that it will be displayed with one day of delay.

We do not collect analytics events for logged-in Turtl users.

If you log into Turtl via SSO and we match your email address with a corresponding one in the tenant, you will be logged in just like any other user and analytics will not be collected.

If we aren't able to match your email address with any of the users in the tenant, you will log in via SSO as a Guest. We do collect analytics events for Guests.

If you submit your email address via a form in a Turtl Doc, we will register and count you as a sign-up, regardless of whether we are collecting your analytics events or not.

Both known readers and guests create unique reader ids (reader_id) when they access a Turtl Doc. If they access a Doc from the same browser/device, they will be matched against the existing id, but if they access it from a different browser/device, a new reader_id will be created, so the same reader will actually be counted twice.

If some readers are counted twice, the total number of (unique) readers as displayed on the dashboard will be slightly higher than it actually is. This is usually not a problem, as readers don’t usually view Docs in different browsers/devices.

Known readers are additionally identified by their email address (reader_email), so when they log in with their email (which is the case in the above access settings), a reader_email entry is created. If they happen to log in from a different browser/device and they enter the same email, it will be matched against the existing reader_email, so the total number of unique known readers will be accurate.

The sign-ups can either come from a native Turtl form in the back cover or in the immerse section or a third-party form anywhere on the doc. If a sign-up is created with the same email address multiple times, each sign-up will add up to this number. For a more in-depth analysis of sign-ups, please download Reads raw data.

Known readers can be identified through:

This means that the no. of known readers may be higher than the no. of sign-ups.

It is also worth noting that once we have identified a known reader through a sign-up form or a lead capture URL, we will be able to collect known reader analytics across other Turtl Docs they read, too, even if they don’t fill in another form.

However, if the reader clears their browser cookies, we won’t be able to track known reader analytics until they complete a new sign-up form, or open a new lead capture URL.

Being logged into Turtl will exclude readers from being shown in the Known reader's section. However, if a logged-in user completes the sign-up form, they will be counted towards the number of signups.

If a signup comes from a list of banned IPs, they will not add to the number signups.

This is where your known reader information is stored. If your CRM is integrated with Turtl, your CRM will show here. Turtl will appear if you don't have one set up. Internal means the reader had access to the Doc either through SSO or email authentication (Source will show as 'Authentication' in this case).

If a person completes the form when they’re already identified (a known reader), the store which identified them first will be written in the “Known readers” section.

Example:

First, a company sends Turtl docs with lead capture URLs from their CRM, which already identify a reader.

Then, the reader is prompted to fill out a Turtl form to sign up for a webinar or newsletter, etc.

In this case, the known reader's lead store is a CRM (Hubspot, Eloqua, etc. ) and not Turtl.