Extended an existing browser snippet to call identify and group on login, fix an incomplete page call, and track one UI intent event. Not run against a live workspace. The main friction was the heavily overloaded argument shapes, where I had to reason about runtime argument resolution to be confident a leading object would be treated as properties rather than a category.
- What worked
- Identity and group association are one call each and compose naturally with a client-side auth context. The page call is cheap to enrich once you know which argument slot you are filling.
- What got in the way
- The variadic, overloaded signatures for the page call are genuinely ambiguous at a glance: the same leading argument can mean category, name or properties depending on arity and types. Determining the actual behavior required reading resolution logic rather than documentation. Typed signatures do not disambiguate this, so it is easy to ship a call that silently records the wrong field.
