plausible tracking not working with custom domain

[janoschherrmann]

We are self-hosting Plausible and I want to try using next-plausible to help set things up. Here's how my _app.tsx looks:
<PlausibleProvider domain='ourdomain.com' customDomain='https://plausible.ourdomain.com' trackOutboundLinks selfHosted> <Component key={router.asPath} {...pageProps} /> </PlausibleProvider>

I've also wrapped our next-config with the next-plausible proxy. https://plausible.ourdomain.com is where we're self-hosting our Plausible instance, so I added it as a custom domain, but I'm not quite sure whether that's correct.

We're deploying to Vercel running next build, but from what I know, Vercel will run next start as well (we're using SSR). I saw that the next-plausible docs mention the proxy only working with next start.

Currently, the tracking doesn't work. Anything I'm missing here?

[4lejandrito]

Hi @janoschsworkspace,

Can you paste your next configuration? Also, is there a public link to your site you can share so that I can have a look?

[tmelliott]

I'm also getting this issue on Vercel, so wondering if anyone has managed to find a solution/workaround for Vercel? 😄

[janoschherrmann]

Hey @tmelliott,

I've actually gotten it to work on Vercel now.

Here's my next-config.js:

const { withPlausibleProxy } = require('next-plausible')

const moduleExports = withPlausibleProxy({
  customDomain: 'https://plausible.bestcourses.io'
})({
 ...config
})

And here's my _app.tsx:

  <PlausibleProvider
        domain='mydomain.com'
        // full url of the subdomain where our self-hosted instance of plausible is hosted
        customDomain='https://mydomain.io'
        trackOutboundLinks
        selfHosted>
        <Component key={router.asPath} {...pageProps} />{' '}
      </PlausibleProvider>

[tmelliott]

Strange, that looks almost exactly like what I had ... I got around it by changing my subdomain from 'plausible' to something else and removing the proxy; so far AdBlock isn't blocking it!

[janoschherrmann]

Yeah, it's very strange. Don't quite know why it works for me now. I'm guessing it was using the full URL of the subdomain with the plausible instance, but not sure tbh.

[4lejandrito]

Now that I think about it... I think you should not add customDomain to PlausibleProvider, that will make the script load from the custom domain instead of the proxy, and adblockers will catch it. Can you try removing customDomain from PlausibleProvider?