cc ​@Amplitude Admin please help!

Amplitude is creating anonymous users and creating start session and page view events every time I view the page editor in Kajabi. The page editor is a totally different URL than my website, which is how I know this is happening. Example screenshot below.

I tried creating drop and block filters to fix this but it hasn’t helped. Screenshots below. PLEASE FIX this. This is totally unacceptable for an analytics platform.

Thanks!

Hi ​@Katie, thanks for flagging this and I’m sorry you’re frustrated with this experience.

The behavior you’re seeing is consistent with the Amplitude SDK running on your Kajabi editor/preview domain. When that happens, Amplitude will fire Start Session and Page Viewed each time the editor loads, which inflates “unique visitors” and page views even if no one’s visiting your public site.

Here’s how to fix it and clean up what you’re seeing:

• Stop Amplitude from running on non‑public domains

Ensure the SDK only initializes on your live domain (for example, yourdomain.com), and not on any editor/preview/admin subdomains. If you control the snippet, wrap it with a simple domain check so it doesn’t run in Kajabi’s editor:

    <script>
      (function() {
        var allowedHosts =  'yourdomain.com', 'www.yourdomain.com'];
        if (!allowedHosts.includes(window.location.hostname)) return; // don't init on editor/preview
        // init amplitude here
        amplitude.init('YOUR_API_KEY', undefined, {
          autocapture: { pageViews: true, sessions: true } // or your preferred settings
        });
      })();
    </script>

This prevents both Start Session and Page Viewed from firing when you’re in the Kajabi editor. See SDK defaults and how to configure default tracking here (browser-sdk-2.md).

• Alternatively, disable default events where needed

If you must load the SDK on the editor host, disable default page views (and/or sessions) there so only your live site captures them:

    amplitude.init('YOUR_API_KEY', undefined, {
      autocapture: {
        pageViews: false,   // disable default Page Viewed on editor
        sessions: false     // optional: also disable session events on editor
      }
    });

In terms of your block/drop filters, I’m not sure those are set up properly. You have property name starts with “https://katie-….etc” but that’s not the property name. That’s the property value. You need to select “event property” and the property is “Page Location”. Then you input the value you’re looking to exclude. I would also recommend using “contains” rather than equals so if different versions of this trigger that you can properly capture them.

I know this is a bit delayed, but hope you still find this helpful.

​@Beth Saunders Thank you so much for getting back to me! I really appreciate it! I think you can sense how frustrated I was at the time. I really appreciate your help.

1. setting up allowed hosts … I had tried using the attribution plugin to exclude the two kajabi referrers but that didn’t work. I’m going to try your version now. Thanks for sharing clear code with me!
2. disabling default events where needed … I’ll keep this in my back pocket. I’m going to try your first solution first.
3. good catch on my filters. Thank you! I did end up with versions that worked but I think they only apply to charts and not to capturing users in the user profiles tab. Is that correct?

I’ll try this now and will let you know if I have an issue. Thanks again!!