Consent Mode v2 with Conseto: what it sets and what to check

analytics_storage

May analytics (GA4) store and read cookies.

ad_storage

May advertising (Google Ads) store and read cookies.

ad_user_data

May user data go to Google for advertising, such as the e-mail hash in enhanced conversions.

ad_personalization

May Google use the visit for personalised ads and remarketing.

• Where consent comes first (GDPR, UK GDPR, Switzerland), all four signals are denied by default before anything from Google loads.
• After the visitor decides, it updates them by the categories accepted.
• It loads GA4 and Google Ads only after consent. This is basic mode: Google receives nothing about visits without consent, not even anonymous pings.

Google models missing conversions from the pings its tags send while consent is denied. Those exist only in advanced mode, when the tags load before the decision. In basic mode, which Conseto uses where consent comes first, there is nothing to model from. You give up those conversions, and nothing about the visitors who declined reaches Google.

• There is no second gtag or GTM container outside Conseto that loads before consent. The site check finds it.
• Your GA4 and Google Ads IDs (with the conversion label) are in the project settings in the app.
• Put a GTM container into the script with the gtm option; the app has no field for it yet.
• In Google Tag Assistant, the gcs parameter on the hits reads G100 for denied and G111 for granted.

You paste the script into the HTML code of the template's head, as on any site (a general procedure; we have not tried it on Shoptet itself yet). A site should have one banner: if you use Conseto's, switch Shoptet's off. The script reads purchases only with the autoTrackEcommerce option and when the shop pushes a GA4-shaped dataLayer.

You download the Conseto plugin in the app ("Installation", "WordPress") and upload it to WordPress; it is not on wordpress.org yet. It adds the script and sends a purchase from the server as a conversion. It is per guide: the code is there and we checked the gateway with a simulated purchase, but we have not run the plugin itself in WordPress; verify it on your shop with the check.