start
Functionality
The start function is used to signal AdConsent that the configuration is finished and AdConsent should start managing the user's consent according to the consent law/zone that is applied to the user.
In case AdConsent is being used along with the Snigel advertisement stack AdEngine, this call is done by AdEngine automatically and should not be called manually. Using AdConsent as a standalone product requires calling of the start function in the publisher page at the end of the configuration section.
Syntax
function adconsent()
argument name | type | optional | value | description |
|---|---|---|---|---|
command | string |
|
|
|
Description
AdConsent can work in two modes: integrated within our programmatic ad solution AdEngine or as a standalone product where it can be integrated with other products supporting the IAB TCF 2.0 API. When integrated with AdEngine, one just needs to register an event listener for the AdEngine ready event and put AdConsent configuration there. For more information about this mode, please check how to use AdConsent with AdEngine. If AdConsent is used in standalone mode startmust be called after the end of the configuration section in order to have AdConsent start its logic, thus enabling consent management. For more information about this mode, please check how to use AdConsent in standalone mode.
Scope
The function must be called after AdConsent configuration section if AdConsent is being used in standalone mode only.
Example
Starting AdConsent after all configurations are set (only to be called as a standalone product)
<script>
// AdConsent configuration here ...
adconsent('start');
</script>