stacklok / toolhive-studio / 24785506739

70%

push

github

feat(analytics): add UTM suite and instance id to on-ramp outbound links (#2075)

* refactor(hooks): extract useInstanceId into a shared hook

The react-query call that fetches the instance id from the main
process was inlined in useHubSpotForm. Lift it into a dedicated
renderer/src/common/hooks/use-instance-id.ts so other renderer
surfaces (on-ramp links, analytics) can share the cached value
without duplicating the queryKey.

* feat(analytics): add buildOnrampDocsUrl helper for on-ramp outbound links

Small builder that emits docs URLs with the full UTM suite
(utm_source, utm_medium, utm_campaign, utm_content) plus an
optional tdi param populated from the instance id. Params are
emitted in a stable, documented order; tdi is omitted when the
instance id query has not yet resolved so the link remains
clickable during the first render.

* feat(nav): attach full UTM suite and instance id to Enterprise upgrade link

The header "Upgrade to Enterprise" button now routes through
buildOnrampDocsUrl with campaign=enterprise-upgrade and
content=app-header, and carries the instance id as tdi, so the
marketing site can attribute clicks back to the app surface and
to the user's install.

* feat(registry): attach full UTM suite and instance id to custom registry promo link

The "Build a custom registry" promo tile now uses the shared
on-ramp URL builder with campaign=custom-registry and
content=registry-view-tile, including the instance id as tdi for
attribution parity with the Enterprise upgrade CTA.

* refactor(hooks): cache useInstanceId for a few days

The instance id is stable across restarts but the IPC itself is
cheap, so pinning the cache forever is overkill. Set staleTime
to three days — enough to avoid the per-mount refetch without
locking the value in the client cache for the lifetime of the
app.

* refactor(nav): scope instance-id fetch to the Enterprise upgrade button

Extract the upgrade CTA into its own small component that owns
the useInstanceId ca... (continued)

3892 of 6380 branches covered (61.0%)

14 of 15 new or added lines in 5 files covered. (93.33%)

6049 of 9075 relevant lines covered (66.66%)

120.62 hits per line