You can add an Account Engagement tracking code to your Turtl Doc(s) to send reader activity - page views, to Account Engagement when the user interacts with a Turtl Doc. Once this activity data is in Account Engagement, it can be used to support various processes.
How to enable the tracking code
To enable the tracking code, please follow the steps below:
1. Access the Integrations Hub
To access the Integrations Hub, click on "Integrate" on the left hand menu.
The Integrations screen will show all available integrations in a grid layout.
2. Enable the tracking code
Click on Pardot, under the settings tab, click on "Reader Intent Data" to expand the section.
Toggle on the setting to enable the tracking code for all Docs.
What information does the tracking code collect by default?
Page visit URL (Turtl Doc URL in our case)
Number of page views
Type of session (eg. Entry point, Last page viewed)
Time spent on the page
Date and time of the session
How does the collected information appear in Account Engagement
You can set up a test Doc, flip through it, and then check if the page views for that Doc came through. You can see these events in two key places:
1. In the Visitors report
Visitor and Prospect visits and page views can be found in the Visitors report.
To access the visitors report, navigate to "Prospects" -> "Visitors". The data appears in the visitor table under the graphs that display basic information about your visitors.
2. In the Prospect activities
Select a prospect from the visitor table in the Visitor report or the Prospect List under "Prospects" -> "Prospect List".
Prospect activities are visible from the "Overview" or the "Activities" tab.
Click on a 'Visit' activity to see the full list of page views.
How can we customize the tracking code to send custom Turtl events to Account Engagement?
If you are on Turtl’s Grow AI or Scale AI plan, our engineering team can customize the standard tracking code to send through additional events from Turtl to Account Engagement that aren’t captured within the standard tracking script.
The table below outlines the additional events we can send to Pardot.
As part of the setup process, please let us know which of the following events you’d like to send. It’s a good idea to keep this as light as possible so you’re not overloaded with information.
Notes:
Properties in bold can be used for all events; other properties are event-specific.
Words between braces are data types/field types, eg, Page URL (string) → Page URL value is a string.
Please contact our support team to share your ideas if you want to track something else.
Custom events list with properties
Event name | Custom properties | Action | Notes |
Chapter page turn | Doc name (string) Workspace (string) Page title (string)
| chapterPageTurn | Title page turn
|
Page turn | Doc name (string) Workspace (string) Page title (string)
| pageTurn | Content page turn |
Read time 30 seconds | Doc name (string) Workspace (string) Page title (string)
| readTime30Seconds |
|
Read time 1 minute | Doc name (string) Workspace (string) Page title (string)
| readTime1min |
|
Read time 2 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime2min |
|
Read time 3 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime3min |
|
Read time 4 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime4min |
|
Read time 5 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime5min |
|
Read time 8 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime8min |
|
Read time 10 minutes | Doc name (string) Workspace (string) Page title (string)
| readTime10min |
|
Enter chapter | Doc name (string) Workspace (string) Page title (string)
| enterChapter | Enter Content page(s) |
Leave chapter | Doc name (string) Workspace (string) Page title (string)
| leaveChapter | Leave Content page(s) |
Logo click | Doc name (string) Workspace (string) Page title (string)
| logoClick |
|
Contents menu click | Doc name (string) Workspace (string) Page title (string)
| contentsMenuClick |
|
Download the PDF version | Doc name (string) Workspace (string) Page title (string)
| downloadThePdfVersion | PDF download button in the Contents menu |
Open fullscreen | Doc name (string) Workspace (string) Page title (string)
| openFullscreen |
|
Link click | Doc name (string) Workspace (string) Page title (string) Label (string) Destination (string) | linkClick |
|
Lead capture form submission | Doc name (string) Workspace (string) Page title (string)
| leadCaptureFormSubmission |
|
Personalization form submission | Doc name (string) Workspace (string) Page title (string)
| personalizationFormSubmission |
|
Poll submission | Doc name (string) Workspace (string) Page title (string) Question (string) Response (string)
| pollSubmission |
|
Share button click - Email | Doc name (string) Workspace (string) Page title (string) Share button location (string) | shareButtonClickEmail | Share button location custom property specifies the location where the share button was clicked:
|
Share button click - X | Doc name (string) Workspace (string) Page title (string) Share button location (string) | shareButtonClickX | Share button location custom property specifies the location where the share button was clicked:
|
Share button click - Facebook | Doc name (string) Workspace (string) Page title (string) Share button location (string) | shareButtonClickFacebook | Share button location custom property specifies the location where the share button was clicked:
|
Share button click - LinkedIn | Doc name (string) Workspace (string) Page title (string) Share button location (string) | shareButtonClickLinkedin | Share button location custom property specifies the location where the share button was clicked:
|
Share button click - Xing | Doc name (string) Workspace (string) Page title (string) Share button location (string) | shareButtonClickXing | Share button location custom property specifies the location where the share button was clicked:
|
View chart | Doc name (string) Workspace (string) Page title (string) Label (string) Source (string) | viewChart |
|
View image | Doc name (string) Workspace (string) Page title (string) Label (string) Source (string) | viewImage |
|
View map | Doc name (string) Workspace (string) Page title (string) Source (string) | viewMap |
|
View PDF | Doc name (string) Workspace (string) Page title (string) Source (string) | viewPdf |
|
Watch video | Doc name (string) Workspace (string) Page title (string) Label (string) Source (string) | watchVideo |
|
Listen to audio | Doc name (string) Workspace (string) Page title (string) Label (string) Source (string) | listenToAudio |
|
View Matterport tour | Doc name (string) Workspace (string) Page title (string) | viewMatterportTour |
|
Creating custom events (Page actions)
To receive custom events we send with the modified tracking code, you need to create a separate Page action for each one in your Pardot first.
Open the Page Actions page.
In Account Engagement, select "Marketing" -> "Automation" -> "Page Actions".
In the Lightning app, open the Automations tab and then select Page Actions.
Click "+ Add Page Action".
Name the page action (we recommend Event Name).
Enter the event URL.
Use: https://<tenantHostname>/forms/turtl.forms.pardot.v1.pageaction.html/action=<action>/*
Where you:Replace <tenantHostname> with your Turtl domain (e.g. team.turtl.co)
Replace <action> with the Action value from the table above.
Example:
https://team.turtl.co/forms/turtl.forms.pardot.v1.pageaction.html/action=downloadThePdfVersion/*
(Optional) Select "Priority Page" if you want to call out this page view as a separate prospect activity, instead of bundling them with other page views.
When finished, click "Create page action".
How do these custom events appear in Account engagement?
You can create a test Doc and trigger the custom events you have set up.
All custom events (Page Views) will be displayed bundled in a Visit activity, with information (Event name, properties) logged under the "URL/Title" section.
If you check the "Priority Page" checkbox when creating your custom event page view, it will also get called out as a separate prospect activity.
In Prospect Overview:
In Prospect's Activities:
In addition, you can view the list of prospects that triggered certain events by navigating to "Marketing" -> "Automation" -> "Page Actions" and selecting a specific Page action.
