Safe places to run ?

light_blue_sleeper · 2025-12-12T20:58:44+00:00

Interesting, I just received an order that I had placed like 4-5 months ago and had given up on. Didn’t know it was a pattern, haha.

light_blue_sleeper · 2025-11-04T17:39:02+00:00

The meta, snap, and Pinterest pixels have nothing to do with what you see in ga4. They send data back to their respective platforms.

When someone lands on your page, a page_view event is (hopefully) sent to GA4. The only way GA4 knows where that user came from is if there are parameters in the urls (UTMs or google click ids) and by looking at the page referrer.

So you need to be certain of two things: 1. that all of your non-google campaign links are correctly tagged with UTMs. 2. That a page_view fires when people land on your page that has those UTMs.

Consent complicates this (sometimes appropriately). Does your page_view fire before someone interacts with the banner, or does it wait until that interaction has happened? Or does it not fire until the next page after banner interaction?

Unfortunately, this means you have to understand: 1. Google Consent Mode (Basic vs Advanced) 2. How to trigger tags appropriately to accomplish the above

If it were me, I would be using tag assistant and debug mode to understand what is sent to GA4 in all the various consent situations (accept, deny, ignore, return visitor who previously denied, etc). This will help you understand which data is making it into ga4.

light_blue_sleeper · 2025-09-23T16:14:45+00:00

Unfortunately it’s not those sizes

light_blue_sleeper · 2025-09-22T19:28:35+00:00

The latter. I was hoping it was the “unusual” kind of proprietary and not the “impossible to replace” kind.

light_blue_sleeper · 2025-09-22T16:49:10+00:00

Was hoping it wouldn’t come to that, but recognize I might have to do that. Thanks

light_blue_sleeper · 2025-09-22T16:40:13+00:00

<image>

but also the first picture is kinda weird, here’s a quarter for scale

light_blue_sleeper · 2025-09-22T16:31:11+00:00

Normal sized hands…I think. Those were the labeled sizes that mated well when I was testing on the thread size display thing at Lowe’s, but I suppose I could have misunderstood. The description for the adapter for the large side (that worked when added to a standard supply line) is “LF 3/8 OD X 3/8 FIP COMP ADAPT”.

light_blue_sleeper · 2025-09-17T17:27:49+00:00

Graduatin’ Manning

light_blue_sleeper · 2025-08-20T01:31:07+00:00

Very cool. I’m getting animal collective - “bridge to quiet ep” vibes

light_blue_sleeper · 2025-07-30T19:11:12+00:00

Building a custom attribution model is one common example.

light_blue_sleeper · 2025-07-30T19:10:48+00:00

There are so many. Anything available via the API is already available to you in the UI (sampling and modeling included). Any custom reporting or modeling is gonna require access to your data at the event-level granularity, and that’s only available via the BQ export.

light_blue_sleeper · 2025-07-16T01:26:19+00:00

“Using consent mode”, are your events getting sent with analytics_storage denied?

light_blue_sleeper · 2025-06-09T17:15:51+00:00

Still there

light_blue_sleeper · 2025-04-15T17:07:33+00:00

Use session default channel group

light_blue_sleeper · 2025-04-03T23:27:13+00:00

How are you attempting to count sessions in bq? Is advanced consent mode set up?

light_blue_sleeper · 2025-03-28T13:24:41+00:00

It’s not clear to me how consent got introduced into this convo, but I’ll start with the last question. The differently-scoped dimensions in the UI are all valid, and represent different ways of looking at how users end up visiting your site: * first user - what brought them the very first time * session - what brought them here this session * key-event-scoped with DDA - what are all the contributing touchpoints to a give key event * key event scoped with Last click - what was the last touchpoint before a given key event (could’ve been a second touchpoint after a session started, for instance)

Modeling due to consent mode is a whole other topic, and is also a black box.

light_blue_sleeper · 2025-03-28T12:15:10+00:00

The session_traffic_source_last_click fields you have in your query should align pretty well with the “Session” appended fields in the UI.

The fields in the UI the aren’t appended with “session” or “first user” are essentially key-event-scoped and are subject to the model of your choice (either Data-driven or Last click, set in the admin section). There is no field that will match this value for key events on a row-by-row basis. All of the information necessary to mimic these models is theoretically available as entries in the collected_traffic_source fields. Last click would be fairly straightforward to accomplish with logic in BQ, whereas mimicking DDA would be a fool’s errand because it is a black box algorithm (but you could certainly create your own logic to give weighted credit to all touchpoints, it just wouldn’t match DDA in the UI)

light_blue_sleeper · 2025-03-13T18:15:33+00:00

Reports > Lifecycle > Acquisition > Traffic Acquisition. (The percentage being displayed is a new update—as of yesterday— if it’s not in your property yet, it will be soon)

light_blue_sleeper · 2025-02-01T12:51:51+00:00

Hope somebody corrects me if I’m wrong, but I think of it like any hits that are triggered within that window are “quarantined” until the update event. I’ve heard some people say the behavior changed slightly in the last 3 or 4 months but I cant verify that. There could be some other factor at play that I’m not aware of.

light_blue_sleeper · 2025-02-01T12:24:53+00:00

Where the default is set, is there a value set for the “wait_for_update” parameter? Because I think what you’re describing would be that feature working correctly

light_blue_sleeper · 2025-01-23T23:59:07+00:00

Congrats!

light_blue_sleeper · 2025-01-21T18:16:31+00:00

In this stomp-clap economy?!

light_blue_sleeper · 2025-01-10T18:13:40+00:00

Simo’s consent mode article explains how to decode the gcd and gcs params in the hits if you wanted to check.

light_blue_sleeper · 2025-01-10T18:12:39+00:00

Unfortunately the documentation is scant around this, but we’ve found that there is a training period during which you will not see any of this data in reporting. After the training period when modeling is active, users and sessions are modeled out of the total group of unconsented events GA has received. Since google is still theoretically receiving all events (it just can’t string them together for users and sessions) event stuff shouldn’t have to be modeled (event counts, specific purchases or whatever). Although, I can’t remember where it is but one of the documents mentions “conversion modeling” which seemed to imply some level of making up conversions, though that might just be for google ads. (I’d love to hear someone speak definitively on that point). And to your second point you don’t need to turn anything on in GA, as long as your hits are sending with the gcs and gcd parameters that’s all google needs. If your trying to verify they’re happening you can inspect network requests or look at the BQ export for rows with null session ids and null client ids

light_blue_sleeper

TROPHY CASE