This article will cover the following frequently asked Analytics questions:

The total number of times a Turtl Doc was opened and the contact 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 action, this is counted separately as a read.
​

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

If you want to be able to calculate the bounce rate yourself, here is how you can arrive at the bounce rate number as it appears on the dashboard from the reads analytics report.

As explained here, the formula we use is this one:

Math.round(((allReaders - readers) * 100) / allReaders) || 0;

allReaders can be obtained by applying the following filters to the reads Analytics report:

To get readers, the steps are the same, but you would need to additionally remove any rows where count_read is 0 before counting the unique values.
​

This depends on the type of embed.

If your Doc is embedded on your website via an iframe, Turtl can only detect reads, but not bounces. In other words, we can't know how many people came on the website and landed on the Turtl Doc, we can only detect the people who have turned a page or otherwise engaged with the embedded Doc. For this reason, we exclude the reads from the overall bounce rate calculations, as it would skew the analytics for that Doc. We suggest embedding a Doc via lightbox if this metric is important to you.

Turtl can block analytics data for certain IPs or CIDR IP groups. This means that the data from blocked IPs is not displayed on the dashboard 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. The maximum number of IPs that can be blocked is 525,000.
​

Please turn to Customer Support 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.

If you set the timeframe to the last 30 days and download the reads report CSV file you will get reads for today minus 30 days (so, excluding today).

If you also need today's reads (up to 5 minutes ago) you can select a custom timeframe and set today as an end date and you will have today's reads included in the downloaded CSV file.

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 contacts 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 contact will actually be counted twice.

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

Known contacts 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 enter the same email, it will be matched against the existing reader_email, so the total number of unique known contacts will be accurate.

The sign-ups can either come from a native Turtl form on the Back cover or Content pages or a third-party form on the Cover, Back cover, or Content pages. 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 contacts can be identified through:

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

It is also worth noting that once we have identified a known contact through a sign-up form, lead-capture URL, etc., we will be able to collect the known contact's analytics across other Turtl Docs they read, too, even if they weren't identified again through one of the above methods.

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

Users may create several unique reader_ids, which count towards contacts if they log in from different browsers or devices, but we only display unique email addresses as known contacts. This can be checked if you count unique reader_id entries against unique reader_email entries in the Reads raw data report.

Being logged into Turtl will exclude contacts from being shown in the contacts section. If a signup comes from a list of banned IPs, they will not add to the number of signups.

This is where your known contact 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 contact 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 contact), the store that identified them first will be written in the “Known contacts” section.

Example:

First, a company sends a Turtl doc with lead capture URLs from their CRM, which already identifies a contact.

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

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

Yes, it does! We don’t show analytics of removed personalizations and Doc analytics dashboards. If a Doc is deleted, we don’t show its analytics on the team dashboard.

You may encounter a situation where you can see a contact clicking on a URL in a Content page but the analytics are showing the page performance time as n/a for an individual contact.

The Avg. Content page time is shown as n/a if a contact lands on a Content page and does not flip that Content page or go to the Title page.

It means that our geoIP database did not know which country a certain IP belongs to.

Engagement score is a metric that is available to measure both content and contacts.

It is calculated using three main normalized components:

The engagement score = sum of the above components * 100

Turtl includes built-in logic to automatically detect and exclude analytics events triggered by bots. If you still have concerns about possible bot traffic, please contact the Support Team, and we’ll be happy to help block any identified bot IPs.

Global Admins and Admins have full visibility across the account, including access to all workspaces and analytics for every Doc.

Workspace Owners, Publishers, Editors, and Analysts can view analytics only for Docs within the workspace they are assigned to.

Personalizers have access solely to analytics for Personalization Docs in their designated workspace.