Ditched the standard GTM templates. Switched to Custom HTML with direct gtag() injection.
Sometimes you just have to force the code to listen. Conversion tracking saved. 🔧✅
#GoogleAds#GTM#Framer#Analytics
"It should be easy." — Me, before opening GTM debug mode. 😅
The Setup: Framer (SPA) + Native CMP.
The Bug: Google Ads tags stuck on "Still Running" forever on tel: clicks. 🛑
The Fix:
☠️ 💀📢 Google has changed the GA4 cookie format without any prior notice or warning. If your tracking setup relies on directly accessing GA cookies, client IDs, or session IDs, you should immediately audit those implementations. This change may silently break data collection, attribution, or integrations that depend on specific cookie formats.👇
Who is likely affected:
>> Multiple users have reported that their Measurement Protocol (MP) setups have stopped working. Check your MP setup.
>> Many server-side GTM setups extract the session or client ID from GA cookies to enrich data. If they are not using GA4’s get APIs or are parsing cookies directly, they are at risk.
>> APIs or middleware designed to forward client data to GA4, BigQuery, or other analytics platforms may break if they rely on cookie-parsed IDs.
>> Some attribution engines (especially marketing automation or multi-touch attribution tools) rely on _ga cookie formats for user stitching. They may now fail to associate sessions correctly.
>> Tools that use GA’s client ID or session ID to match a web session to a lead may now collect invalid or missing IDs.
>> Some 3rd-party platforms (like segment. com, RudderStack, or custom CDPs) may have integrations that assume a fixed GA cookie format.
As a long-term fix, avoid relying on GA cookie internals as it prevents breakage from undocumented changes.
Jeśli nie chcesz, żeby Twoje dane z Facebooka, Instagrama lub innych usług Meta były wykorzystywane do trenowania sztucznej inteligencji, możesz wyrazić sprzeciw. Wystarczy, że wypełnisz ten formularz: https://t.co/OTMwqfmJ8j.
Do you remove dots before hashing emails with the SHA256 algorithm for enhanced conversions for @gmail.com and @googlemail.com domains? According to the G Ads documentation, this is not required. However, according to the documentation for the G Ads API and GA4, it is required.
Excited to announce we've launched Customer Match for Google Analytics audiences! If your GA4 data includes user-provided data, any audience exported to Google advertising products will now also match your 1P consented, hashed customer data with Google data, in addition to your tag-based user identifiers.
Learn more:
https://t.co/KxsWmagE4X
#googleanalytics #audiences #customermatch #1PD
💥 The real definition of organic search marketing channel (or organic search traffic) in #GA4 is not mentioned even in the official documentation by Google. 🚨
In GA4, the labelling of Organic search marketing channels (or organic search traffic) is based on two main factors:
1) The source matches a predefined list of search engines and/or
2) The medium exactly matches "organic".
.
.
When a traffic source matches a predefined list of search engines, it does not matter what their traffic medium is.
For example, traffic from 'dogpile .com / referral' is labelled as organic search traffic because 'dogpile' is one of the search engines recognized by Google.
Similarly,
Traffic from 'lite .duckduckgo .com / referral' is labelled as organic search traffic because 'duckduckgo' is a search engine that Google recognises.
Once the primary domain is recognized as a search engine, any subdomain it has become irrelevant.
For example, Google considers traffic from 'test .baidu .com' or traffic from 'translate .yandex .com' organic search traffic because 'Baidu
Google consider traffic from 'test .baidu .com' or traffic from 'translate .yandex .com' as organic search traffic because 'baidu' and 'yandex' are the search engines recognized by Google.
.
.
Likewise, when a traffic medium exactly matches 'organic', it does not matter what its traffic source is.
For example, traffic from '(not set) / organic' is labelled as organic search traffic because the medium is 'organic'.
.
.
Any traffic from Google-owned property which is not explicitly tagged as paid is treated as organic search traffic.
So traffic from 'google/(not set)' will be labelled as organic search traffic.
Traffic from 'google / email' will be labelled as organic search traffic.
Similarly,
Traffic from Google lens 'lens .google .com / referral' will be labelled as organic search traffic.
session_traffic_source_last_click record has started appearing in BigQuery table schemas for the GA4 export.
This record includes data about the *session* traffic source, as it aligns with the last click model in GA4.
This is a welcome addition!
#bigquery#googleanalytics4
❗️[GA4] New recommended events: lead generation❗️
Google Analytics 4 has recently expanded its list of recommended events to include new options specifically for lead generation, qualification, and conversion for both online and offline activities 🌐📈
These options are especially useful for businesses with long sales funnels that involve offline activities 🏢📞
For example, this can be very helpful for B2B sales, high-cost products, or any sales that occur offline in physical stores or through phone calls 🛍️💼
Find out the full list of lead generation events and how they work here: https://t.co/crdFcO5mUs
The Firebase Analytics SDK now supports passing "eu_consent_policy" to both ad_user_data and ad_personalization. This aligns with the updated consent mode, where consent is denied only for users in the EEA, per the EU User Consent Policy.
Firebase/SGTM support spotted in the release notes of the Firebase Android SDK (22.0). 🧐
There's no documentation about this (that I could find), so perhaps it's a preliminary infrastructure update with the actual feature coming up later.
#firebase#googletagmanager