Segment with Webflow

Segment earns its place on a marketing site when the number of tools has outgrown the number of scripts you want on the page. Rather than loading analytics, the CRM, the ad pixels and the warehouse connector separately, the site emits one stream and Segment fans it out.

The work is mostly upstream of the code. A destination list is easy; an event taxonomy that still reads clearly in a year is not. I define a small set of events, name them for what a person did rather than which button they clicked, and resist the pull to instrument everything.

Two details decide whether this stays cheap. Website sources default to device mode, which means each destination still loads its own SDK on the page; switching the ones that allow it to cloud mode is where the performance win actually comes from, and it also survives ad blockers. And billing counts monthly tracked users rather than events, so the instinct to trim event volume optimises the wrong number.

Identity is the other half. A visitor who reads three pages, signs up a week later and converts a month after that is one person, and the funnel only shows that if the marketing site and the product agree on how to identify them. That agreement is a decision to make before building, not a setting to find afterwards.