All Collections
Analytics & Performance
How to get individual reader analytics
How to get individual reader analytics

Learn how to start seeing individual analytics and known readers

Dominic Adams avatar
Written by Dominic Adams
Updated over a week ago

In Turtl, you can then collect analytics for individual readers, including the Docs they read, how long they spend in each section, and more.

To see known readers and collect individual analytics you need to do one of the following things:

1. Enable a native Turtl signup form on your Docs

The native Turtl form collects the names and email addresses of readers. When a reader fills in this form, the information is then automatically stored in Turtl and will display the reader under the “known readers” section of the dashboard. The native Turtl form can be enabled on your Immerse sections and the back cover of your Turtl Docs. See more information on how to enable the Turtl form here.


2. Integrate Turtl with your CRM

Reader information is stored in your CRM. To display the name and email address of your readers in your Turtl analytics dashboards, you'll need to let Turtl connect with your CRM.

We currently support integrations for Pardot, Marketo Rest, Hubspot, Salesforce, Eloqua, Dotdigital, Act-On and Microsoft Dynamics.

Once your CRM is connected we'll be able to show your known readers in Turtl, but we still need to know which read is associated with which reader in your CRM. To identify a reader to Turtl you either need to send a lead capture URL to your reader or add a custom form to your content.

Lead capture URLs

A lead capture URL is a link to your content with a unique identifier, allowing Turtl to match our reader ID (a pseudonymized string of letters and numbers) with a contact in your CRM. Lead capture URLs can be sent to your existing CRM contacts. Each CRM has a different way of sending lead capture URLs. You can find instructions for your particular CRM in our integrations section.

Custom forms

If you are looking to collect new contacts and view their reading behaviour in Turtl you will need to add a custom form. When a reader fills out a form their information, along with the reader ID, is sent to your CRM and is either added to an existing contact or used to create a new contact. Turtl can then use the reader ID to display the reader information in analytics. 

You will need to create a form in your CRM and then add it to Turtl. You can find instructions for your CRM in our integrations section.

Note: Once we have identified a known reader through a signup 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 signup form or open a new lead capture URL sent from your CRM.


3. Make your Turtl Doc accessible to specific people only

You can restrict access to your Turtl Docs to specific email addresses or email domains. With this setting, readers will be presented with an access screen requiring them to enter their email address in order to read the Doc. Known reader analytics will then be available for readers that access these Docs.

Important note: In order to capture individual reader analytics for Docs that are accessible to specific people only, you must make sure your team's privacy policy is set in Turtl.

Now your readers will be able to accept the privacy terms and pull through as known readers in the Doc dashboard.


4. Make your Turtl Doc accessible by SSO

Another way to restrict access to your Turtl Docs is with the setting Anyone at My Company, which will require you to sign in via your company's SSO in order to access the Doc. Once the reader has logged into the SSO and navigates the Doc, they will be displayed in the Known Readers section of your Dashboard and have 'Authentication' under the Source column.

For more information, check out these Frequently Asked Questions regarding analytics in Turtl.

Did this answer your question?