Google Analytics (Footer) is the PLUS module in WP Quick Tools that loads Analytics through the WordPress footer. You can use a GA4 Measurement ID or a custom HTML and JavaScript snippet.
Before adding the tag, check that Analytics is not already managed by another plugin, the theme, or Google Tag Manager. The module’s duplicate check is indicative: it does not replace a configuration review or manage visitor consent.
ID mode generates the standard gtag.js loader for the identifier you enter. Use the Measurement ID for the correct GA4 property.
Custom code mode lets you insert an HTML/JS snippet. The code can execute scripts: use only trusted, verified content.
The module looks for gtag, GA, GTM, and dataLayer in the browser and normally avoids loading a second instance. The presence of dataLayer can trigger the check even without an active Analytics tag.
The module does not configure a CMP, automatically wait for consent, or implement Consent Mode on its own. Verify how the tag is actually controlled before enabling it on the public site.
Check whether the theme, plugins, or Tag Manager are already loading Analytics. Choose one consistent path for the tag.
Make sure the site’s privacy system controls this specific loader. The presence of a banner alone is not enough.
Open Google Analytics (Footer), select the mode, and enter the GA4 Measurement ID or verified snippet.
Leave the option that forces loading alongside other code disabled unless you have verified a need for it.
Save the parameters and enable the module only in an appropriate test context or after verifying the necessary controls.
Check tag loading and data in the correct property. Also test denied consent, accepted consent, and the absence of duplication.
The GA4 Measurement ID for the desired property, normally in the format G-XXXXXXXXXX. Check that it belongs to the correct web stream.
No. It configures the loading of an existing identifier or snippet. The property and web stream are managed in Google Analytics.
Loading starts from the standard WordPress wp_footer hook. JavaScript then adds the necessary tags to the document.
Yes. The page must execute wp_footer. A template that does not call this hook may prevent the module from producing output.
The browser looks for gtag or ga functions, a dataLayer array, and certain known Google scripts. The check is best-effort and depends on loading order.
The presence of dataLayer or another loader may be enough to trigger the check. Review the implementation before forcing a second tag.
A dedicated option exists, but using it without checking is not recommended. It can cause duplicate loading or double counting if another system already tracks visits.
No. It does not include a CMP or automatically wait for consent. A verified external configuration is needed to control this loader.
No. Consent settings and signals must be implemented and verified separately.
Yes, in Paste JS/HTML code mode. Scripts can run: use only trusted code that is compatible with the site and its consent system.
Access to WQT management and the unfiltered_html capability are required. Availability may differ in multisite installations.
No. It handles code insertion. Statistics and events are viewed in the configured analytics platform.
Check the identifier, activation, footer, duplicate check, consent, browser blocking, and cache. Also verify the property and web stream selected in Analytics.