[Solution] Same web property ID is tracked twice

Google’s Tag Assistant plugin is an indispensable tool for troubleshooting various Google tags like Google Analytics, Google AdWords, and Google Tag Manager; just install and navigate to your site to enable checks for nearly 300 possible issues. This post will describe how to fix of one of the most common issues reported by this plugin: “Same web property ID is tracked twice.”


Same web property ID is tracked twice simply means that you have the Google Analytics tracking script on your page more than once, with the same tracking ID. This means every page load fires off two or more instances of the GA code, and will cause metrics like page views and bounce rate to be incorrect. The most common reasons for this error are:

  1. GA is firing from within Google Tag Manager AND from GA code in a page template
  2. GA is firing from a plugin (e.g. a Magento or WordPress plugin) AND from GA code in a page template
  3. GTM contains multiple GA pageview tags
  4. Your page template contains old and new versions of the GA script at the same time

In short, Google Analytics provides a tracking code script that can be directly placed on your website. Alternately, you can fire Google Analytics from within Google Tag Manager or various plugins.  To avoid double-counting, you should use only one of these implementation methods, and the tracking code should only be implemented once. For tips on determining where exactly you’ve double-implemented the GA tracking code, read on.


Check out my new API Connector Add-on to import data from thousands of platforms (e.g. Shopify, Harvest, Mailchimp, ActiveCampaign, VWO, YouTube, etc.) directly into Google Sheets.


This is the best all-around method to start with since it usually identifies the source of the issue. To start, install this Chrome add-on: Google Analytics Debugger. Once it’s installed, do the following:

  1. Click the add-on icon in the Chrome toolbar to ensure that it says “GA Debug: ON”
  2. Navigate to your site
  3. Open Developer Tools in Chrome (Press F12 on Windows or Cmd + Opt + I on Mac), and click the Console tab
  4. [optional] Type “pageview” into the filter bar at the top. This isn’t necessary, but it makes the output easier to read
  5. Check for multiple versions of the “send pageview” call to Google Analytics, as shown in the screenshot.
  6. If you see multiple calls with the same UA number, with and without the “gtm” preface, as in the above example, it means you have implemented GA both directly on the page and through GTM. In this case you need to remove your GA code from the page template so that you’re only firing GA from within Google Tag Manager. (While you could alternately remove your GA code from GTM so it’s only firing from the page template, generally it’s better to implement via GTM)
  7. If you see multiple calls with the same UA number, and they all have the “gtm” preface, it means you’ve set up multiple GA pageview tags from within GTM. This is an example of what that would look like:
    Here you can see some calls prefaced with ‘gtm1’, and others prefaced with ‘gtm2’. In this case you need to log into your GTM account, navigate to Tags and remove all but one of your GA pageview tags.
  8. If you see multiple calls with the same UA number, and none of them have the ‘gtm’ preface, it means you have multiple GA pageview tags being fired from within your page template. Here’s an example of what that would look like:
    Here you can see two lines that each say ga(“send”, “pageview”). There’s no ‘gtm’ preface so you know they’re not being set in Google Tag Manager.

Once you’ve completed the above, you should know whether the extra GA code is firing from the page template, from GTM, or some combination. If it’s firing from GTM only, you’re done here as you just need to log into your GTM account to remove the extra code. If the code is firing from the page template, read on for information on how to dig a little more to see exactly where the code is being injected onto the page.


The method from #1 will verify if you have multiple instances of the tracking code, but it won’t necessarily identify where this code is being fired from. To check this you will need to review each place where GA code can be inserted.

To identify where the code has been added, first check the page source. Since GA tracking code can be located in a separate JS file, this method isn’t always effective, but it’s worth checking since it’s fast and easy.

To check the page source, navigate to your site and click Ctrl-U (or right-click > View Page Source). Now hit CTRL-F and search for your account ID  (‘UA-XXXX-X’). This may immediately locate the tracking code script(s) on your page.


If you have a custom site, you or your developers will need to find and remove these extra GA scripts from the page template files within your codebase. If you’re using a platform like WordPress or Magento, you may need to remove these scripts from your plugins or settings. Step #4 has some more info on that.


If you didn’t find anything by reviewing the page source, you can search all the scripts for your site like this:

  1. Open Developer Tools in Chrome (Press F12 on Windows or Cmd + Opt + I on Mac)
  2. click Ctrl+Shift+F
  3. In the search box that appears, type in your UA tracking ID.
  4. In the bottom panel, a list of code snippets containing this tracking ID will appear. You can review each one to see the name of the file containing the snippet, and click each entry to be taken to the location in your code.


