When one data processing service reloads another data processing service, we talk about subconsents or subservices.
Example: Google Tag Manager reloads Facebook Pixel. YouTube reloads the Doubleclick service, which is used to display advertising.
The reloaded data processing service depends on the other service. The YouTube video could theoretically be fired without Doubleclick, but the Doubleclick ad could not be fired without the YouTube video already running.
Implementation
If multiple data processing services depend on each other, please set up the dependent service as a subconsent.
Rule of thumb: subconsent is always the child technology that depends on the parent technology.
Example: Facebook Pixel is dependent on the running of the Google Tag Manager. In this case, please set up Facebook Pixel as a subconsent of Google Tag Manager.
Note: Usually both the parent and child services are called with the name of the parent technology and the code of the two services is adjusted separately.
In the example, this means: The script for the Google Tag Manager, as well as the one for Facebook Pixel, are called via the attribute:
data-usercentrics="Google Tag Manager"
An exception to this case applies to services such as YouTube, which you block via the Smart Data Protector: here, the parent and child services are not called using the name of the parent technology, and the code of the two services is not customized separately. Instead, YouTube is blocked as a parent technology by the Smart Data Protector, and with it (consequently) the subconsent Doubleclick is blocked too.