Turtl comes with its own powerful analytics engine as standard. All contact behavior is tracked here and made available for interrogation via our user-friendly dashboards.
Tracking codes with default events
You can add a default CRM tracking script to your Turtl Doc(s) to send contact activity, e.g. Turtl page visits, to a CRM of your choice - we currently support tracking scripts for:
Tracking codes with custom events
With some services, like Marketo, HubSpot, and Google you can also send other analytics events through a custom events setup.
Turtl’s analytics uses an events-based system, so whenever a contact takes an action within a doc, a corresponding event is emitted. The following actions trigger an event:
Event name | What it captures | Variables | Notes |
Chapter page turn | Reader moves between Chapter pages — the horizontal navigation across top-level sections of a Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) | Chapter page turn |
Page turn | Reader moves between Content pages within a chapter — the vertical reading flow inside a section | doc_name (string), doc_url (string), workspace (string), page_title (string) | Content page turn |
Read Doc 30 sec | Reader has spent 30 seconds engaging with the Doc — first signal of meaningful attention | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 1 minute | Reader has spent 1 minute engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 2 mins | Reader has spent 2 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 3 mins | Reader has spent 3 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 4 mins | Reader has spent 4 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 5 mins | Reader has spent 5 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) | Common threshold for "high intent" segments |
Read Doc 8 mins | Reader has spent 8 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Read Doc 10 mins | Reader has spent 10 minutes engaging with the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) | Strong indicator of deep engagement / MQL signal |
Enter chapter | Reader enters a Content page within a chapter | doc_name (string), doc_url (string), workspace (string), page_title (string) | Enter Content page(s) |
Leave chapter | Reader leaves a Content page within a chapter | doc_name (string), doc_url (string), workspace (string), page_title (string) | Leave Content page(s) |
Logo click | Reader clicks the brand logo in the Doc toolbar — typically redirects to a customer's home page | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Contents menu click | Reader opens the Doc's contents menu to navigate between sections | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Download the PDF version | Reader downloads the PDF version of the Doc from the Contents menu | doc_name (string), doc_url (string), workspace (string), page_title (string) | PDF download button in the Contents menu |
Open fullscreen | Reader expands the Doc into fullscreen view | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Link click | Reader clicks any internal or external link inside the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), destination (string) | destination captures the target URL; label captures the link text |
Lead capture form submission | Reader submits a lead capture form embedded within the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) | High-intent conversion event |
Personalisation form submission | Reader submits a personalisation form, triggering a personalised version of the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string) |
|
Poll submission | Reader submits a response to a poll embedded in the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string), question (string), response (string) | Use question and response to analyse poll outcomes |
Share button click - email | Reader clicks the email share button | doc_name (string), doc_url (string), workspace (string), page_title (string), share_button_location (string) | share_button_location specifies where the share button was clicked: Toolbar / Content page widget / Back cover |
Share button click - X | Reader clicks the X (Twitter) share button | doc_name (string), doc_url (string), workspace (string), page_title (string), share_button_location (string) | As above |
Share button click - Facebook | Reader clicks the Facebook share button | doc_name (string), doc_url (string), workspace (string), page_title (string), share_button_location (string) | As above |
Share button click - LinkedIn | Reader clicks the LinkedIn share button | doc_name (string), doc_url (string), workspace (string), page_title (string), share_button_location (string) | As above |
Share button click - Xing | Reader clicks the Xing share button | doc_name (string), doc_url (string), workspace (string), page_title (string), share_button_location (string) | As above |
View chart | Reader opens an embedded chart in zoom (lightbox) mode | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) | label and source identify which chart was viewed |
View image | Reader opens an embedded image in zoom (lightbox) mode | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) |
|
View map | Reader opens an embedded map in zoom (lightbox) mode | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) |
|
View PDF | Reader opens an embedded PDF in zoom (lightbox) mode | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) |
|
Watch video | Reader plays an embedded video inside the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) | Strong engagement signal — useful for video performance reporting |
Listen to audio | Reader plays an embedded audio file inside the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) |
|
View Matterport tour | Reader opens a Matterport 3D virtual tour embedded in the Doc | doc_name (string), doc_url (string), workspace (string), page_title (string), label (string), source (string) |
|
Once this contact engagement data is in your CRM, it can support various processes.
Other client-side scripts
In addition to sending Turtl events to your existing analytics platforms, tracking codes can be applied from other external services to your Turtl Docs to gain deeper insights:
Note: If there is a particular tracking code you’d like to apply that is not on this list, please contact support@turtl.co.
What’s the process of getting the code snippet into Turtl
Once you have the tracking code, please send it to support@turtl.co and we will set it up as an extension for you, which can be toggled on/off on your Turtl Docs. You can also choose to apply this extension to all Turtl Docs automatically.