Web container generator
- Use IAB TCF GVLv3 in Trust banner generation
- Internal update of
tC.trigger()
to update the event format - Support legitimate interest policy urls for IAB TCF GVLv3 vendors
- Support GPC activation by privacy banner
- Support various URLs for IAB vendor list
- Support new "illustrations" attribute for IAB TCF GVLv3 purposes, specialPurposes, features and specialFeatures
- Update handling of hidden subcategories
- Support dataRetention & dataCategories attributes published in IAB TCF GVLv3
- Support localization of vendor policy URLs included in IAB TCF GVLv3
- Fix Privacy GPC handling when statistics are included in privacy scope
- Fix
tC.isCookieEnabled()
in iframe context
- Privacy - Add an option to handle Global Privacy Control
- Privacy - TCFv2 - Add
tC.privacy.getNbIabVendors()
- Optimize OnSite consent API to make IAB TCFv2 consent available sooner
- Update IAB TCFv2 module to protect from wrong vendor configuration in IAB TCFv2 official vendor list
- Fix collision on TCSESSION 1st party cookie between TagDedup and Campaign tracking
- Fixes a generator bug introduced on the 30/03/2023 (side-effect from a generation engine upgrade)
- The bug was causing an ordering issue where Tags may be loaded in a different order from before
- It is highly recommended you generate a new version for containers generated between the 30/03/2023 and the 04/04/2023 to prevent any unexpected behavior on your website
- Update IAB TCFv2 module to automatically add vendor number to banner text (new TCF requirement)
- Trigger module update to add
tC.generateEventId()
and allow to pass a specific event id to the trigger API
- Trigger module update for Rakuten and Microsoft UET integration
- Internal upgrade of the generator engine. Greatly improves generator performance. This upgrade should not impact the generation result, though we recommend that you test your first generated container before your next deployment.
- Refactoring on various TagCommander modules
- Add tc_privacy_do_not_track flag
- Refactoring on the TagDeduplication
- Refactoring on the tC.privacy module
- Add new Consent OnSite API commands:
consent.onReady
consentBanner.show
consentBanner.hide
consentCenter.show
consentCenter.hide
- Refactoring on the Privacy Banners
- Refactoring on the tC object initialization
- Update
tC.setCookie
to encode!'()~
characters in the cookie value. This is a requirement for WAF restrictions of some TagCommander users.
- Update
tC.privacy.hit
to not send hits when analytics category was refused using consent JS OnSite API
- Update
trigger
JS OnSite API to better use source-keys in multi-container contexts
- Update
tC.setCookie
to useencodeURIComponent
instead ofescape
(deprecated)
- Update page data format in
cact('trigger')
API
- Refactoring on privacy hits generation
- Better handling of old .tagcommander.com domain redirections on Tag Deduplication
- Improve tC.privacy.getCategoryIdList
- Fix domain detection
- Do not mutate
cact()
arguments
- Automatically integrate domains set up in Domain Management
- Make consent data available in
consent.get
before privacy file is loaded
- Add refused_vendors in CAX events
- Fix blocked on categories not sent in CAX events
- Integrate TrustCommander settings with DataStorage cookies
- Commanders Act - Platform X Source keys enabled on all web containers
- Add page and device information in OneTag events
- Improve TrustCommander event format.
list_categories
is renamedoptin_categories
.optout_categories
are now included in the event.
- Improve setCookie domain detection
- Tag Deduplication - Add a (programatic) option to not use tc_cj_v2 encryption. This is a requirement for WAF restrictions of some TagCommander users.
- Store generated versions on remote server (no more NFS usage)
- Fix tC.log escaping
- Fix minor tags generation
- Integrate
tC.trigger
/cact('trigger')
natively inside web containers
- Tag Deduplication - Fix campaign/medium cookie initialization
- Include blocked on categories in Privacy hits
- Refactoring on Privacy Banner Templates
- Tag Deduplication - Fix launcher on "bypass" setups
- TrustCommander - Fix analytics for setups where it is set as blocked on category
- TrustCommander - Fix
tC.privacy.getBlockedOnCategories
- Add new Consent OnSite APIs:
consent.onUpdate
consent.update
consent.revoke
- Add
consent.get
OnSite API
- Privacy - Rework parameters inclusion
- Privacy - Fix categories statistics sending
- Privacy - Fix missing TCID on some opin hits
- Privacy - Optimize vendor statistics when visitor is optin to all vendors
- TrustCommander - Integrate Google ACM
- Improve generator performance
- Update vendor statistics format
- Fix optional modules inclusion in unminified web containers
- Fix TC_PRIVACY cookie content caused by a retro-compatibility issue with old banners
- Fix privacy vendors initialization
- Fix privacy vendors usage in TMS
- Integrate __tcfapi stub
- Use privacy vendors in TMS
- Set consent duration by Privacy banner
- Fix vendor encoding in web containers
- Fix tC.events sorting
- Fix internal variable initialization on container reload
- Fix internal variable initialization on container reload
- Deactivate tC reach
- Fix privacy statistics on optin all
- Fix privacy statistics intialization from container
- Fix privacy statistics intialization from container
- Fix Tag Deduplication initialization on container reload
- Do not run Privacy code when cookies are disabled
- Refactoring on generator code base
- Fix tC.event initialization on container reload
- Fix to avoid reloading tC.event when triggred on Dom Ready
- Fix conflict between containers when initializating internal variables
- Fix Tag Deduplication by merging config when multiple containers are on the same page
- Add
tC.isCookieEnabled
- Add more details for privacy statistics on optin all
- Security fix
- Fix platform user rights
- Fix privacy analytics
- Fix TCPID in privacy analytics
- Add option to disable TCPID
- Privacy - add custom separator and domain
- Fix custom events to work without second argument
- Fix tc_array_events object initialization
- Refactoring for Privacy Standalone
- Fix privacy analytics
- Fix
tC.array_launched_tags
initialization
- Fix
tC.privacy.validRules
initialization
- Refactoring on Privacy Templates (Privacy v2)
- Add custom privacy default status (optin/optout) for tags
- Add option to set default privacy default status (optin/optout) for banners
- Privacy - On Premise option
- Fix Browser Extension error
- Fix tC.event on mutli-container contexts
- Fix Dom Ready Trigger
- Handle dynamic change of version from Browser Extension
- Initial release of TagCommander v2
Last modified 1mo ago