Note: This feature is available on our Grow and Scale plans, and isn't available on Adopt. Please contact support if you want to upgrade your plan.
Turtl analytics dashboards let you monitor the performance of your content. For a more customized solution, Turtl also supports daily transfer of the data points collected in read reports into an external analytics platform of your choice, such as Tableau or Power BI.
Why set up scheduled data delivery?
This automated process makes it easy to integrate Turtl data into your current analytics workflows, making sure you always have the latest information for thorough analysis.
Since Turtl Docs continuously collect analytics data, it's helpful to automatically and regularly import it into other platforms, eliminating the need for manual intervention.
By receiving data in an external analytical platform, you can use familiar tools with customizable features and dashboards designed to your specific needs.
Consolidating analytics data from various online channels and services into one platform simplifies data comparison and analysis.
It enables your analytics or marketing experts to use this data without needing to log in to Turtl or require a license.
What's included in the report
By default, scheduled data delivery sends the same data as the reads report you can download from your analytics dashboard. Each file covers the previous day's activity and contains one row per read, with the following groups of fields:
Read details: The tenant, a unique read ID, the Doc URL that was read, the timestamp of the read, and the date of the export snapshot.
Doc and Workspace details: Doc ID, title, format, use case, topics and labels, the Doc author, and the Workspace ID and name.
Reader details: Reader ID, email and name, job title, department and phone number, plus the CRM or marketing platform the reader's record came from.
Account reveal: The identified account, the provider that identified it, and the source of the match.
Personalization: The Personalization ID and title, who created it, and the batch it belongs to if it was created as part of a batch.
Traffic source: UTM campaign, source, medium, term and content, how the reader arrived, and whether the Doc was read in an iframe or a lightbox.
Device and location: Device type, browser and version, operating system and version, IP address, and the reader's country and city.
Engagement counts: Sessions, reads and sign-ups, plus counts of clicks on links, charts, images, polls, audio, video, share options and PDFs.
Time spent: Total reading time, split by Title and Content pages, and time spent viewing images, PDFs and charts or playing audio and video. All times are recorded in milliseconds.
Read status: Whether the read was initialized, whether the reader interacted with the Doc, and whether the read came from a banned IP address.
You can download an example file to see the full list of columns and how the data is structured. For a definition of each individual column, see How to download the contact analytics activity.
Notes:
Account reveal fields are included in the standard report, but they're only populated for reads where an account was identified. In the example file they show as "N/A", because the example is taken from a tenant without Account Reveal data.
If you need data that isn't in the standard report, we can build a custom report for you. Scoping is required to work out which Turtl data to include, so please get in touch with professional-services@turtl.co for a quote.
How does it work?
Every day, Turtl sends raw reads data exports as CSV files to your storage container. You can choose to receive these files in one of the following locations:
Each CSV file contains data from the previous day. The delivery process begins at 7 AM UK time and continues sequentially. The exact timing may vary slightly depending on the queue and the complexity of the data delivery job.
Getting started
To set up scheduled data delivery, contact your Customer Success Manager or Turtl support and provide the details for your chosen data delivery platform.
AWS S3 bucket
Region | string | an AWS region - for example, eu-west-1 |
Access_key_id | string | an AWS access key ID |
Secret_access_key | string | an AWS access key secret |
Path | string | the S3 bucket path where data is going to be delivered |
Google Cloud Storage (GCS)
Client_email | string | the email associated with your GCS service account |
Private_key | string | the private key for your GCS service account |
Path | string | the GCS bucket path where data is going to be delivered |
Note: The GCS service account needs the storage.objects.create permission for this to work.
sFTP
Credentials | string | SSH keys or username and password |
Path | string | the location where the data will be delivered |
Next steps
Once we have your credentials, we'll complete the setup. Your Customer Success Manager will notify you when everything is ready.