Step 1 · Sign up and get your site key

When you create your Jourvex account, your first site is created automatically and a unique site key is generated for it.

The site key tells Jourvex which workspace incoming journeys belong to.

Example site key: site_live_2h81Kx9QpA

You can find your site key in: Dashboard → Settings → Installation

Step 2 · Install Jourvex

Add the Jourvex runtime to your website using a single script tag. Paste this before the closing </head> tag on every page you want coverage on.

html
<script
  defer
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY">
</script>
Replace YOUR_SITE_KEY with the site key from your Jourvex dashboard.

First-party delivery

First-party proxy coverage is built in. All request from jvx.js route through edge.jourvex.com - a Jourvex-owned edge domain - before reaching the backend. No DNS setup required on your end.

Google Tag Manager

If your site uses Google Tag Manager, install Jourvex as a Custom HTML tag firing on all pages.

GTM — Custom HTML
<script
  defer
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY">
</script>
1 Open Google Tag Manager
2 Create a new Custom HTML tag
3 Paste the Jourvex script
4 Set the trigger to All Pages
5 Publish your container

Next.js

Add the script inside your root layout or custom document file.

app/layout.tsx
import Script from "next/script";

<Script
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY"
  strategy="afterInteractive"
/>

Remix

Add the runtime inside your root document before the closing </body> tag.

root.tsx
<script
  defer
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY">
</script>

SvelteKit

Add the runtime inside your root HTML template.

app.html
<script
  defer
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY">
</script>

Step 3 · Verify installation

Open your website in a new tab and navigate through several pages.

Jourvex should begin capturing visitor activity automatically. Your first journeys should appear in the dashboard within a few minutes.

Debug mode

To enable debug mode locally:

html
<script
  defer
  src="https://edge.jourvex.com/jvx.js?debug=true"
  data-site-key="YOUR_SITE_KEY">
</script>

Optional · Queue stub

If you plan to use the State API before Jourvex finishes loading, add the queue stub before the runtime script.

html
<script>
window.jourvex = window.jourvex || {
  _queue: [],
  on: function(event, cb) {
    this._queue.push({ event, cb });
  }
};
</script>

<script
  defer
  src="https://edge.jourvex.com/jvx.js"
  data-site-key="YOUR_SITE_KEY">
</script>

What Jourvex captures automatically

Jourvex automatically captures evaluator journey signals with no manual event mapping required.

Page views
Full page loads and SPA route changes
Session depth
Navigation activity, dwell patterns, and engagement depth
CTA intent
Demo, signup, trial, and conversion intent signals
Attribution
Referrers, campaigns, and UTM parameters
External redirects
Outbound clicks to docs, GitHub, pricing, and integrations
Journey stitching
Cross-session evaluator continuity across return visits

Common issues

No journeys appearing
Verify your site key is correct and confirm the script is installed before the closing </head> tag.
GTM install not firing
Confirm your GTM container was published and the trigger is set to All Pages.