![]() Note: Closing the CMP UI is your responsibility, so once the user has done something to dispatch Appl圜onsentEvent or AcceptAllEvent, don't show the CMP, or destroy it. That's all, create your CMP, show consents and give the user the ability to choose which things to enable and disable and dispatch the above events. dispatch ( new AcceptAllEvent ( soloCmpDataBundle ) ) dispatch ( new Appl圜onsentEvent ( soloCmpDataBundle ) ) /** AcceptAllEvent In this case, when the user clicks accept everything, it is not necessary to dispatch the event 'MoreChoicesEvent' **/ EventDispatcher. dispatch ( new MoreChoicesEvent ( ) ) /** Appl圜onsentEvent **/ EventDispatcher. */ import cmpstub from cmpstub ( ) import from /** MoreChoicesEvent Before dispatching 'Appl圜onsentEvent', make sure you dispatch the event 'MoreChoicesEvent' This is necessary to indicate to the library that the consent customization panel has been opened so that the various subscribers can perform the appropriate logics. This example demonstrates the basic use case of a CMP UI using our library. ⚡️ Partial integration with AMP (docs later).□ Ability to add plugins in standard flow.□ Optimized consent release performance.Together with the easier implementation of your CMP you have: Implement only the UI part of the CMP, everything else is handled by SoloCmp.This library is completely framework agnostic, so feel free to implement your CMP with any framework such as Vue, React and others.Note that this library was born to satisfy the CMPs for publishers' websites. Library with the intention of simplifying and adding more ways of customization of the whole flow that starts from the view of the CMP banner at the release of the user's consent. This library is a wrapper of the IAB's Transparency and Consent Framework (TCF). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |