What if the Tag Assistant doesn't detect any data from my dynamic remarketing tag?
If, when testing your dynamic remarketing tag, you don't see any data in the "Data Layer" section of the Tag Assistant, several causes are possible. First check the Tag Assistant connection to the correct domain, the saved AW- tag ID and whether dynamic remarketing is enabled in the module. Then check script loading, errors and consent:
- First of all, you should know that this may simply be due to the installation of the AdBlock extension on your browser, or any other cookie-blocking extension. If you have indeed installed such an extension, deactivate it and retest your remarketing tag using our procedure, then check the result again.
- This may also be due to a JavaScript error introduced by a previous technical intervention or by a third-party module present on your store, which is preventing the tag from being triggered. See our FAQ "How to detect a JavaScript error" to find out if such an error exists and how to resolve it.
- It may also be due to the incorrect operation of your cookie consent banner module: if it completely blocks the Google Ads tag even if consent to cookies is granted by the visitor (if you followed our test procedure, you normally clicked on "Accept all" on your cookie banner), check the banner configuration and integration before attributing the cause to a particular module. Calls from this tag may then be prevented. Record the consent states, errors and missing calls for the support team responsible for the affected component once the cause is isolated.
The module includes an Advanced Cookie Banner integration; the result depends on both modules’ versions and configuration. Check consent configuration and the signals actually observed.
If the test still fails, check that you selected the correct AW- tag and event. Inspect console errors and network restrictions, including Content Security Policy (CSP). A loading or connection problem can explain an empty data layer.
If data is present in the layer, also check the hits sent and the feed IDs: this alone does not establish that ads are eligible to run. See the FAQ about a drop in data.
After cookies are refused, sending no data can be consistent with a basic consent mode setup. Compare the behavior with the configured mode before concluding that it is a fault.