How to test my Google Ads dynamic remarketing tag?

To check dynamic remarketing, inspect the tag calls, parameters and consent choices. This technical check alone does not guarantee that Google Ads will serve ads.

1. Prepare the test

Disable any ad blocker for the test domain. Check the AW- ID in Basic settings, enable dynamic remarketing and review consent configuration.

Run the first test by accepting all cookies. Test the other choices separately afterwards. A drop in data can have several causes; it does not by itself prove a banner fault.

2. Connect Tag Assistant

Open Tag Assistant, click Add domain, enter the full store URL and click Connect. Browse the store in the tab opened for debugging. Confirm the connection if prompted.

Select the tag matching the AW- ID saved in the module.

3. Check a product and its IDs

In the store tab, after accepting cookies on your consent banner, open a product. In Tag Assistant, select that page and the page_view call emitted by the module. The history row label may vary; identify the call by its contents rather than requiring a particular row name.

Inspect the data layer parameters and the hits sent. Also check items: each object must contain the product id and google_business_vertical set to retail. Compare the complete ID with the Merchant Center feed.

Product example in Tag Assistant: the data layer contains page_view, fictitious destination AW-999999999, items[].id equal to 1 and the retail vertical.

In this example, product 1 costs EUR 19.12, its category is Men and isSaleItem is true. Identify the call by its page_view contents.

items[].id must identify the same item as ecomm_prodid. Also check its price, category and combination. user_id is optional according to the module setting; read about its limitations.

If you can see the product information in the data layer, continue checking the hits and ID matches. Its presence alone does not establish receipt or campaign eligibility.

If you don't see any data appear, follow the diagnostic steps before attributing the cause to a blocker, banner or module.

4. Check combinations and other pages

If each combination is exported separately, select another combination and check the new ID. Add the product to the cart and inspect the add_to_cart call and its parameters. Then open the cart and, using a test order, the confirmation page; compare the items and values.

The module also emits page_view with the appropriate page type for categories, search, cart and order confirmation. One product page does not validate all these paths, particularly with a custom theme or checkout.

5. Check consent states

In Consent, check the initial state and updates after banner interaction. Check ad_storage, analytics_storage, ad_user_data and ad_personalization. Repeat for the choices offered by your banner and after navigation.

After refusal, behavior depends on the basic or advanced consent mode implementation. Sending no data is therefore not automatically a fault. Read Google’s consent verification instructions.

If calls appear correct but data or ads are still missing, also check feed IDs, diagnostics, account and campaign configuration in Google Ads. See the possible causes of a drop in data.

Consent states in Tag Assistant: check all four signals for the session’s choices.