If you’re using a platform like WordPress or Magento, there are a few common places where GA code can be inserted. You will need to review each of these:

a) Google Analytics plugins. In WordPress, navigate to Plugins > Installed Plugins and see if there are any Google Analytics plugins in the list.

b) Google Tag Manager plugins. As above, navigate to WordPress > Plugins > Installed Plugins and see if there are any Google Tag Manager plugins in the list. If so, check the settings or log into your Tag Manager account to look for a GA tag.

c) Theme page templates (usually located at WordPress > Appearance > Editor > header.php). Open up your theme’s files and search for GA or GTM code to see if it has been directly inserted here.

d) Custom option within a theme. Some themes have an option to directly enter a GA tracking ID, usually located under WordPress > Appearance > Customize. Review your theme’s settings to see if this is the case.

e) Platform settings. A lot of popular platforms have built-in integrations with Google Analytics. For example, Magento’s integration is located at Stores -> Configuration -> Sales -> Google API (Magento screenshot below). As before, make sure you’re using either the built-in tracking OR on-page code, not both.web-property-img10

Still have any questions? Let me know below.


Get your own tag manager! Click for information on my Google Tag Manager consulting service.


      1. Maybe you fixed it since you posted — I just checked and don’t see any tracking error, or any warning message in Tag Assistant.

    1. Hi Pawel, I checked your site and the issue is that the same GA code is firing twice: one via Google Tag Manager, and once via a service called CallPage. Check the CallPage settings and either disable the GA tracking or send it to a different property ID.

    1. Hi Marija, I checked it and the problem is that you are firing the GA code both directly on the page and again through Google Tag Manager (GTM). This means every page is being counted twice.
      To fix this, you need to remove one copy of the GA code. I suggest keeping the GTM version and removing the GA code from the page. I can’t get more specific because I don’t know how your website is structured, but basically you need to find where GA gets added to the site, and remove it. Good luck 🙂

    1. Hi Sergey, I see the code on your page firing 5 times to a single tracker, meaning your page views are being counted 5x too high.
      From what I can tell, the extra pageviews are coming from this script: brain.com.ua/build/retail.js?20180329. Please remove it from the page and see if that resolves the problem.

    1. Hey there, you have the GA code firing from both within a script (pptaccess.com/cdn-cgi/apps/head/yeBqAOWLrE5L_1tK101nGDWoKGM.js) and from within Google Tag Manager (GTM). I’m not totally sure what that script is but it appears to be related to Cloudflare. So I suggest disabling GA from within Cloudflare, or otherwise removing the GA section from the script, and using GTM only. Please let me know if that works for you!

  1. HI I have same issue and I already read your tutorial but not the problem still Same web property ID is tracked twice, and I would appreciate some assistance. my we site raqidigital.com

    1. I checked your site but Tag Assistant isn’t showing any error for me. If you’re still seeing an error, shoot me a message via the contact form and I’ll take another look.

    1. What happens when you actually click on the ‘2 requests’ text? I’ve seen this issue on another site, where Tag Assistant originally showed 3 Remarketing Tag requests, but when I clicked on the ‘3 Requests’ text, it collapsed them together and showed them as just 1.

  2. Hey,
    Thank you for sharing! However, I tried all your tips and nothing worked.
    My Google Tag Assistant says “Same web property ID is tracked twice.” & “Non-standard implementation.” What does that mean?
    The website is: http://www.interoffices.com

    1. I checked your site and don’t see the “Same web property ID is tracked twice” error message in Tag Assistant, so maybe you’ve updated your site since posting this comment. And you can ignore the “non-standard implementation” message since your code is firing fine. (It’s just a false error message that appears when your GTM account ID is longer than 6 characters).

  3. Try and figure this one out then! I’m stuck!
    Same web property ID is tracked twice apparently. I’m not using GTM. I only have one analytics ID being picked up in my source code. I’m using the default Magento 2 integration. No other tracking code in header/footer or javascript. If I disable Analytics in Magento, I lose both ‘tracked pages’ – perhaps a bug?

    1. Hi Sam, I checked your site and as you said, the script is only set once via Magento. And since both tracking calls disappear when you disable Magento, it confirms that this is a bug with the Magento GA integration. I checked online and found this bug discussed here: https://github.com/magento/magento2/issues/12221. That page says it will be fixed with the with the upcoming 2.3.0 release, but if you’d like to fix it earlier, you can try disabling the default Magento GA integration and implementing GA through a different Magento plugin.

    1. I found the GA script twice on your page: once via the MonsterInsights plugin, and once again via Google Tag Manager. So just delete one of those and you should be good. (I personally prefer to install GA via GTM rather than a plugin, but it’s up to you). Hope that helps!

      1. Thanks Ana! Can you help how to find this error? Use Google Chrome dev tool or other services.

      2. I followed the steps I described in the first method above: opened the GA Debugger and filtered for ‘pageview’.

    1. I checked your site and I see 2 possibilities. First, I see Global Site Tag (gtag.js) on your site, as well as Magento’s built-in tracking. This could be the problem as normally you should only have one or the other, not both. However, in this case it also looks like your gtag.js snippet is missing a line, in which case it’s not firing anyway.

      The other possibility is you’re running into a known Magento bug, in which their GA tracking code fires twice (details: https://github.com/magento/magento2/issues/12221). They should be fixing this by the end of 2018. In the meantime I suggest disabling Magento’s GA tracking and fixing your version of the Global Site Tag. You can find the full script at Admin > Property > Tracking Info > Tracking Code.

  4. Hi Ana,

    I would be grateful for your help on this. https://apprisemed.co.uk

    I installed Google Optimize, using GA, as recommended to reduce latency as would otherwise occur if used GTM which is easier. I’m getting a problem, ‘same web property ID Is being tracked twice’.

    Much appreciated

    1. Hi Sam, I checked your site with the GA Debugger and see ‘gtm1.send’ and ‘gtm2.send’ pageview calls, which means you have 2 pageview tags being set in GTM. I don’t think this is related to your Optimize installation, you just need to log into GTM and remove one of the extra Google Analytics Page View tags.

      1. I also have this issue, does it matter which tag is removed? Can tags be tied to triggers for example?

      2. If the tag doesn’t have a trigger, then it won’t fire at all and won’t cause your property to be tracked twice, so you can safely ignore any tags without triggers. You need to remove any extra, active Pageview tag.

      3. Hi Ana, thanks for your reply. I have two tags set up against the same property, and they both have the same trigger. I’m guessing that in this case it won’t make a difference which one gets deleted?

        The site is https://www.premierleague.com

      4. Right, I checked your site and didn’t see any difference between what the 2 tags are sending to GA, so you should be fine to delete either one.

    1. Hi Marcus, using the GA debugger I see one line that reads ga(“send”, “pageview”) and another that reads ga(“gtm1.send”, “pageview”). This means you have GA code firing from both a script on your page and from within GTM. To fix this, I suggest removing the code from your script and using just GTM (though you could alternately do the reverse). The script looks to be located at /cdn-cgi/apps/head/mEKuAwu_y_u1Qu9t6St41ByEyd4.js.

    1. Hi Drew, I checked your site and don’t see the “Same web property ID tracked twice” error message in Tag Assistant. I think you’re fine.

  5. Hi Ana, first I want to thank you for writing an article on this topic. I’ve been trying to find an adequate response to my issue, but no success. I read the article, however, I’m not sure quite sure how to fix this issue without breaking something? 🙂 Could you please take a look and give me some advice?
    Second, your Mixed Analytics Audit Tool is a real blessing! I’m using it for a while now, and it has helped me tons! Thanks a lot!

    1. Hey Mina, thanks so much for your comment. Made my day 🙂
      I checked your site and you have GA installed via both GTM and GA at the same time, which double counts page views. I suggest leaving your GTM version and removing your other GA script.
      Since you’re using WordPress you’d need to check all the places GA could be installed: the plugin list, header file, or theme options.
      If you send me WordPress login details I can take a look and tell you exactly what needs to be changed.

      1. Hi Ana, thank you for your quick answer as well as for the information you’ve provided.
        The thing is that I accidentally realized that I had this issue on my site. Then I tried to find a solution and found your article. I knew I needed to fix it, but was somehow unsure how to do it.
        Instead of asking, I left it aside thinking I’d fix it later, completely forgot that I haven’t done it yet, which resulted in Google disabling my Adsense account today due to invalid traffic.
        So, I’d greatly appreciate your help! I’m going to send you my login details right now.

  6. Ana, you are a star!!! I wouldn’t have guessed in a million years that it was being fired via All-in-one SEO plugin!!! I completely, COMPLETELY overlooked it! And I was having such a hard time trying to fix it myself, that I couldn’t see the wood for the trees, so I gave it up! Luckily, we have you! Thanks a lot! I really appreciate your help! Couldn’t have made it without you for sure!

    1. Hi Alex, I checked your site with the GA debugger and see 2 pageview calls: one with gtm1 and one with gtm2. That means you have 2 pageview tags being set in GTM, so you just need to log in to GTM, navigate to the Tags list, and delete one of your pageview tags. Typically a pageview tag will have have Type = Google Analytics – Universal Analytics.

  7. Hi, I’m seeing the same error on my site (https://advanced-homehealthcare.com/). When I take a look through GA Debugger and Developer Tools I’m seeing multiple GA pageview tags being fired from within the page template. But I cannot for the life of me figure out where it’s coming from. Any suggestions?

    1. Hi Stacie, I’d start with your plugins, since I see the text “Google Analytics Tracking by Google Analyticator” in your source code. Test disabling the Google Analyticator plugin entirely and reloading the page– if your GA tracking entirely disappears, you’ll know Google Analyticator is setting GA twice and you need to adjust your plugin settings. If GA tracking starts firing just once, then it means you were previously setting GA from 2 different locations, and now the issue is resolved.

      If it has no effect at all, you will need to keep looking among your plugins and theme files. (I can help with that if you send me your WordPress login credentials to take a look.)

      Let me know how it goes!

  8. Anna hi! Thanks a lot for this awesome article. It helps to find and solved an issue with the welcome screen. Thanks for it!

    Anyway, I still have a question.
    Analytics implemented by GTM

    1. The gtm1 and gtm2
    For the “welcome” screen, I add the Tag = “event. welcome”
    Tag: Track type = Event
    Trigger: Some Window Loaded Events when URL contains “welcome”

    if the Trigger is disabled I see on the page only gtm1, if the trigger is working I have gtm1 and gtm2 with next settings.

    Running command: ga(“create”, “UA-GAID-1”, {name: “gtm2”, cookieDomain: “auto”})
    Running command: ga(“gtm2.set”, “&gtm”, “2wg2GTM-ID”)
    Running command: ga(“gtm2.set”, “nonInteraction”, false)
    Running command: ga(“gtm2.set”, “hitCallback”, [function])
    Running command: ga(“gtm2.send”, {hitType: “event”, eventCategory: “welcome”, eventAction: “impression”, eventLabel: undefined, eventValue: undefined})

    Is it correct because i add an event with pageview?

  9. Hello,Ana! My name is Ana too 🙂 I am installed Google Tag Manager and Google Analytics and the Tag Assistant says that i have the same ID tracked twice and that i have Multiples Google Tag Manager and Google Analytics Installations… I have been trying to fix this but i don’t know how…Can you help me?My URL is http://www.anacastilho.com.Thank you!

    1. Hi Ana! The problem is that you have both on-site GA code (gtag.js) and Google Tag Manager running on your site. Since you’re using WordPress, you have likely added GA tracking code via a GA plugin — you’ll need to look through your list of plugins, check their settings, and remove your extra GA tracking. If you can’t find it, feel free to email me login info to your WordPress account and I can check it for you.

  10. Hello! Thank you for your reply. I started to add the code to the Theme editor but then i removed and now i only have it through Insert Headers and Footers Plugin,I removed the GTM and GA Plugins. But there’s still an error. Ok,i will.Thank you

    1. Unfortunately I can’t get more specific because every WordPress theme and plugins are different. Feel free to email me login info to your WordPress account if you’d like me to take a look.

  11. I fixed the error but now it says that I have Non-Standard-Implementation on Google Analytics, and i am not sure that my GTM container is published… Not sure that both GA and GTM are working correctly…

    1. You can safely ignore the non-standard implementation error message. I rechecked your site and all looks good to me now.

    1. In your page source you can see DuracellTomi’s Google Tag Manager for WordPress plugin as well as the GA script directly on the page. Just remove one of those and you should be good!

    1. I just checked your site and confirmed it’s not being tracked twice. I checked Tag Assistant and don’t see any error message there either, are you still seeing it?

      1. Hey Ana. Will check again when I’m back at my PC later.

        Thanks for the speedy response 🙂

  12. Hi Ana, tried to go through all above explained steps but still couldn’t figure out the problem. Tag Assistant also shows “Same web property ID is tracked twice.” Can you maybe take a look at our site? https://www.rinn.net/mein-garten.html And: Best article I found concerning this topic! Thank you!

    1. Hi there, I appreciate your comment! Unfortunately your case can’t be resolved by the above steps because you’re using a custom version of Google Analytics. From what I can tell by viewing your page source, your GA code is wrapped in a function that checks if the user has accepted cookies or not, and there’s a problem with this function causing it to fire twice. So your code isn’t on the page twice, it’s just that the same code is being triggered twice. Since you’re using the third party tool Cookiebot, I suggest reaching out to them or checking their documentation at https://support.cookiebot.com/hc/en-us/articles/360003813893-Controlling-Google-Analytics-Universal-with-Cookiebot to make sure you’ve implemented their version of GA correctly.

    1. Hi Ömer, yep, now I see it. In the GA debugger I see GA firing three times on those pages: twice through GTM and once through the gtag script directly on the page. If you click Ctrl-U, you can see why: you have the GTM script on the page twice (in the header and again in the footer), as well as the gtag script at the top of the page. You need to remove all but one of those scripts, and then your GA tracking will only fire once.

    1. I checked and don’t see any issue. If you haven’t already fixed it, can you please link me directly to the URL where you’re experiencing the issue?

    1. I think I got it (fingers crossed) I deactivated WP plug-in. I was nervous that since GTM tags reference analytics it would disrupt the data flow. Gosh this is confusing!

    1. Hey Ali! I checked your site and see that you have multiple page view tags firing via GTM. From what I can tell, the problem is that you have a regular page view as well as an enhanced ecommerce product detail page view firing on the same page. You can resolve this by logging into your GTM account and blocking the regular page view from firing on product detail pages (you can do that with a blocking trigger). Alternately, you could modify your regular page view tag so that it passes through the enhanced ecommerce data on product detail pages, but the specifics of this will depend on your setup. Please let me know if you have any other questions.

    1. If you open up Dev Tools and filter by ‘pageview’ you can see that GTM is sending 2 pageview hits on each page. So you’ll need to log into GTM and remove one of your extra pageview tags. If you only see 1 pageview tag, make sure it doesn’t have extra triggers applied to it that would cause it to fire more than once.

  13. Hello Ana! I found this information very helpful! I am also getting a “Same web property ID is tracked twice.” error on my site: allinmusicfest.com
    I use wordpress, I have the Google Analytics for WordPress by MonsterInsight on installed and I also use the actual Google Analytics page to analyze my data. Does this mean that I should uninstall or deactivate the plug in version in order to get better quality data and no “double recordings”? Thank you!

      1. Hey Jessica, I checked your site and you have 2 versions of GA running at the same time. One is through MonsterInsight, and one is through a gtag script directly on the page. So you will need to remove one of them to prevent double-counting (it doesn’t matter which one, unless you’re using specific tracking functions from one or the other).
        As for with or without the www, no issues there. Your site has a redirect in place so all traffic will be sent to the same version of the site and tracked together.

  14. Hi Ana Thanks so much for the reply! I feel much more reassured. Now I only get a “Non-standard implementation” comment when I run a check. To my understanding this is not an issue but advice? Have you seen this before?

    1. Yup, I checked and all looks good now! No worries about the “non-standard implementation” error, this is a common error message and can safely be ignored if the tags are firing correctly (and they are).

  15. Hi Ana, thanks for the helpful article. I had MonsterInsights and deactivated it on my site. Still, Tag Assistant says I’m double tracking. Could you help?

    1. Hey Larry, I only see one instance of GA firing on your site. If you’re still seeing an issue, could you please link the exact page?

      1. It’s working fine now! Not sure if viewing the site while logged into WP caused that issue. Thanks again for offering such a resource for us.

    1. The problem is you have a GA script (Global Site Tag) on the site and are also running GA through Google Tag Manager. I recommend removing the GA script from your site and tracking through GTM only. Since you’re using WordPress, you’ll need to check your plugins and theme files to see where the GA script is being added.

  16. Hi Anne, your blog is really nice and informative but I have still a problem with my GA for https://www.herbalcart.com/
    I have found a 0.16% bounce rate for this week and I think that is not true.
    I have also found the warning “Multiple installations of Global site tag (gtag.js) detected” via Google tag manager (Chrome Extention)
    Please let me know what should I do. (i have not installed google tag manager yet)

    1. Hi Jeff, correct, your bounce rate isn’t actually .16%. It’s exactly related to the error message you’re seeing, since you have 2 installations of GA tracking. This means every pageview gets double counted, and since every visit automatically has 2 page views, GA counts it as ~zero bounces (since a bounce is a single page view).
      To fix this issue, you need to remove one instance of your GA tracking code. It looks like you’re using WordPress, so you’ll need to check your Woocommerce options, your theme options, and plugins to determine where you’ve added the code twice.

    1. I checked your setup — it’s a little hard to see what’s going on because you have so many tags and trackers firing, you’re firing multiple events on a single page view, and you’re using custom names for your tracker and data layer (that’s why the troubleshooting steps above don’t work for you). So as a general step I’d suggest stripping your implementation down to the essentials and sticking to a standard implementation, you can add in complexity later.

      With that said, I do see GA firing twice on some pages, e.g. /signup/menu, and both are coming out of your GTM container. So to resolve you’ll need to log into GTM and look for either multiple UA Pageview tags or a single pageview tag with multiple triggers.

  17. Hey Ana, I have same problem again. We create some events tracking for our website with GTM but we are getting same web property ID is tracked twice error. We create GA tags with GTM and some pageview events. How can I fix that?

    Here our website: https://www.724ihale.com

  18. Hey Ana, really sorry to add to this long list of sites to check but Im having problems too. Spent ages trying to work out where the second call is coming from. It should all be done through GTM. https://www.tamiyaclub.com if you could point me in the right direction that would be great

    1. Hey Chris, no need to apologize, I enjoy checking out all the sites 😀
      In this case it looks like your second call is coming from Cloudflare. Can you try logging into your Cloudflare settings and checking if the GA app is enabled? I believe this is the link: https://www.cloudflare.com/apps/google-analytics.
      If it’s enabled (I think it is), just disable it and you should be back to a single tracking call.
      Let me know how it goes!

    1. Hey Bianca, thank you for the message. I checked your site and don’t see any double-tracking on it. So I think you’re fine, but let me know if you’re still seeing any issue.

    1. Hi Steven, I checked your site and it looks like you have both the gtag and Google Tag Manager scripts placed on your site. Just remove your gtag script to prevent tracking twice.

    1. Hey Ania, both your pageviews are being sent from GTM. That means you need to log into your GTM container and check your page view tag(s). The issue will be either because you have 2 pageview tags, or because you have 2 different triggers for a single pageview tag, causing it to fire twice.

  19. Hello Ana,
    First, I want to thank you for your post! I see you kindly devote yourself to help people as much as you can. it’s so valuable from you.
    In fact, I tried all the steps and confused already. Please can you check and let me know what I need to do: https://smarthomenest.com
    Thanks in advance so much.

    1. Hi Edmon, thank you for the kind words! I appreciate that.
      I checked your site and the issue is that you have the gtag script on your site twice, causing the GA tracking script to double fire. It looks like the top script has been added via a WordPress plugin called Alidropship GA Enhanced Ecommerce plugin, while the bottom one has been entered somewhere in your theme. So just remove one of those and you should be good to go.

      1. Thanks again greatly Ana.
        Now you made me clear what was the cause.

        Just would like to ask whether this cause is serious problem if I leave them as they are, since both are essential for me. Will it affect to my overall website performance?

      2. Yep, unfortunately you need to choose one or the other. If you leave both, GA will fire twice for every page view, double-counting pageviews and causing an inaccurate bounce rate calculation.

    1. There are 2 main possibilities for duplicate tags in GTM:
      1) You have 2 separate pageview tags. To check for this, look down your list of tags for tags of type ‘Google Analytics: Universal Analytics’. You’ll need to click into these tags and see if you have more than one tag with Track type = Page View.
      2) The other possibility is that you have 1 pageview tag, but the tag has 2 different triggers. Look for your ‘Google Analytics: Universal Analytics’ page view tag, and make sure it is only attached to a single trigger.

    1. Hi there, I checked your site and you have 2 pageview tags being sent through GTM. Just remove one of them and you’ll be all set.

Leave a Reply

Your email address will not be published.