Sound Bite: How can personalisation drive lasting value?

Will Hayes•21 February 2024

Ready to talk?

Book a free discovery call to discuss how we can help with your data and analytics challenges.

Book a discovery call

Check your setup for free

Our instant analytics audit scans your GA4 configuration and flags what's missing, broken or misconfigured.

Run a free audit

Suggested content

BigQuery Tips: When your query is technically correct but BigQuery won't run it

There is a particular kind of frustration that comes from staring at a query you know is correct and watching it fail. No syntax error. No logic problem. Just a wall. We hit two of them on the same project. What we were building The job was to migrate ga4_daily_snapshot for a large enterprise client from a BigQuery scheduled query into a proper Dataform pipeline. The scheduled query had been added to over time until it was too large to maintain with any confidence. Moving it to Dataform w

Katie Kaczmarek•17 Aug 2026

Podcast

#146 Assimilated by Anthropic: What We Lost When the Harness Died

Anthropic's clampdown ended the OpenClaw era. Dara and Matthew cover Opus 5, fake GitHub identities in the UK safety tests and EU AI Act Article 50, then ask what was actually lost when the custom harness died, and whether the frustration since is their own fault.

Dara Fitzgerald•14 Aug 2026

BigQuery Tips: The subquery in your WHERE clause that's scanning your entire table

There is a pattern that appears in a lot of BigQuery pipelines and looks completely reasonable. You have a control table that stores the latest processed date. Rather than hardcoding a date into your query, you pull it dynamically: SELECT * FROM `project.dataset.events` WHERE event_date = ( SELECT latest FROM `project.dataset.control_table` ); The query returns the right results. The logic is clean. And if your events table is large and date-partitioned, you might be scanning the entire

Katie Kaczmarek•13 Aug 2026