Blog

What we learned about landing sGTM events in Snowflake

A grounded take on landing sGTM events in Snowflake, written from real production work.

Snowflake is rarely the cheapest option, but it is often the option teams already have, which makes it the right destination by default.

The short version: event data in Snowflake without a custom ingest pipeline is mostly a matter of doing the obvious thing carefully. Stage events to S3 or GCS from your server container, then use Snowpipe to land them automatically. Skip the temptation to write a custom loader.

You inherit a slightly slower freshness profile compared to streaming inserts. For most analytics that is fine. That trade-off is the one most teams underweight when they plan the work, and it is the one that quietly determines whether the project ships on time.

If you want a longer treatment, we have a deeper post in the series. For now, the takeaway is small enough to fit on a sticky note: When the warehouse is already there, the right answer is usually to use what is already there.