Transparency & Consent
Features documented here are only available for giosg script v2. If you are using the giosg script v1, please contact giosg support for more details on how to upgrade.
This document describes the implementation of Transparency & Consent (TC) in giosg products. Implementing this TC framework to your site will assure that giosg services continue to work in the future. If not stated otherwise by the site containing giosg products, we will assume that no consent is granted and start only those services that can comply with the given consent.
Changes to existing features¶
- If visitor has not given consent for cookies or gives it after the visitor variables are sent, they are not attached to the current visitor on the page.
My site uses IAB TC Framework¶
Please check the implementation guide for IAB TC Framework.
My site uses some other TC Framework¶
Please check the implementation guide for other TC Frameworks.
Required purposes and their usage¶
|1||Store and/or access information on a device||Cookies and local-/session storage are used|
|2||Select basic ads||Used to present basic ads where applicable|
|4||Select personalized ads||Used to provide ads based on user previous actions where applicable|
|6||Select personalized content||Used to provide content based on user actions where applicable|
|7||Measure ad performance||Used to gather statistics on ad performance where applicable|
|8||Measure content performance||Used to gather statistics on content performance where applicable|
|10||Develop and improve products||Usage data gathered for product development and improvement purpose|
More detailed information regarding Purpose IDs can be found from IAB Europe Transparency Consent Framework Policies.
Purpose usage and explanation¶
|Purpose ID||Chat button visible on the page||Chat / Video||Interactions||Rules||Visitor analytics|
*Feature will work partially without this purpose.
|Purpose ID||Chat / Video||Interactions||Rules||Visitor analytics|
|1||Allows chat/video session identifiers and visitor related identifiers to be saved.||Allows interaction state to be saved for example which part of the interaction the visitor is or is the interaction shown already.||Rule execution related data is saved for example has rule matched.||Allows visitor related identifiers to be saved.|
|2||-||This is applicable if the interaction is an ad. Allows it to be shown.||-||-|
|4||-||This is applicable if the interaction is not an ad and uses some visitor related information to customize the behavior. Allows it to be shown.||-||-|
|6||Allows the chat/video session to be retrieved for example after visitor reloads the page.||This is applicable if the interaction uses some visitor related information to customize the behavior. Allows it to be shown.||Allows rules to use visitor information to match for example visit counts, page reloads, sessions, etc.||-|
|7||-||This is applicable if the interaction is an ad. Allows the performance(impressions, clicks, etc.) metrics to be collected.||-||-|
|8||Allows collection of general visitor information(time on page, current url, etc.) related to the visit.||This is applicable if the interaction is not an ad. Allows the performance(impressions, clicks, etc.) to be collected.||-||Allows gathering analytics of user actions.|
|10||Allows metrics of system and service behavior to be collected and used to improve services.||-||-||Allows metrics of system and service behavior to be collected and used to improve services.|