內容簡介
這個外掛可在正確的隱私設定下，讓您擺脫 Cookie 標籤。與僅對未啟用阻擋的使用者不同，藉由追蹤所有使用者，您可以收集重要的洞察力。根據您當地的法律和外掛設定，您可能不需要 Cookie 標籤。運用資料去決定您要向 Google 傳送哪些資料。讓您的 Google Analytics 追蹤對追蹤和廣告阻擋程式不可見。
注意！
此外掛使用伺服器到伺服器之追蹤。這一方面是很大的優勢，因為使用者的瀏覽器並不會有任何動作，但另一方面，這也意味著每個您想要追蹤的頁面都必須由 PHP 處理。
因此如果您使用快取外掛或 Cloudflare 快取或類似的外掛，它將無法運作，因為您將只追蹤實際達到伺服器的訪問次數。
外掛功能
無 Cookie 追蹤
隱藏所有使用者和 PII 資料而不送往 Google – 如果您的私隱法律允許的話，可擺脫 Cookie 標籤。
比較無 Cookie 追蹤與後端 Cookie 與 GA Library Cookie
與 woocommerce 的 Enhanced Ecommerce 購買追蹤整合
增強的購物結帳步驟，以進行結帳行為分析報告
增強的購物行為分析報告的購買行為
將追蹤點傳送至自訂 URL，而非 GA 或兩者皆有。
通過 shortcode 提供停用選項連結。
遵守「不要追蹤」標頭。
使用現有的停用 Cookie。
匿名化 IP
許多除錯選項
建立自己的客戶端識別代碼。
支援 woocommerce，但如果沒用到 woocommerce 也是行的。
重要提示：建議不要混合前端追蹤資料和此外掛的資料，請為此外掛的追蹤資料建立單獨屬性或檢視。
如果混合使用，您可能會得到重複的點擊。
此外掛使用 Google Analytics 測量協定來發送伺服器到伺服器的追蹤請求。追蹤在前端不可檢測，這意味著它不能被廣告阻擋程式封鎖。
此外掛不受蘋果 Safari 或任何其他追蹤 /廣告阻擋技術的影響。它僅會受到不允許保存 Cookie 的影響。
最大優點：不向 Google 發送任何使用者資料，且追蹤不受廣告阻擋程式影響。
最大缺點：透過後端追蹤，無法獲得所有資料，例如網頁標題和螢幕大小等資訊無法獲取。
使用此外掛作為現有前端追蹤的補充，以查看廣告阻擋程式的影響，或將其作為您唯一的追蹤解決方案。
建議在現有前端追蹤之外額外使用此外掛。
無 Cookie 追蹤
啟用無 Cookie 追蹤：常規 > 客戶端 ID 生成 > 無 Cookie。
它使用非常簡單的指紋辨識，即 Useragent、IP 和瀏覽器不跟蹤標頭的雜湊。
使用這種簡單的指紋辨識的好處是它不會被任何瀏覽器封鎖。
缺點是只有當 IP 地址未變更時它才穩定，而大多數情況下每 24 小時 IP 地址都會更改。
即使如此，它仍比瀏覽器封鎖追蹤 Cookie 而使每次頁面查看都產生新用戶更好。使用此設置可確保每個使用者有一個穩定的會話。
無 Cookie 追蹤與午夜重置
與無 Cookie 追蹤類似，但有一個重要區別：使用者識別代碼每天午夜都會重置。因此，您只能在一天內追蹤使用者。如果他隔天再回來，他將獲得新的識別代碼。
為什麼要這樣做？因為根據您的當地法律，您不再收集「使用者資訊」。這樣您可能就不需要出現 Cookie 標籤了。
外掛標籤
開發者團隊
② 後台搜尋「Cookieless Backend Server Tracking for Google Analytics – WordPress Plugin」→ 直接安裝（推薦）
原文外掛簡介
Get rid of the cookie banner with this plugin and the correct privacy settings. And gather important insights by seeing ALL users in your tracking, and not only users without blockers. Decide with data you want to sent to google. Depending on your local laws and plugin settings you might not need a cookie banner. Make your Analytics tracking invisible for tracking/ad blockers.
BE AWARE
This plugin uses server to server tracking. On the one hand it is a big advantage, because nothing is happening in the browser of the user. On the other Hand this means: every page you want to track need to processed by PHP.
So if you have a caching plugin or cloudflare caching or similiar it won’t work, because you will only track thoses hits which really hit the server.
Plugin Features
Cookieless tracking
Hide all user and PII Data from Google -> get rid of cookie banner if your privacy laws allow it.
Compare cookieless tracking vs. backend cookie vs. GA Library Cookie
Enhanced Ecommerce Purchase Tracking intgration with woocommerce
Enhanced Ecommerce checkout steps for Checkout Behaviour Analysis Report
Enhanced Ecommerce purchase actions for Shopping Behaviour Analysis Report
Sent Tracking hit to a custom URL, not to GA or to both.
Opt out link via shortcode.
Obey Do Not Track header.
Use existing opt out cookie.
Anonymizeip
A lot of debugging options
Creates an own client id.
woocoommerce support, but works without woocommerce as well.
Important: Recommendation is not to mix frontend tracking data with data from this plugin. Please create a separate property or view for the tracking data from this plugin.
If you mix the data you probably will get duplicate hits.
This Plugin uses the google analytics measurement protocol to send server to server tracking requests. The Tracking is not detectable in the frontend, which means it can not be blocked by ad blocker.
This Plugin is not affected by newest ITP of Apples Safari or any other tracking/ad blocking technology. It will be only affected if no cookies are allowed to save.
Biggest advantage: Don’t send any user data to google and tracking not affected by ad blocker.
Biggest downside: with backend tracking not all data is available, so e.g. page titles and screen sizes are not available.
Use this plugin as addition to your existing frontend tracking, to see the impact of ad blockers or use it as your only tracking solution.
Recommendation is, to use it in addition to existing frontend tracking.
Cookieless tracking
To activate cookieless tracking: General > Client ID Generation > cookieless
It uses a very simple fingerprint. It is a hash from Useragent, IP and browser do not track header.
Advantage of using such a simple fingerprint is, that it is not blocked by any browser.
Disadvantage is that it is only stable as long as the IP adress is not changing. Which it does mostly every 24h.
This is still better as having a new user for each page view, which happens if the browsers block tracking cookies. With this setting you make sure to have a stable session for each user.
Cookieless tracking with Reset at midnight
It is similiar to cookieless tracking with an important differences: The User identifier is resetet everday at midnight. So you are only able to track a user during one day. If he comes back the next day he will get a new identifier.
Why should you do that? Because depending of your local laws you do not gather “user information” anymore. With this setting you might not need a consent for tracking anymore, because you do not track the user.
compare cid generator methods
Check “Advanced > Compare different cid generator methods” to compare different cid generation methods.
The following will be compared:
1. cookieless from this plugin
2. tracking cookie from this plugin
3. If available: tracking cookie generated by Google Analytics frontend library: _ga cookie. (Must have implemented Standard GA Frontend tracking)
The test data should go in a separated test property. You need to create a custom dimensions which is populated with the type of cid:
1. created by plugin
2. cookieless
3. created by GA library
If you like to share your results I am happy to hear from you.
Notes for woocommerce integration
1. gross prices are tracked.
2. product tags are tracked as brand in GA.
3. Enhanced Ecommerce is not fully implemented yet. It will evolve release by release. If you have any feature wishes please use the WP Support Forum of this Plugin.
4. For technical reasons the add to cart event is not logged to the frontend. But you see it in the logs.
