weeveo
  • Features
  • How it works
  • Revenue
  • Agents
  • Pricing
  • Docs
Sign in
Start free
weeveoanalytics

Understand your traffic.See what leads to sales.

See where visitors come from, what they do and which visits lead to purchases. Basic statistics without a popup. Recordings require permission.

Start freeService status

© 2026 Weeveo. All rights reserved.

Product

  • Features
  • Revenue reporting
  • Realtime
  • Funnels & journeys
  • Pricing

Developers

  • Documentation
  • Agents & MCP
  • Browser SDK
  • REST API
  • Start free
  • Sign in

Company

  • Changelog
  • Support
  • Contact
  • Privacy policy
  • Terms of service
  • Refund policy
  • Status

weeveo

Skip to content
Documentation home
Start here
Meet WeeveoYour first siteFind your way aroundCore concepts & metrics
Install & track
Install the trackerFramework & CMS recipesTracker configurationBrowser SDK referenceConsent & your CMPVisitor identity & payment matchingVerify your installationCustom tracking domains
Understand your traffic
Overview & realtimeDates, filters & comparisonsSources & campaignsPages & engagementEvents & visitor timelinesExplore, paths & saved viewsTraffic quality & anomalies
Conversions & revenue
Goals & conversionsFunnels & bottlenecksRetention cohortsRevenue reportingConnect a payment providerAttribution modelsCustomer journeysAll payment providers
Experience & performance
Session replaysClick & scroll heatmapsWeb Vitals & performance
Developers & agents
Connect ChatGPT, Claude & agentsCreate & manage API keysREST API quickstartAnalytics query referenceErrors, limits & safe retriesJavaScript & Python examplesMCP transport & tool discoveryOAuth discovery & authorizationPermissions & write consentAsk Weeveo & saved chatsApp identity & plugin metadataHTTP surface referenceAll API & MCP tools
Workspace & privacy
Workspaces & multiple sitesTeam, roles & invitationsSite preferences & notificationsPublic reports, embeds & badgesAccount & securityPrivacy & collection controlsVisitor export & erasure
Operate Weeveo
Background jobs & maintenanceTroubleshooting & common questionsQuestions & analysis recipes
Building something?Explore every API tool Download JSON reference ↗
DocsInstall & track
Install & track

Framework & CMS recipes

Install in Next.js, React, HTML, WordPress and hosted site builders.

On this page
Next.js App RouterReact, Vue, Svelte and plain HTMLWordPress and WooCommerceShopify and other hosted buildersTag managers and CSPClient-side event readiness

Next.js App Router#

Add one Script to your root layout. Keep the project's server privacy settings consistent with these attributes. A production website uses the public HTTPS host, not localhost.

tsx
import Script from "next/script";

// Inside your root layout's <body>:
<Script src="https://weeveo.com/weeveo.js"
  strategy="afterInteractive"
  data-project-id="YOUR_PROJECT_UUID"
  data-host="https://weeveo.com"
  data-mode="cookieless"
  data-consent="banner"
  data-privacy-url="https://example.com/privacy" />

React, Vue, Svelte and plain HTML#

Paste the standard snippet in the application's shared HTML shell. For Vite this is typically index.html. The tracker handles pushState, replaceState and popstate changes in pathname. Query-only changes do not create a new automatic pageview. Avoid installing the script in a component that mounts repeatedly.

WordPress and WooCommerce#

Use your theme's shared head/footer integration or a trusted custom-code mechanism. Install once, keep it out of checkout/account private pages if appropriate, and configure your CMP. WooCommerce revenue is a separate payment integration; installing the tracker does not connect payment webhooks.

Shopify and other hosted builders#

Use the builder's supported custom-code area for your storefront. Platform restrictions may prevent script execution in protected checkout pages. Verify the public storefront, and connect Shopify or your actual provider separately for revenue. Never paste a Weeveo API key into theme code.

Tag managers and CSP#

If a tag manager controls loading, load once and coordinate consent rather than firing duplicate tags on every navigation. Permit the chosen tracking host in script-src and connect-src in your Content Security Policy; optional recording also loads recorder.js. Avoid weakening the policy with broad wildcards.

Client-side event readiness#

The tracker loads asynchronously. Call its methods after it has loaded; optional chaining prevents a crash but drops an action that occurs before readiness. The current browser SDK does not provide a pre-load event queue.

Still looking for an answer? Try troubleshooting or get in touch.

PreviousInstall the trackerNextTracker configuration
ON THIS PAGE
Next.js App RouterReact, Vue, Svelte and plain HTMLWordPress and WooCommerceShopify and other hosted buildersTag managers and CSPClient-side event readiness
Your sites. Your permission.

Start with read access. Grant changes when you need them.

Understand access

Search Weeveo documentation

Good places to start

Start hereYour first siteGo from a new workspace to your first verified visit.Install & trackInstall the trackerOne shared script, configured for your site and consent policy.Install & trackBrowser SDK referenceTrack actions, inspect consent and identify a permitted persistent visitor.Developers & agentsConnect ChatGPT, Claude & agentsUse OAuth sign-in for hosted agents, with optional API keys for other clients.Developers & agentsAnalytics query referenceExact shared date, traffic, comparison and filter parameters.Developers & agentsAll API & MCP toolsEvery tool, argument schema and permission in the shared registry.
K to open↑ ↓ to select · Enter to open · Esc to close