How to add Google Analytics to the Modern SharePoint

By João Ferreira Dec 21, 2017 Development, Office 365 73 Comments

Having an analytics tool monitoring your intranet is essential to understand the engagement of the users and how they are interacting with the content that is published.

Google Analytics is widely used in the internet, it provides a concise analysis with reports of everything that happens in your site as well as real time reports, mostly targeted for public sites it also works on SharePoint intranets.

Earlier this year I wrote an article that explains step by step how to add Google Analytics to SharePoint without modifying the master page, while that solution is still valid for classic SharePoint it doesn’t work on the modern sites and libraries.

In this article, I explain step by step how to build and deploy an Application Customizer using the SharePoint Framework Extensions, I am also providing the installation files and the instructions to use it if you don’t want to build it yourself.

How to setup Google Analytics

First things first, before we get into the SharePoint bits let’s set up google analytics and get everything you need.

Sign in to your Analytics account
Select the Admin tab
Select an account from the menu in the ACCOUNT column, or CREATE NEW ACCOUNT if you don’t have one already
Select a property from the menu in the PROPERTY column
Under PROPERTY, click Tracking Info Tracking Code
Save the Tracking Id

More information about google analytics setup can be found here.

Create the Application Customizer Extension project

The Application Customizer is one of the available extension types provided by the SharePoint Framework and allows you to add custom JavaScript to every page in a site or web.

To achieve the steps below you need to have installed the SPFx v1.4 or higher, you can get the latest version from here.

Create a folder with the name of the project e.g. analytics
Open the console window in the new directory
Type the command yo @microsoft/sharepoint
When prompted:
- Accept the default app-extension as your solution name, and press Enter.
- Choose SharePoint Online only (latest), and press Enter.
- Choose Use the current folder, and press Enter.
- Choose Y to make the extension available to be added without activating any features.
- Choose Extension as the client-side component type to be created.
- Choose Application Customizer as the extension type to be created.
- Provide a name to the extension. e.g. analytics
- Provide a description to the extension. e.g. Google Analytics for SharePoint modern pages
The download of all the requirements might take a few minutes, once it’s done you will see a message indicating the success of the operation.

Build the extension

Now that you have the extension project created let’s proceed and modify it to include the Google Analytics JavaScript code.

Type code . to open the project (this will open visual studio code but you can use another editor).
On your solution go to src/extensions/analytics and open the AnalyticsApplicationCustomizer.ts
Locate the interface it IAnalyticsApplicationCustomizerProperties and replace it by the code below
```
export interface IAnalyticsApplicationCustomizerProperties {
 trackingID: string;
}
```

Locate the OnInit method and replace it by the code below

public onInit(): Promise {    
	let trackingID: string = this.properties.trackingID;
	if (!trackingID) {
		Log.info(LOG_SOURCE, "Tracking ID not provided";);
	}else{
		var gtagScript = document.createElement("script");
		gtagScript.type = "text/javascript";
		gtagScript.src = `https://www.googletagmanager.com/gtag/js?id=${trackingID}`;    
		gtagScript.async = true;
		document.head.appendChild(gtagScript);  

		eval(`
			window.dataLayer = window.dataLayer || [];
			function gtag(){dataLayer.push(arguments);}
			gtag('js', new Date());    
			gtag('config',  '${trackingID}');
		`);
	}
	return Promise.resolve();
}

This snippet is a modified version of the code provided by Google, it was converted from JavaScript to TypeScript to use the Tracking Id dynamically.

Package the analytics solution

To deploy the analytics solution to all the users it needs to be packaged and installed in the SharePoint Online.

The instructions below are specific for SPFx 1.4 or higher and will make use of the Asset Packaging functionality.

On your project go to the config folder and open the package-solution.json and confirm if the property includeClientSideAssets exists in the solution, if it doesn’t exist it means that you are not using SPFx 1.4 to update your project follow the steps described in this article.
To get the basic structure for the packaging run the command gulp bundle --ship
To get the installation package run the command gulp package-solution --ship
On your project structure navigate to sharepoint/solution, in this folder you will find the *.sppkg file

Install Google Analytics on Modern SharePoint

Extensions won’t be automatically enabled. SharePoint Framework extensions must be specifically associated to sites, lists, and fields programmatically to be visible to site users.

