Skip to content

SvelteKit

This guide covers SvelteKit. Tested with @sveltejs/kit@2.

Terminal window
npm install @vektis-io/tracker

Generate a key at Settings → API Keys in the VEKTIS dashboard, then create or update .env:

Terminal window
PUBLIC_VEKTIS_KEY=vk_pub_prd_...

Use a publishable key (vk_pub_*) — it’s scoped to event ingest only and safe to ship in your browser bundle.

The tracker is browser-only. Initialize it inside a top-level +layout.svelte so it runs on every page once the bundle hydrates:

src/routes/+layout.svelte
<script lang="ts">
import { onMount } from "svelte";
import { PUBLIC_VEKTIS_KEY } from "$env/static/public";
import * as vektis from "@vektis-io/tracker";
onMount(() => {
vektis.init({ apiKey: PUBLIC_VEKTIS_KEY });
});
</script>
<slot />

user_id is what produces the Seats number on a dev item’s Customer Breakdown — how many people at an account used the feature, out of everyone there VEKTIS has seen. Send a stable id from your own system, never an email address (hashed or otherwise); VEKTIS only ever counts distinct people within a feature, and never displays the identifier or any individual’s activity across features.

import * as vektis from "@vektis-io/tracker";
vektis.identify({
customer_id: "acct_A1",
user_id: "user_123",
name: "Acme Corp",
});

The optional name is the account’s display name. It is what the Customer Breakdown shows instead of the raw customer_id — omit it and every row there is an opaque id.

Call this from whatever store or load function exposes the authenticated user — typically a Svelte store subscription that fires once the session is hydrated.

import * as vektis from "@vektis-io/tracker";
vektis.track("feature.used", { feature_id: "reports-dashboard" });

In the browser dev console:

vektis.getStatus();
// { state: "READY", queueLength: 0, identityCustomerId: "acct_A1", identityUserId: "user_123" }