Experimentation, plumbed into the warehouse
Five links on A/B testing that ties back to revenue.
1. Feature flags vs experiments — they overlap but aren't the same, here's the line. Source: a PostHog explainer.
2. Statrigor without a stats degree — sequential testing and why peeking ruins results. Source: an experimentation blog.
3. Warehouse-native experimentation — computing lift in SQL instead of a tool's black box. Source: Eppo blog.
4. The metric tree — connecting a button test to ARR. Source: Reforge.
5. Why most A/B tests are underpowered — the sample-size reality check. Source: a CRO thread.
That's the stack for this week. Forward to a teammate.
Five links on A/B testing that ties back to revenue.
1. Feature flags vs experiments — they overlap but aren't the same, here's the line. Source: a PostHog explainer.
2. Statrigor without a stats degree — sequential testing and why peeking ruins results. Source: an experimentation blog.
3. Warehouse-native experimentation — computing lift in SQL instead of a tool's black box. Source: Eppo blog.
4. The metric tree — connecting a button test to ARR. Source: Reforge.
5. Why most A/B tests are underpowered — the sample-size reality check. Source: a CRO thread.
That's the stack for this week. Forward to a teammate.
Consent plumbing, done properly
Most teams bolt on a banner and call it compliance. These go a level deeper on the wiring.
— 1. Google Consent Mode v2 advanced vs basic — Simo Ahava's breakdown of what actually fires before consent in each mode; the modeling caveat alone saves a reporting mess. Source: simoahava.com.
— 2. OneTrust vs Cookiebot vs Osano field notes — a practitioner thread comparing geo-rule granularity, not feature checklists. Source: r/analytics.
— 3. Server-side consent forwarding — passing consent signals through your sGTM container so downstream tags respect it. Source: Stape blog.
— 4. IAB TCF string anatomy — what those base64 consent strings encode, decoded byte by byte. Source: IAB Tech Lab.
Skip if you only serve US traffic. Essential the day you take a single EU click.
That's the stack for this week. Forward to a teammate.
Most teams bolt on a banner and call it compliance. These go a level deeper on the wiring.
— 1. Google Consent Mode v2 advanced vs basic — Simo Ahava's breakdown of what actually fires before consent in each mode; the modeling caveat alone saves a reporting mess. Source: simoahava.com.
— 2. OneTrust vs Cookiebot vs Osano field notes — a practitioner thread comparing geo-rule granularity, not feature checklists. Source: r/analytics.
— 3. Server-side consent forwarding — passing consent signals through your sGTM container so downstream tags respect it. Source: Stape blog.
— 4. IAB TCF string anatomy — what those base64 consent strings encode, decoded byte by byte. Source: IAB Tech Lab.
Skip if you only serve US traffic. Essential the day you take a single EU click.
That's the stack for this week. Forward to a teammate.
Switch attribution models without starting a turf war
The change-management checklist, not the math one.
1 — Run the new model in shadow alongside the old one for a full sales cycle.
Why: showing both numbers side by side disarms the 'you're stealing my credit' fight.
2 — Document which channels gain and lose credit before the meeting.
Why: the channel owners who lose will find out anyway; better they hear it from you.
3 — Freeze the model during the comparison window.
Why: tweaking weights mid-test makes the deltas un-interpretable.
4 — Pick a switch date that aligns to a reporting boundary, never mid-quarter.
Why: a number that changes definition mid-quarter is a forecast nobody can defend.
That's the stack for this week. Forward to a teammate.
—
Рядом обитают: @MarTechNotesHub (crm)
The change-management checklist, not the math one.
1 — Run the new model in shadow alongside the old one for a full sales cycle.
Why: showing both numbers side by side disarms the 'you're stealing my credit' fight.
2 — Document which channels gain and lose credit before the meeting.
Why: the channel owners who lose will find out anyway; better they hear it from you.
3 — Freeze the model during the comparison window.
Why: tweaking weights mid-test makes the deltas un-interpretable.
4 — Pick a switch date that aligns to a reporting boundary, never mid-quarter.
Why: a number that changes definition mid-quarter is a forecast nobody can defend.
That's the stack for this week. Forward to a teammate.
—
Рядом обитают: @MarTechNotesHub (crm)
Reverse ETL reads worth your weekend
The layer that pushes warehouse data back into your tools is finally documented well. Five picks:
— 1. Hightouch's "Composable CDP" whitepaper — the clearest argument for ditching packaged CDPs in favor of your warehouse as the source of truth. Source: Hightouch docs.
— 2. Census on sync diffing — how incremental syncs actually detect row changes without re-sending everything; the section on watermark columns is the keeper. Source: Census engineering blog.
— 3. dbt's "metrics layer" RFC — read the original discussion thread, not the marketing page; the tradeoffs are in the comments. Source: dbt GitHub.
— 4. Snowplow's event modeling guide — schema design before you pipe anything anywhere. Source: Snowplow docs.
— 5. "Modern Data Stack is a fallacy" by Pedram Navid — the necessary counter-read so you don't drink it all. Source: pedramnavid.com.
Skip if you're under 1M monthly events. Essential if your activation is bottlenecked on engineering.
That's the stack for this week. Forward to a teammate.
The layer that pushes warehouse data back into your tools is finally documented well. Five picks:
— 1. Hightouch's "Composable CDP" whitepaper — the clearest argument for ditching packaged CDPs in favor of your warehouse as the source of truth. Source: Hightouch docs.
— 2. Census on sync diffing — how incremental syncs actually detect row changes without re-sending everything; the section on watermark columns is the keeper. Source: Census engineering blog.
— 3. dbt's "metrics layer" RFC — read the original discussion thread, not the marketing page; the tradeoffs are in the comments. Source: dbt GitHub.
— 4. Snowplow's event modeling guide — schema design before you pipe anything anywhere. Source: Snowplow docs.
— 5. "Modern Data Stack is a fallacy" by Pedram Navid — the necessary counter-read so you don't drink it all. Source: pedramnavid.com.
Skip if you're under 1M monthly events. Essential if your activation is bottlenecked on engineering.
That's the stack for this week. Forward to a teammate.
Identity resolution without the vendor pitch
Stitching one human across devices is the hardest part of any stack. Vendor-neutral reads only.
— 1. "Deterministic vs probabilistic matching" — when a hashed email beats a fuzzy fingerprint, and the false-merge cost of getting it wrong. Source: Segment Academy.
— 2. Identity graph data modeling — how to store edges so you can un-merge later (you will need to). Source: RudderStack blog.
— 3. UTM hygiene as identity input — Avinash Kaushik on why dirty campaign tags poison every downstream join. Source: kaushik.net.
— 4. Apple's Private Click Measurement explainer — the model that survives without third-party cookies. Source: WebKit blog.
Skip if you have one channel and one device type. Essential if you run cross-device retargeting.
That's the stack for this week. Forward to a teammate.
Stitching one human across devices is the hardest part of any stack. Vendor-neutral reads only.
— 1. "Deterministic vs probabilistic matching" — when a hashed email beats a fuzzy fingerprint, and the false-merge cost of getting it wrong. Source: Segment Academy.
— 2. Identity graph data modeling — how to store edges so you can un-merge later (you will need to). Source: RudderStack blog.
— 3. UTM hygiene as identity input — Avinash Kaushik on why dirty campaign tags poison every downstream join. Source: kaushik.net.
— 4. Apple's Private Click Measurement explainer — the model that survives without third-party cookies. Source: WebKit blog.
Skip if you have one channel and one device type. Essential if you run cross-device retargeting.
That's the stack for this week. Forward to a teammate.
Attribution reads that admit the limits
Every model lies a little. These tell you how.
— 1. "Incrementality over attribution" — the case for geo-holdout tests instead of last-click theater. Source: Recast blog.
— 2. Markov-chain attribution, explained simply — removal effect math without a PhD; the worked example clicks instantly. Source: Analytics Vidhya.
— 3. Media Mix Modeling for small budgets — Meta's open-source Robyn and when MMM is overkill. Source: facebookexperimental on GitHub.
— 4. "Why your CAC is wrong" — blended vs paid CAC and the trap of counting organic as free. Source: Lenny's Newsletter.
Skip if you spend under five figures a month. Essential before you reallocate a budget.
That's the stack for this week. Forward to a teammate.
Every model lies a little. These tell you how.
— 1. "Incrementality over attribution" — the case for geo-holdout tests instead of last-click theater. Source: Recast blog.
— 2. Markov-chain attribution, explained simply — removal effect math without a PhD; the worked example clicks instantly. Source: Analytics Vidhya.
— 3. Media Mix Modeling for small budgets — Meta's open-source Robyn and when MMM is overkill. Source: facebookexperimental on GitHub.
— 4. "Why your CAC is wrong" — blended vs paid CAC and the trap of counting organic as free. Source: Lenny's Newsletter.
Skip if you spend under five figures a month. Essential before you reallocate a budget.
That's the stack for this week. Forward to a teammate.
From the network
Want more on Digital ops workflows? @TheOpsPlaybook covers it daily and goes deeper than most. Solid follow.
Want more on Digital ops workflows? @TheOpsPlaybook covers it daily and goes deeper than most. Solid follow.
Email deliverability as an engineering problem
Not copywriting. Plumbing. These treat inbox placement like infra.
— 1. DMARC, DKIM, SPF in one diagram — the alignment rules that actually decide gmail placement, drawn clearly. Source: dmarcian.
— 2. Google and Yahoo's 2024 bulk-sender rules — the one-click unsubscribe header spec and spam-rate threshold. Source: Google Postmaster docs.
— 3. IP warming schedules that work — day-by-day volume ramps from a real ESP migration. Source: Postmark blog.
— 4. Seed-list testing vs Google Postmaster Tools — why both, and what each blind-spots. Source: Word to the Wise.
Skip if you send under 5k a day. Essential the week before any domain or ESP migration.
That's the stack for this week. Forward to a teammate.
Not copywriting. Plumbing. These treat inbox placement like infra.
— 1. DMARC, DKIM, SPF in one diagram — the alignment rules that actually decide gmail placement, drawn clearly. Source: dmarcian.
— 2. Google and Yahoo's 2024 bulk-sender rules — the one-click unsubscribe header spec and spam-rate threshold. Source: Google Postmaster docs.
— 3. IP warming schedules that work — day-by-day volume ramps from a real ESP migration. Source: Postmark blog.
— 4. Seed-list testing vs Google Postmaster Tools — why both, and what each blind-spots. Source: Word to the Wise.
Skip if you send under 5k a day. Essential the week before any domain or ESP migration.
That's the stack for this week. Forward to a teammate.
Server-side tagging: the real tradeoffs
Moving tags off the browser fixes some things and breaks others. Curated honestly.
— 1. Server-side GTM cost reality — the Cloud Run bill nobody quotes you, with sizing math. Source: Stape blog.
— 2. First-party cookie restoration via sGTM — extending cookie lifetime past Safari's 7-day ITP cap. Source: Simo Ahava.
— 3. What you lose moving server-side — client-side enrichment you'll have to rebuild. Source: MeasureSchool.
— 4. Conversions API vs pixel — when CAPI genuinely recovers signal and when it's redundant. Source: Meta for Developers.
Skip if your client-side tags fire fine and you're not ITP-blocked. Essential if Safari conversions cratered.
That's the stack for this week. Forward to a teammate.
Moving tags off the browser fixes some things and breaks others. Curated honestly.
— 1. Server-side GTM cost reality — the Cloud Run bill nobody quotes you, with sizing math. Source: Stape blog.
— 2. First-party cookie restoration via sGTM — extending cookie lifetime past Safari's 7-day ITP cap. Source: Simo Ahava.
— 3. What you lose moving server-side — client-side enrichment you'll have to rebuild. Source: MeasureSchool.
— 4. Conversions API vs pixel — when CAPI genuinely recovers signal and when it's redundant. Source: Meta for Developers.
Skip if your client-side tags fire fine and you're not ITP-blocked. Essential if Safari conversions cratered.
That's the stack for this week. Forward to a teammate.