To achieve the steps described in this section you will need to install the SharePoint PnP PowerShell.

If you haven’t built the project download the solution package from here
Open your App Catalog and upload the sppkg file
Check the box Make this solution available to all sites in the organization
On your project go to src/extensions/analytics and open the AnalyticsApplicationCustomizer.manifest.json
Copy the id value
Open the PowerShell command line
To establish a connection, execute the command Connect-PnPOnline -UseWebLogin -Url https://yourtenant.sharepoint.com/
To enable the extension, execute the command Add-PnPCustomAction -ClientSideComponentId "id" -Name "Analytics" -Title "Analytics" -Location ClientSideExtension.ApplicationCustomizer -ClientSideComponentProperties: '{"trackingID":"UA-00000000-1"}' -Scope site
Replace the “id” by the client component id
Replace the “UA-00000000-1” by your own google analytics tracking id

Conclusion

In this article, you learned how to add Google Analytics to the Modern SharePoint sites and how to create an application customizer step by step.

If you were already using Google Analytics to monitor the SharePoint usage now you can combine your existent solution with this approach to get a complete overview of all the pages.

Download Google Analytics SPPKG V2
Explore Solution on GitHub

73 Responses to “How to add Google Analytics to the Modern SharePoint”

Dave
December 22, 2017

How do we do the same for SharePoint Online?
Reply
- João Ferreira
  December 22, 2017
  
  Hi Dave,
  
  The steps described in this article are for SharePoint Online modern team sites, lists and libraries.
  Reply
João Ferreira
December 23, 2017

Thanks Bart, I’ll update the code.
Reply
- João Ferreira
  December 23, 2017
  
  It is added automatically if you have checked Make this solution available to all sites in the organization. You just need to activate it using powershell
  Reply
  - João Ferreira
    December 23, 2017
    
    Not sure if it’s the same. Have you checked the box to make it available? It’s mandatory to get the extention running. Have you tested the code with a site collection workbench?
    Reply
João Miguel
December 29, 2017

Hi,

Nice job. But it needs some more tuning.
The events when switching between modern pages are not being count. Probably because that pages don’t make a full post back.

Does the pnp command activates to all the sites and site collections on the tenant?
I had to connect to another site collection and activate the extension. And the sites inside that site collection are not counting also. Am I missing something?
Reply
- João Ferreira
  December 29, 2017
  
  Hi João,
  
  Thanks for the feedback, the google post is only made on the first load of the page. I’ll work on a new version to register all the pages.
  Once you activate the extension it is added to the entire site collection. There is a know bug with application customizers where the extension is not loaded in some cases. More info here https://github.com/SharePoint/sp-dev-docs/issues/1042
  I’ll try to provide a more robust solution in the next version.
  Reply
  - João Miguel
    December 30, 2017
    
    Thanks,
    
    I’ll try to figure out that also.
    Probably one event will do the trick.
    
    But not this year…
    
    Happy new year
    Reply
    - João Ferreira
      December 30, 2017
      
      Happy new year João
      Reply
  - Tuomas Pakkanen
    September 11, 2018
    
    Hi,
    
    Have you had a chance to update the code so that it would also track when user navigates between different pages on the modern site? Now it tracks only the first load, maybe a bit depending which navigation element is clicked.
    
    Best regards
    Tuomas
    Reply
    - João Ferreira
      October 10, 2018
      
      Hi Tuomas,
      
      I’m getting the solution updated and released this month, I was able to detect the changes when the navigation is made without redirects.
      Reply
      - Tuomas Pakkanen
        October 11, 2018
        
        Hi,
        
        Awesome job, thanks!
        
        Best regards
        Tuomas
      - Tuomas Pakkanen
        November 1, 2018
        
        No pressure, but have you had a chance to update this? Thanks a lot! Also curious about if you’ve done anything similar for Azure Application Insights?
      - João Ferreira
        November 10, 2018
        
        Hi Tuomas,
        
        The solution was updated and a version 2 is available for download.
        To get it up and running on your environment replace the existent sppkg file on the app catalog by the new one and don’t forget to deploy it globally.
        
        My best,
        
        João Ferreira
      - Tuomas Pakkanen
        November 12, 2018
        
        Hi,
        
        Thanks a lot, it works great!
        
        Best regards
        Tuomas
Iro
April 17, 2018

Hello,

Does this work for Office Groups as well? I tried to follow all your steps but it doesn’t seem to appear in the site contents after executing the scripts.
Reply
- João Ferreira
  April 17, 2018
  
  Hi Iro,
  
  This solution is compatible with group sites, it works for all modern SharePoint sites.
  When installing the solution make sure you check the option Make this solution available to all sites in the organization, with this option selected the solution will not appear in the site contents and is deployed globally to the site collection after executing the commands describes on step 8 and 9.
  Let me know if you were able to install the solution in your site.
  Reply
  - Iro
    May 25, 2018
    
    I was not able to install it, but I mistakenly thought it was a site of an Office Group while it was a communication site instead. So maybe the type of site has something to do with it?
    Reply
    - João Ferreira
      May 28, 2018
      
      Hi Iro,
      
      The type of site should not be a problem as long as you choose a modern site.
      
      My best,
      
      João Ferreira
      Reply
Ihsan Rehman
May 25, 2018

one of the best examples of SPFX it actually explains how to start the journey, well done. hats off to you.
Reply
- João Ferreira
  May 25, 2018
  
  Thanks Ihsan for your comment.
  Reply
JP Nelson
May 31, 2018

Great post and I went thru it 3 times on 2 different tenants. I do not see the ext/app when I try to add it to a site. Does it take a while to show up? Or did I miss something?
Reply
- João Ferreira
  May 31, 2018
  Hi JP,
  
  Please make sure you check the box to make the solution available to all sites in the organization, as shown in the image bellow.
  
  If you are using the package from the article make sure you add the extension with this GUID – 9811e000-540c-479c-8436-1cb4c4fd0484
  To intall the solution you should run the code bellow with your own tracking id.
  
  Connect-PnPOnline -UseWebLogin -Url https://yourtenant.sharepoint.com/ Add-PnPCustomAction -ClientSideComponentId "9811e000-540c-479c-8436-1cb4c4fd0484" -Name "Analytics" -Title "Analytics" -Location ClientSideExtension.ApplicationCustomizer -ClientSideComponentProperties: '{"trackingID":"UA-00000000-1"}' -Scope site
  
  To check if the solution is being applied to the site collection use the code bellow. It will list all the extensions deployed at site collection level.
  
  Connect-PnPOnline -UseWebLogin -Url https://yourtenant.sharepoint.com/ Get-PnPCustomAction -Scope site
  
  Hope this helps you to get the solution running.
  Reply
Ellen Kong
July 30, 2018

How would we add Application Insights to SharePoint Online? We use both Google Analytics and Application Insights, but we a transitioning from Classic to Modern sites. Would we be able to use your solution and add in some extra lines for Application Insights? Or does that need to be a separate Application Customizer solution?
Reply
- João Ferreira
  July 31, 2018
  
  HI Ellen,
  
  It needs to be a separated Application Customizer,this is something I have on my back log for quite some time. It will be the next project I’ll release both for modern and classic SharePoint.
  Reply
ihsan
September 20, 2018

solution doesn’t work with google tag manager as i can not see the logged categories inside GA. any ideas why??
Reply
- João Ferreira
  October 10, 2018
  
  Tag manager is not supported by this solution it will be available in this blog this year as a separate solution.
  
  Regards,
  
  Joao Ferreira
  Reply
  - Gena
    January 23, 2019
    
    Hi João,
    do you have any updates on Google Tag Manager (GTM) integration or a SPFx solution option? That would be really great to have this option too on modern as it allows us more detailed tracking as with tracking id. Thanks in advance.
    Regards,
    Gena
    Reply
    - João Ferreira
      April 23, 2019
      
      Hi Gena,
      
      The solution is finally available here.
      https://sharepoint.handsontek.net/2019/04/21/how-to-add-google-tag-manager-globally-to-sharepoint-online/
      Reply
  - Esben Rasmussen
    February 25, 2019
    
    Hi João
    
    I am trying to figure out if it is possible to add Google Tag Manager to Sharepoint.
    
    So far, from what I have been able to find, your article on Google Analytics seems to be the only one coming close to describing how to add this kind of code to a new Sharepoint solution.
    
    Do you also have an article on how to add Google Tag Manager or do you have one planned?
    Reply
    - João Ferreira
      March 7, 2019
      
      Hi Esben,
      
      I’ve planned a solution to add Google Tag Manager to SharePoint.
      It should be out in the next couple weeks, and it will be available for classic and modern SharePoint.
      Reply
      - Esben Rasmussen
        March 7, 2019
        
        That sounds really great. I will look forward to it.
      - Ross
        April 15, 2019
        
        Hi João
        Have you made any progress with GTM on modern SharePoint? I’d really be interested in this solution.
      - João Ferreira
        April 23, 2019
        
        Hi Ross,
        
        The solution is finally ready and you can download it from here.
        http://sharepoint-tricks.com/tenant-app-catalog-vs-site-collection-app-catalog/
