| 开发者 | shivaat |
|---|---|
| 更新时间 | 2026年11月2日 03:25 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
G- Measurement ID. Consent Mode v2 (Advanced or Basic), regional defaults, WP Consent API support, and your own visits left out by role.G- Measurement ID, for tracking only.Tagsmith uses Google Consent Mode v2 and follows your consent banner's choices (it shows none). Clarity follows the same setting, with three values:
window.tagsmithGrant().In Advanced mode they wait for marketing consent from visitors whose default is "not agreed", in Basic mode from everyone; in Off mode they load for everyone. Without a WP Consent API banner or Google Consent Mode (ad_storage), a visitor who has to agree never triggers a pixel. Where visitors must agree, a banner that decides only in the browser (CookieYes) loses leads from forms that send visitors to another page. Google Ads waits the same way and, in Basic mode with the Google tag set up, also for its grant.
Yes. Every feature is free, with no usage limits or upgrade screens, and nothing will be locked later. It shows no notices outside its own screens and never installs other plugins.
Yes, for the reports: Tagsmith reads them from your own GA4 property, with read-only access. If you have none yet, create a free property at analytics.google.com, then connect.
Yes. Choose "Add the tracking code only" and paste your G- Measurement ID. You get the Google tag with Consent Mode, plus Clarity and the ad pixels if you turn them on, without reports in WordPress.
When visits move by 10% or more, the Overview says what lined up: Google clicks against GA4, your tag, site updates, relabelled or automated visits. Small gaps against Google Analytics come from caching, time zones (Tagsmith uses your WordPress one) or a second tag.
No. The plugin sends its author no usage data. The sign-in relay sees your site address, your IP address and the email of the Google account you sign in with, only while you connect or refresh tokens, and keeps none of it on disk. With your own Google client, the relay is never contacted.
Deleting the plugin removes its settings, saved reports, Clarity snapshots and tokens from the database and asks Google to revoke its access. It also removes its notes on WooCommerce orders. If your site cannot reach Google then, or is a copy whose address changed (Tagsmith does not ask Google to revoke), remove the access at myaccount.google.com/permissions. On a site with an external object cache, cached report copies expire by themselves within a week.
Yes. On the Sign-in & data tab, under "Use my own Google client", add your client ID and secret. Your site then talks only to Google; the sign-in relay is never contacted.
build is compiled from assets/src. To rebuild, use Node 22 and run npm ci && npm run build in the plugin folder.
The demo folder holds the Live Preview's sample data.