Data stream fields
The Renta Javascript SDK supports integration with the following data warehouses:
Snowflake
Google BigQuery
Clickhouse
Two tables will be created in your data warehouse after successful integration: events and sessions.
Event table
All events that you have configured using the Javascript SDK will be sent to the data warehouse in real-time.
Session table
Sessions are inserted once a day at 02:00 UTC.
Below you can get acquainted with the structure of the tables and the description of the fields.
Structure of the event table
Field name | Type of data | Description |
---|---|---|
dateTime | datetime | Date and time of the event in UTC |
date | date | Date of the event in UTC |
sendAt | datetime | Date and time when the event was sent from the client side |
eventId | String | Unique Event ID |
eventType | String | Event type |
eventName | String | Event name |
properties | String | Json object that contains custom event attributes |
anonymousId | String | Unique cookie values |
userId | String | UserId number. Contains the value passed to Google Analytics. |
groupId | String | Unique group value (only available for a group type event) |
content | String | Maintance of utm_content |
medium | String | Maintance ofutm_medium |
source | String | Maintance of utm_source |
term | String | Maintance of utm_term |
campaign | String | Maintance of utm_campaign |
dataSource | String | The data source for the request. Initialy, requests from analytics.js they will have the web value, and requests from the mobile SDK will have the app value. |
device | String | Device type: desktop, tablet, mobile, TV. |
deviceBrowser | String | Browser (for instance, Chrome or Firefox). |
deviceBrowserVersion | String | Browser version. |
deviceOperatingSystem | String | Operating system(for instance, Macintosh or Windows). |
deviceOperatingSystemVersion | String | Operating system version. |
deviceIp | String | IP-adress |
country | String | Country |
city | String | City |
region | String | Region |
deviceUserAgent | String | User Agent |
deviceScreenHeight | Int | Resolution of the user’s screen in pixels by height |
deviceScreenWidth | Int | Resolution of the user’s screen in pixels by width |
deviceViewPortHeight | Int | The size of the viewing area in the browser by height |
deviceViewPortWidth | Int | The size of the viewing area in the browser by width |
deviceDocEncoding | String | Encoding. For instance, UTF-8. |
location | String | URL with additional parameters. For instance: https://site.com/catalog/platya?page=2 |
hostname | String | Domain. For instance: https://site.com/ |
path | String | Path of the pages URL. For instance: /catalog/platya |
title | String | Title of the page. |
page | String | The full URL path. For instance: https://site.com/catalog/platya |
documentReferrer | String | If the medium field has the referral value, the path of the traffic source is indicated here, and the host name is contained in the source field. |
fbclid | String | The Facebook Ads click ID that is passed to the URL when the ad is clicked. |
gclid | String | The Google Ads click ID that is passed to the URL when the ad is clicked. |
ydclid | String | The Yandex Direct click ID that is passed to the URL when the ad is clicked. |
ga_cookie_id | String | The unique meaning of Google Analytics cookies |
ym_cookie_id | String | The unique meaning of Yandex Metrika cookies |
fbc_cookie_id | String | The unique meaning of Facebook cookies |
fbp_cookie_id | String | The unique meaning of Facebook cookies |
offset | String | A service parameter of the Javascript SDK. Used to count sessions (the session table is only available in integration with DWH). |
Structure of the session table
The Renta Javascript SDK generates sessions based on Google Analytics logic.
Column name | Description |
---|---|
sessionId | Session number. It’s a unique value. |
anonymousId | The unique identifier of the Renta Javascript SDK cookie. Sets at the device level. |
userIds | Array of userId values. |
eventIds | A list of events that are included in the SessionID. |
totalHits | Number of events within the sessionю |
transactionIds | Transaction IDs that were reached within the sessionю |
totalTransactions | The number of transactions that were achieved during the session. |
totalPageviews | Number of pages viewed. |
totalEvents | Number of events. |
timestamp | Time in Unix Timestamp format. |
dateTime | Session start time in UTC. It’s the first dateTime within the session. |
dateTimeLast | The end of the session in UTC. It’s the last hit within the session. |
date | Session start date in UTC. |
secondsInSession | Session duration in seconds. |
content | Content of utm_content |
medium | Content of utm_medium |
source | Content of utm_source |
term | ent of utm_term |
campaign | Content of utm_campain |
gclid | Contains Google Click ID if auto-tagging between Google Ads and Google Analytics is enabled. |
device | Device type: desktop, tablet, mobile, TV. |
ip | IP of the device |
city | City |
country | Country |
region | Region |
browser | Browser |
browserVersion | Browser version |
operatingSystem | Operating system |
operatingSystemVersion | Operating system version |
landingPage | The landing page on the site. It’s the page of the first hit. |
hostname | Domain name. Identifies by landingPage. |
exitPage | Exit page. It’s the last page viewed during the session. |
bounce | Returns one if there was a failure within the session. The failure is fixed if there was only one hit in the session. |
visitSession | The user’s session number. If this is the first session, the field is set to 1. |
newVisits | If this is the first visit, then 1. In other cases, an empty value. |
documentReferral | Domain name, ignoring utm tags. For instance, if the transition was from http://convert.ua/contacts?source=test, then documentReferral = convert.ua. |
documentReferrer | The full address of the page from which the transition to the site was made. The logic is similar to documentReferral, but returns the full path of url: http://site.com/contactsНазвание таблиц |
You can specify the name of the tables in the integration configuration:

Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.