- João Ferreira
  April 23, 2019
  
  Hi,
  
  Google tag manager is finally available here.
  https://sharepoint.handsontek.net/2019/04/21/how-to-add-google-tag-manager-globally-to-sharepoint-online/
  Reply
Nick Pettijohn
October 8, 2018

Hi, João.

Thank you! Your instructions ran perfectly, the first time (after I removed the redundant semi-colon).

I ran Get-PnPCustomAction -Scope site and see “Analytics” listed. Now what?

1. How do I know which site collections are using this Application Customizer?
2. What activation steps do I need to take at the site collection and/or site level, if any?
3. How do I use/activate this on a classic site that has some modern pages on it?

Thank you again!

Nick
Reply
- João Ferreira
  October 10, 2018
  
  Hi Nick,
  
  Thanks for your comment I appreciate your feedback.
  
  1 – The application customizer is only used by modern site and pages where you deployed the extension, for each site collection where you want to monitor modern site you will need to execute step 7 and 8 using PowerShell
  
  2 – Once you do it at site collection level it will work on all modern sites and pages in the site collection
  
  3 – To use Google analytics you will need to use another solution that I also built, and it’s available in the link bellow, both can be used on the same site collection if you are using modern and classic site together.
  
  http://sharepoint.handsontek.net/2017/02/26/how-to-add-google-analytics-to-sharepoint-without-modifying-the-master-page/
  Reply
Nick Pettijohn
October 10, 2018

I found my issue: Double-checked package-solution.json in the Config folder. Changed “skipFeatureDeployment” from “true” to “false”. Re-packaged and uploaded to the AppCatalog. I can now add the app to any site collection or site.

Questions:
1. Is activating at the top of a site collection sufficient, or does each sub-site need it added?
2. How does this work on a classic site collection with a mixture of wiki pages and classic pages? Would I need to install the classic solution also? Or one or the other, but not both?

