Skip to content

Self-hosted Umami tracking in v1 #717

Description

@dastrokes

🐛 The bug

After upgrading to @nuxt/scripts@1.0.0, Umami stops tracking when using self-hosted endpoint.

Config

exportdefaultdefineNuxtConfig({modules: ['@nuxt/scripts'],scripts: {registry: {umamiAnalytics: {websiteId: '00000000-0000-0000-0000-000000000000',scriptInput: {src: 'https://analytics.example.com/script.js',},domains: ['example.com'],trigger: 'onNuxtReady',},},},})

Working Config pre v1.0

export default defineNuxtConfig({
modules: ['@nuxt/scripts'],
scripts: {
registry: {
umamiAnalytics: {
websiteId: '00000000-0000-0000-0000-000000000000',
hostUrl: 'https://analytics.example.com',
domains: ['example.com'],
},
},
},
})

🛠️ To reproduce

https://stackblitz.com/edit/nuxt-starter-ehk216uq?file=nuxt.config.ts

🌈 Expected behavior

Self-hosted umami should work as expected or better documented in https://scripts.nuxt.com/scripts/umami-analytics

ℹ️ Additional context

Actual behavior

The browser sends:

POST https://example.com/_scripts/p/analytics.example.com/api/send

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions