Consent Management Platform Tag Delivery Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing user consent and data collection in websites are inefficient, leading to redundant tag loading, potential unauthorized data collection, and performance issues due to the lack of connectivity between Consent Management Platforms (CMPs) and Tag Management Platforms (TMPs, as well as reliance on cookies that can be deleted or blocked.
Innovation Solution
A system that delivers only consented tracking tags to websites, using a consent management platform to determine user consent and store tag-selection parameters, and provides a consent prompt tag to gather user consent dynamically, ensuring that only authorized tags are deployed and used, thereby reducing processing load and improving website performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all tracking tags are loaded onto a website, then comprehensive data collection capability is achieved, but website loading speed decreases and processing load increases
Solution Approach 1:
The patent extracts only the necessary tracking tags that have user consent into a separate delivered set, while leaving non-consented tags in the original library. This selective extraction ensures that only authorized tags are loaded onto the website, reducing the total number of tags that need to be processed and thereby improving loading speed while maintaining compliant data collection capability.
Solution Approach 2:
The system performs preliminary consent verification and tag selection before website deployment. By determining user consent status and selecting appropriate tags in advance (before the website is live), the system prepares a pre-filtered set of tags that comply with user preferences. This preliminary action prevents the need to load and then filter tags at runtime, thus improving loading speed.
2Productivity
If tracking tags are loaded without verifying user consent, then data collection is maximized, but unauthorized data collection occurs violating user privacy
Solution Approach 1:
The patent implements preliminary consent verification by checking user consent status before delivering tracking tags to the website. The system determines which tags have user consent in advance and includes only those in the delivered tag set. This preliminary action ensures that data collection is always authorized, eliminating unauthorized data collection while maintaining efficient collection of permitted data.
Solution Approach 2:
The patent introduces a consent management intermediary system that sits between the tag library and the website deployment. This intermediary verifies user consent status and filters tags accordingly, ensuring that only authorized tags are delivered. The intermediary acts as a mediator that guarantees compliance with user privacy preferences while enabling efficient data collection of permitted information.
3Adaptability or versatility
If Consent Management Platforms and Tag Management Platforms operate independently, then system modularity is maintained, but connectivity and coordination between platforms are lost
Solution Approach 1:
The patent merges the functionality of Consent Management and Tag Management platforms by integrating the consent verification process into the tag delivery mechanism. The system combines consent status determination with tag selection and delivery in a unified process, ensuring that tag delivery accuracy is improved while maintaining the operational independence of the underlying platforms through a coordinated interface.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method of providing one or more selected tracking tags to a domain owner server for deployment on a website is described. The one or more tracking tags are selected from a set of available tracking tags and the method comprises: storing the set of available tracking tags, each available tracking tag including a purpose parameter describing a use to which data collected by the available tracking tag will be put; storing a plurality of user identifiers and a plurality of sets of tag- selection parameters, each user identifier identifying a website user and having an associated set of tag-selection parameters which identity a specific tracking tag and indicate whether a user consent has been obtained for a specific purpose of the specific tag; receiving, from the domain owner server, a request for deployment of one or more tracking tags on the website, the request including a received user identifier identifying a user accessing the website; for a user identifier corresponding to the received user identifier, comparing the tag-selection parameters for each specific tracking tag to the purpose parameter of each corresponding available tracking tag; selecting available tracking tags where the purpose parameter of the available tracking tag corresponds to a specific purpose which has an indication of user consent in the corresponding tag-selection parameters; and transmitting the selected available tracking tags to the domain owner server for deployment on the website.