Nick
Reply
- Nick Pettijohn
  October 10, 2018
  
  Edit:
  2. How does this work on a classic site collection with a mixture of wiki pages and MODERN pages? Would I need to install the classic solution also? Or one or the other, but not both?
  Reply
  - João Ferreira
    October 10, 2018
    
    You need to use both solutions, the modern one will be loaded only on modern pages and the same thing happens for the classic solution.
    Reply
    - Jiri F.
      November 23, 2018
      
      Hi,
      I’ve added the GA to our SharePoint tenant and I can see in source code of the modern SP pages the string “customActions” : [{“title”:”Analytics”,”location”:”ClientSideExtension.ApplicationCustomizer”,”clientSideComponentId” … ” with my Google Analytics trackingID in it, but there are no data measured in Google analytics for these pages.
      Is there anything else what needs to be done, to make it work?
      
      And I’d like to ask if the GA is supposed to also apear on Modern SharePoint websites created as part of Office 365 Groups / Microsoft Teams, because I can’t see the GA trackingID in the source code of pages on these sites.
      
      Thanks,
      
      Jiri
      Reply
      - João Ferreira
        November 25, 2018
        
        Hi Jiri,
        
        Sometimes when you with open sessions on SharePoint and Google Analytics in the same browser the tracking doesn’t work.
        If you can’t see the data from other users on other computers, please make sure the Analytics ID is correct.
        This solution will work on all modern sites you just need to enable the extension on all sites that you want to track.
        
        Thanks,
        
        João
- João Ferreira
  October 10, 2018
  
  Thanks for the feedback Nick, this is not the desired behavior but I’m glad you were able no make it work using this trick.
  
  1 – Activation at the top of the site collection is sufficient, however with the latest updates on modern when navigating between pages you might not get the new page into the analytics. I’m working on a solution to solve this issue that I’ll publish this month.
  
  2 – You need to install both solutions for scenarios like this
  Reply
Rami
October 10, 2018

Hi Joao,

I have faced the issue with:

“Add-PnPCustomAction : A parameter cannot be found that matches parameter name ‘ClientSideComponentId’.”

I have tried both created own .sppkg file and your pkg with,
Add-PnPCustomAction -ClientSideComponentId “9811e000-540c-479c-8436-1cb4c4fd0484” -Name “Analytics” -Title “Analytics” -Location ClientSideExtension.ApplicationCustomizer -ClientSideComponentProperties: ‘{“trackingID”:”UA-my-own-id”}’ -Scope site.

Please give me a suggestion.

Thanks and Regards,

Rami
Reply
- João Ferreira
  October 10, 2018
  
  Hi Rami,
  
  In order to execute this command you need to have the PNP powershell installed looking to your command it seems to be correct.
  I did a double check on Microsoft documentation https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpcustomaction?view=sharepoint-ps
  Please make sure you have the PnP cmdlets installed
  
  Regards,
  
  Joao Ferreira
  Reply
  - Rami
    October 11, 2018
    
    HI Joåo,
    
    I have installed SharePointPnPPowerShell2016 and checked the PnP cmdlets. Want me to install SharePointPnPPowerShellOnline and excute this command?!.
    
    Thanks,
    
    Rami
    Reply
    - João Ferreira
      November 25, 2018
      
      Hi Rami,
      
      To use this solution you will need to use the SharePointPnPPowerShellOnline
      
      Thanks,
      
      João
      Reply
João Ferreira
October 10, 2018

Hi Aadil,

Can you please let me know what version of the framework are you using to build the solution?

Regards,

João Ferreira
Reply
Jason Brownhill
November 23, 2018

Hi Joao,
In the newly revised version I think you’re referencing a property in the file ‘AnalyticsApplicationCustomizer.ts’ that is missing if I just take the one page from your github revision? This is the point it isn’t happy with in the code on that page:

${strings.MissingID}`);

I just removed the .MissingID and recompiled, everything built okay. Just testing now.

Hope that helps.
Jason.
Reply
- João Ferreira
  November 25, 2018
  
  Hi Jason,
  
  Thanks for letting me know, I’ll validate the code to check what happened to the strings file.
  
  Thanks,
  
  João
  Reply
  - Jason
    November 26, 2018
    
    No worries. I’m going to download the full package from Github to see if there are other files I need to package up. I was simply following the original blog instructions and editing the single page. I’ll let you know how I get on.
    
    Jason.
    Reply
Dhiran Gajjar
February 5, 2019

Hi Joao,

I followed the instructions and managed to deploy the app to our app catalog and then add it to one of our modern sites. Looked at GA and it was being registered. Now a few weeks later I am trying to follow steps 7 and 8 having noted the original GUID and even though it seems to add the custom action I cannot not see it being actioned as a script to enable the tracking. In the developer tool the only thing with my GA code is the same thing that Jiri posted.

[{“title”:”Analytics”,”location”:”ClientSideExtension.ApplicationCustomizer”,”clientSideComponentId” … ” with my Google Analytics trackingID
Reply
- João Ferreira
  February 10, 2019
  
  Hello Dhiran,
  
  There is a new version of this solution and it does not require the activation of the solution using PowerShell.
  Have a look at this link http://sharepoint.handsontek.net/2019/02/10/deploy-google-analytics-globally-on-modern-sharepoint/
  Reply
Cindy OSbon
February 8, 2019

Hi Joao, if I use the solution you provide how do I complete steps 4 and 5 if I didn’t build the project?

4.On your project go to src/extensions/analytics and open the AnalyticsApplicationCustomizer.manifest.json
5.Copy the id value
6.Open the PowerShell command line
7.To establish a connection, execute the command Connect-PnPOnline -UseWebLogin -Url https://yourtenant.sharepoint.com/
8.To enable the extension, execute the command Add-PnPCustomAction -ClientSideComponentId “id” -Name “Analytics” -Title “Analytics” -Location ClientSideExtension.ApplicationCustomizer -ClientSideComponentProperties: ‘{“trackingID”:”UA-00000000-1″}’ -Scope site
Replace the “id” by the client component id
Replace the “UA-00000000-1” by your own google analytics tracking id
Reply
- João Ferreira
  February 10, 2019
  
  Hi Cindy,
  
  I just published a new version of this solution that easier to implement on SharePoint and does not require the use of PowerShell.
  Please have a look here http://sharepoint.handsontek.net/2019/02/10/deploy-google-analytics-globally-on-modern-sharepoint/
  Reply
  - Cindy OSbon
    February 25, 2019
    
    Thank you! This is wonderful.
    Reply
Jason
February 11, 2019

Hi Joao,
Can you share the query to GA please? Although we got it to work, we’re still seeing inconsistent hits. Just wanted to see if there is a difference between the GA snippet in ours compared to yours – only because we’re not GA specialist.
Thanks,
Jason.
Reply
- João Ferreira
  March 7, 2019
  
  Hello Jason,
  
  There was a bug on SharePoint preventing this solution to collect the data everytime you navigated.
  The bug was fixed by Microsoft and you should be able to see the correct data on your system now.
  Reply
The Ultimate Guide to Setup Google Analytics for SharePoint.
February 12, 2019

[…] http://sharepoint.handsontek.net/2017/12/21/how-to-add-google-analytics-to-the-modern-sharepoint/ […]
Reply
kesava
March 15, 2019

why should we deploy the app to tenant level when it is needed at only site collection level. pls explain.
Reply
- João Ferreira
  March 26, 2019
  
  At tenant level it will monitor all the site collections on your site, but you can always choose to install the solution in the individual site collection using the local app catalog
  Reply
João Ferreira
March 26, 2019

Hi Anita,

You can get around this by using the site collection app catalog, more information about it available here.
Reply
Intranet sur SharePoint Online | KTNN SharePoint
May 25, 2019

[…] How to add Google Analytics to the Modern SharePoint […]
Reply
João Ferreira
June 10, 2019

Hello,

With classic SharePoint you can do this https://sharepoint.handsontek.net/2018/04/18/send-sharepoint-user-profile-details-to-google-analytics/
On modern SharePoint you will need to modify the solution and recompile to add the same parameters.
Reply
Krishant
August 20, 2019

Hi
Thanks for the solution. I tried using the steps you described and added an application customizer to the root of my SharePoint Tenant (https://portal.sharepoint.com).
Does this also track all site collections or would it only track traffic to that one site collection? I assume all site collections, however my GA does not show any data over the last 24 hours. We are not using the root site collection but are using a different site (https://portal.sharepoint.com/sites/intranet).
Anything I am doing wrong?
Reply
- João Ferreira
  August 20, 2019
  
  Hi Krishant,
  
  The app needs to be added to the global app catalog and needs then to be applied to each site collection you want to track using PowerShell.
  For the site collection you are trying to monitor please do the following:
  
  1 – Open the PowerShell console
  2 – Execute the command Connect-PnPOnline -UseWebLogin -Url https://yourtenant.sharepoint.com/sites/intranet
  3 – Execute the command Get-PnPCustomAction -scope site
  
  If the solution is applied you should see an entry with the name Analytics
  
  If you don’t see it now that you are connected to the site collection execute the PowerShell command from step 8, and update your tracking id
  
  Add-PnPCustomAction -ClientSideComponentId “id” -Name “Analytics” -Title “Analytics” -Location ClientSideExtension.ApplicationCustomizer -ClientSideComponentProperties: ‘{“trackingID”:”UA-00000000-1″}’ -Scope site
  
  Let me know how it went and have a nice day 🙂
  Reply
Tom
September 5, 2019

Hello Joao:

Hi, I’m getting error “.ts(44,31): error TS1005: ‘}’ expected” when running ‘gulp bundle –ship’ in command line via visual studio. Getting error that build has failed and can’t figure out why…can you help?
Thanks!
Tom
Reply
- Tom
  September 6, 2019
  
  Joao: I was able to use your example to get the application built and deployed. However, I am not seeing all users data enter into the Google Analytics dashboard, especially specific sites that I or other users visit. The only sites that are registering are sites we rarely visit.
  
  One site in particular is this one: “/_layouts/15/Preload.aspx?disableTelemetry=true&scenario=teamsitehome”
  
  Does this mean that GA is not gathering the data needed? Do I need to set disable telemetry=false in PNP Powershell?
  Any help would be great! Thanks!
  
  Tom
  Reply
  - João Ferreira
    September 6, 2019
    
    Hi Tom,
    
    I’m sorry for the late reply to your comments, I’m happy you were able to get it working on you site.
    The code on this solution is not taking advantage of all the features of the latest versions of the framework but we can manually add the solution to the Tenant Wide Extensions to get it deployed across all modern pages.
    
    Assuming you are using the sppkg file provided in the article do the following:
    
    1 – Open your App Catalog and upload the sppkg file
    2 – Check the box Make this solution available to all sites in the organization
    3 – Go to Site contents and open the list Tenant Wide Extensions
    4 – Click on new
    5 – Fill the form with the following data, the image might help
    
    Title – Analytics
    Component Id – 9811e000-540c-479c-8436-1cb4c4fd0484
    Component Properties – {“trackingID”:”UA-00664002-1″} – Use your own tracking ID
    Location – ClientSideExtension.ApplicationCustomizer
    Sequence – 1
    
    6 – Click Save
    
    This way all modern sites and pages in the tenant will be monitored, I just tested the solution on my dev tenant and it is tracking as shown in the image below.
    
    Please try to connect to SharePoint from a computer or cellphone where google analytics is not open, I’ve seen users with analytics opened being ignored.
    
    Note: If you have built your solution let me know and I’ll give the instructions to get the component ID.
    Let me know how this goes hope you can get it working.
    
    Have a nice day 🙂
    Reply
Thangu
September 19, 2019

Such wonderful content on handsontek. Really awesome.
Reply
Cézar
February 18, 2020

Olá João, tudo bem?

Muito obrigado pelo tutorial!

Será que você poderia me ajudar com uma questão?

Eu tive o seguinte problema ao executar os comandos ‘gulp bundle –ship’ e ‘gulp package-solution –ship’:

PS C:\Users\Dell\Desktop\Google Analytics> gulp bundle –ship
fs.js:27
const { Math, Object } = primordials;
^

ReferenceError: primordials is not defined
at fs.js:27:26
at req_ (C:\Users\Dell\Desktop\Google Analytics\node_modules\natives\index.js:143:24)
at Object.req [as require] (C:\Users\Dell\Desktop\Google Analytics\node_modules\natives\index.js:55:10)
at Object. (C:\Users\Dell\Desktop\Google Analytics\node_modules\gulp\node_modules\graceful-fs\fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Module.require (internal/modules/cjs/loader.js:848:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (C:\Users\Dell\Desktop\Google Analytics\node_modules\gulp\node_modules\graceful-fs\graceful-fs.js:3:27)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Module.require (internal/modules/cjs/loader.js:848:19)
PS C:\Users\Dell\Desktop\Google Analytics> gulp package-solution –ship
fs.js:27
const { Math, Object } = primordials;
^

ReferenceError: primordials is not defined
at fs.js:27:26
at req_ (C:\Users\Dell\Desktop\Google Analytics\node_modules\natives\index.js:143:24)
at Object.req [as require] (C:\Users\Dell\Desktop\Google Analytics\node_modules\natives\index.js:55:10)
at Object. (C:\Users\Dell\Desktop\Google Analytics\node_modules\gulp\node_modules\graceful-fs\fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Module.require (internal/modules/cjs/loader.js:848:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (C:\Users\Dell\Desktop\Google Analytics\node_modules\gulp\node_modules\graceful-fs\graceful-fs.js:3:27)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
at Module.require (internal/modules/cjs/loader.js:848:19)

Desde já obrigado!

Um abraço!
Reply
- Cézar
  February 19, 2020
  
  Olá!
  
  Já consegui resolver o problema! Foi só alterar a versão do node para 10.19.0.
  
  Obrigado!
  Reply
  - João Ferreira
    February 20, 2020
    
    Olá Cézar,
    
    Obrigado pela informação.
    Reply