raw_hits

The raw_hits table is a "hit" scope table. This means it records all incoming tag calls (page_view or event).

---

Syncing

Hits appear in the raw_hits table once the session to which they belong has expired, which occurs after a 30-minute period of inactivity following the last hit.

---

Tables and definition 🔗

Source : https://dbdiagram.io/e/67bf2e04263d6cf9a08d27a6/67c08ae8263d6cf9a0b33078

---

Fields definition

datetime

Date and time when the hit was recorded. Automatically created by Quanti: but overridable if is needed.

hit_id

Unique hit identifier. Automatically created by Quanti:.

session_id

Unique session (can be also called visit) identifier. A session is a set of events from the same visitor. It ends when the tag does not record any events for 30 minutes. session_id is automatically created by Quanti: from the value of a cookie placed on the user's browser by the tag. A visitor can make multiple sessions. session_id can be modified. it means you can override by pushing your own value in the tag

visitor_id

Unique visitor identifier. Automatically created by Quanti: from the value of a cookie placed on the user's browser by the tag. One visitor = One browser. A visitor_id can be associated to multiple hit_id and session_id. It can be overridable if is needed like in a server-side setup.

user_id

Unique user identifier. This identifier has to be specify in the tag. Typically the value is based on a hashed version of the user's email address (using SHA256, for example).

A user (identified by a user_id) can have several devices, and therefore several browsers (identified by several visitors_id). They can have multiple sessions (identified by multiple session_id) during which they navigate from page to page and record multiple events, event and page_view (identified by multiple hit_id).

Explanation of the Different Types of Identifiers

device_type

The type of device automatically recovered by the tag when the hit was recorded. 3 possible values : desktop, mobile, or tablet. It can be overridable if is needed like in a server-side setup.

url

The current URL of the page automatically recovered by the tag the hit was recorded but overridable if is needed like in a server-side setup.

conversion_id

Unique conversion identifier. This identifier is generally generated by your site / back-end and it has to be specify in the tag. It makes possible to identify each conversion. This field is logically populated only on the hit that recorded the conversion.

conversion_value

Monetary value of the conversion generated by the site and specify in the tag. This field is logically populated only on the hit that recorded the conversion.

conversion_type

The type of the conversion generated by the site and specify in the tag. It can be a lead, a purchase, a secondary conversion, etc. This field is logically populated only on the hit that recorded the conversion.

consent

The value of consent expressed by the user upon arrival on the site and retained throughout their navigation. It generated by the site and specify in the tag. This field can be used to do statistics on the consent users by filling it with a list of vendors or typologies of cookies accepted by the user.

event

The type of event. This can be an 'event' or a 'pageView' depending on what was specified in the tag when the hit was recorded.

event_category

A parameter useful to categorize events. Typically the object that was interacted with. It has to be specify in the tag.

event_action

A parameter useful to categorize events. Typically the type of interaction. It has to be specify in the tag.

event_label

A parameter useful to categorize events. Typically label given to the event. It has to be specify in the tag.

event_value

Numeric value associated with the event. It has to be specify in the tag.

account_id

Unique account identifier given by Quanti: during tag creation. It can't be modified.

referrer

The referrer is the visitor's originating page. In other words, it is the page that precedes the tag call. Automatically recovered by the tag during the hit but overridable if is needed like in a server-side setup.

user_agent

Technical informations about your browser. Automatically recovered by the tag during the hit but overridable if is needed like in a server-side setup.

product_ids

A parameter useful to recover informations about products. usually a JSON is pushed in this field

ad_user_data

Controls the sending of user-identifiable data for advertising purposes.

ad_storage

Controls the use of data for personalized advertising (e.g., remarketing, audience targeting).

ad_personalization

Controls the use of local storage for advertising purposes (e.g., marketing cookies).

analytics_storage

Controls the use of storage for analytics data.