The Raw Data Export feature allows you to export raw data from Contentsquare at a pageview or session level, to leverage in other tools. You can create, schedule, manage, and run export jobs using the Contentsquare console.
Using this feature you can export the following data:
See full fields reference documentation here.
-
project_id, user_id
-
Session (time, duration, replay link, transactions,...)
-
Page (URL, query, time, interaction)
-
Technology (OS, device, browser, screen)
-
Geo (language, city, country)
-
Performance (load time, dom time)
-
Events (click, tap, scroll, hover, custom,...)
- Errors (JS errors, API errors, Custom errors)
Use the Raw Data Export to:
-
Schedule exports of raw data tables (page views, sessions, users, segments…)
-
Access the export directly from your Contentsquare console
-
Feed your data stores and accumulate data beyond the Contentsquare retention period.
Example use cases:
| Analytics | Cross-reference Contentsquare raw data with data from other sources to unify end-user touchpoints across all platforms (Adobe, Google). |
| Marketing | Leverage segments data in marketing systems (Salesforce, Adobe Oracle, Sap Hybris, Marketo, Insider,...) to drive hyper-personalized and enjoyable experiences, engagement, conversions, and loyalty. |
| UX/UI | Leverage segments data to improve end-user experience (frustration/churn) |
| Business Insights | Leverage data in your BI tools (Tableau, Power BI, Qlikview, Looker,..) for further analysis and visualization. |
| Data Analytics | Push CS data to your data warehouse to run analysis and feed machine learning algorithms. |
| Data Retention | Retain CS data past the contractualized CS data-retention period. |
Access the Raw Data Export feature
1. Click on the Setting icon > Console > go to the Data Export tab.
2. There are two sections in the Data Export tab:
- Data exports (default): schedule new exports and view, edit, activate, deactivate or delete the exports you have already scheduled.
- Recent exports: view the history of your data exports.
Create a data export job
1. Click on “+ Add data export” and choose whether you want to create a one-time job or a recurrent job (you will have the option to choose between daily or hourly jobs later in the process).
-
One-time job: is executed as soon as you validate the form.
- You can extract data for the specified date range (7 days max, and limited to your contractual data retention period)
- You can only query for completed days (meaning you can not query the current day)
- Schedule a recurrent export: either daily (to extract raw data for 1 day, every day) or hourly (to extract raw data for 1 hour, every hour).
2. Name your export, select schedule options, entity type (pageview or session level), and file format.
| CSV with header | CSV with the field names as first row |
| CSV without header | CSV without field names |
| JSON | Each row consists of its own JSON object |
3. Select fields and segments to export.
- Extractable fields will depend on the selected entity type (pageview or session).
4. Select the device you want to extract the data for and click 'Create' to finalize. The created data export will then appear in the 'Data Exports' list.
- “All visitors” is the default segment is selected, which will extract every session.
- If you select several segments, all the sessions that belong to at least 1 of the selected segments will be exported. All the sessions that do not belong to at least 1 of the selected segments will be filtered out and will not be exported.
- In the data, you will get one column per selected segment, with either 1 or 0 as a value depending on whether a session belongs to the segment (1) or not (0).
- You may notice a 4-hour gap, which results from a recurrent job scheduled to run every 4 hours. This default setting optimizes data collection and ensures that reports capture all relevant information.
Manage exports
‘Data Exports’ displays a list of exports that have been configured and scheduled. You can view, edit, delete, duplicate, and suspend/activate schedule exports.
- Click the ‘...’ button for any row to access these options in the drop-down menu
Download exported files
There are two methods for downloading your exports:
To download exported files manually click the download button for the export.
To download files programmatically use the Raw Data API
- Retrieving the files programmatically can be useful, for example, to get all the new files generated by a recurrent job every day (and feed any kind of client application, data warehouses & BI tools, etc.)
FAQs
Who can manage the exports?
Only Contentsquare admin roles can create and manage export jobs from the console.
How long does Contentsquare store the export?
Exports and related files can be accessed for 7 days following their creation giving you time to store them in your preferred tool.
How many jobs can run at once?
A maximum of 10 recurrent jobs (with 1 segment per job) can be active at the same time. You may need to suspend or delete a daily job before creating a new one. A maximum of 1 one-time job can be computing at any given time. But you can put up to 9 more one-time jobs in a queue. Queued jobs will be triggered one after the other, waiting for the current computing job to be completed.
How many jobs can I have total?
You cannot have more than 100 jobs (all status included) listed in the interface. If you reach the limit you will need to delete some of your jobs before being able to create new ones.
How many days worth of data can I export?
For one-time jobs, you can export data from a 7-day period maximum.
How is a day of data defined?
A day runs from midnight to midnight in UTC. The export is agnostic on the time zone (which is user-specific on the platform). All our dates and times are in UTC, that you can still convert to any desired time zone in your own application.
When is an export job triggered?
An export job starts 4 hours after the end of the period being exported to ensure complete data collection.
For example:
• Daily exports are triggered at 04:00 AM UTC.
• For hourly exports, if you’re exporting data from 06:00 AM to 07:00 AM, the job will start at 11:00 AM.
For one-time exports, you can only export data from the last full day; the current day cannot be exported.
How fresh is the data?
For a one-time export and daily export, you’ll be able to export up to the last full day of data. For hourly jobs, at any given time you’ll have up to the last terminated hour minus 4 hours.
What if my export does not download as expected?
Errors that may occur with the Raw Data Export do not appear clearly in the UI. If your expected files are not available in the recent export interface, it means an error occurred and you should try again.
What about mobile events?
Mobile events are not exportable yet as they are too complex and heavy to be stored in files.
How do I target precise elements in my analysis?
Target paths are translated and stored as CS Targets based on DOM structure. If you need to target a precise element, you will need to identify unique paths or rely on your HTML id attributes.
Why can’t I access a session replay link available in my export?
The link may be outside the scope of your contract's session replay retention period and is therefore no longer accessible.
How do I find the primary key for this data set?
For session exports the key is session_id
For views export the key is a combination of the fields session_id + view_number
Why there is a time gap when an export job is configured to be on an hourly basis?
Recurrent jobs are configured to run every four hours, a default setting optimized for efficient data collection and processing. This four-hour interval ensures that the captured data is both comprehensive and current while maintaining system performance. The 4-hour time gap between the Creation Date and the report’s date range is due to this default configuration. Each report reflects data processed up to four hours after the initial date range, ensuring that all relevant information is included.