...
When using AdEngine v3, AdConsent configuration is loaded server-side.
However, there are some cases where a custom callback is required for the configuration calls in AdConsent or other modules that may be seamless seamlessly integrated with AdEngine using the same call structure AdConsent uses. An example is the usage of a specific Analytics module to integrate with AdConsent, other than Google Analytics. In this case, a custom callback must be provided in order to correctly handle the events to be forwarded to the analytics module.
...
The _snigelCallback object has a first layer which that defines the module in which the callbacks are going to be used in.
Inside each module, the specific callback is defined using the command name for which it was written to as the field identifier.
...
The command name value can be any of the available commands in the AdConsent API reference. The callback definition shall need to follow the same AdConsent API reference for that command, regarding the number of input parameters for the callback, which data is to be expected, etc., in order to correctly set the callback for that particular command.
...