Hello all,

Further to the recommendations that Anna and Manuela from Quietly have developed for integrating  Google Tag Manager, Google Analytics, Google Search Console and Sentry into the new ISLG application: https://docs.google.com/document/d/1fXZKgUpxyuG9y-_UjSIeDWITJaAdboaj5rP-YEGmKTQ/edit, I have created this to-do group so that we can discuss and develop task list for implementing all their recommendations.

Here are the main tasks that need to be accomplished:

Anna and Manuela will take the lead on implementing tasks #1-3 above. Savannah and Stephanie will be responsible for implementing any development tasks related to marketing site (i.e., anything hosted on new.investorstatelawguide.com). Ketan and Harsh will be responsible for implementing any development tasks related to the application (i.e., anything hosted on app.investorstatelawguide.com).

For task #4, Harsh , Jitesh and Ketan please examine the installation instructions and share any questions or concern about the setup process. Assuming there are no technical issues, we will proceed with getting this setup with the new ISLG application.

Please proceed with creating any necessary to-do's above, and we'll track progress and communicate within those individual to-do's.

Let me know if you have any questions or concerns.

Thanks,

Morgan

Hi Morgan , 

Thank you for this. I believe our role will just be inserting the GA code produced once the goals are set up in Google Analytics, but let me know if I am missing anything. 

Hi Savannah ,

Yes, no action need at this point. Anna and Manuela will provide more information when they are ready.

However, Harsh , Jitesh and Ketan , please let us if you understand the installation instruction for task #4. 

Thanks,

Morgan 

Hi Manuela - 

I was speaking with Morgan and Liam last Friday and we would additionally like to use GTM for our LinkedIn tracking. 

We would need for a retargeting tag to be set up along with a goal for lead submission / upgrade your profile. 

Please let me know what information you would need from me to make this happen and how your team would prefer to get the LinkedIn pixel code data. 

Thanks!
Jocelyn 

Hi Jocelyn , hi Morgan , 

Regarding Google Tag Manager, once you set up the ads account on LinkedIn and generate the pixel code, just send it over to us ~2 days before you launch the campaign via email, that way we can ensure everything's set up correctly. 

And I wanted to share a timeline for the ad assets themselves: 

Let me know if you have any questions!

Hi Manuela ,

Everything above looks good to me.

Jocelyn , let us know if you see any issues with the timing.

Thanks,

Morgan 

Hey Morgan -

My only feedback is if we want to launch on the 1st, receiving assets on the 31st makes it a little tight.

Manuela - if we could aim to get the assets by EoD on the 30th that would be amazing. 

Thanks!
Jocelyn

Hi Jocelyn ,

Note that the application will be ready on the 1st, but we'll probably do the official launch on the 5th, so that should give us enough time to get things ready.

Thanks,

Morgan

Morgan  - gotcha! That will leave us plenty of time then :)

Hi Morgan ,

I wanted to share these Google Tag Manager Analytics Deployment Instructions with you and your team. If you could please share these with your dev team and let me know when we can expect them to complete this, that would be great.

Anna is working on a tag-tracking spreadsheet outlining exactly which events we recommend tracking, and what we'll be able to tag within our agreed-upon hours – we'll be sharing that with you tomorrow for your review.

Let me know if you have any questions!
Manuela

cc Anna  

Thanks Manuela .

Ketan and Harsh , could you please examine the instructions above and provide an estimate on how much work this will be to implement, and then we'll determine when to get this complete.

Thanks,

Morgan

Hi Morgan ,

As per Manuela 's note, please find the tagging documentation here. A few notes to keep in mind as you're reviewing:

Lastly, we've also denoted whether implementing tracking for each event will be feasible within the remaining hours we have scoped. We've tried to prioritize based on which events we think will set a solid foundation for ISLG to start, and which ones we can layer in fairly quickly after all the app features are finalized. 

Please let us know if you have any questions once you and your team have reviewed -- always happy to set up a call if needed!

Thanks,
Anna

Great. Thanks Anna . Could we setup a call next week to take me through some of the above.

Also, do I currently have access to the Tag Manager account? I've never used it before.

Thanks,

Morgan

Hi Morgan ,

As per instruction by Manuela . We have set Google tag manager script before launch.

Ok. Great. Harsh . So the scripts are setup? 

Hi Morgan ,

We will set up when will do final deployment on app.islg by next week end.

Ok. Great. Thanks Harsh .

Morgan

Hey Morgan ,

We can definitely set up a call for next week -- are you free next Monday between 10:30-11:30 am or next Tuesday between 9-10 am? If so, we'll send over a calendar invite to confirm.

For access, both the Tag Manager and associated Google Analytics accounts have been set up through the ISLG Gmail email you provided, so if you're logged in, you should see them come through, but let us know if you see otherwise. 

cc Manuela  

Hi Anna ,

A call on Monday at 10:30 works for me. Manuela , could you please send me the details.

Thanks,

Morgan

Invitation sent! Talk to you then, Morgan. 

Hi Morgan ,

You can access the events/tagging documentation sheet here, which has now been recreated in the investorstatelawguide@gmail.com account.

As per our conversation, for the Tag Manager deployment codes, we'll want to push the codes for the marketing site live first (first two sets in the deployment code doc) to implement the LinkedIn tags for the Enhanced Profiles campaign. Everything for the app side can come second.

In the meantime, we'll look out for any comments or edits you have for the events documentation sheet.

cc Manuela  

Great. Thanks Anna . I'll review the event/tagging documentation and provide my edits and comments by the end of this week.

Harsh , Ketan , Stephanie   and Savannah , regarding the integration of the tag manager deployment coded, I've created the following to-do to track this work: Integrate Google Tag Manager deployment codes - TOLOGIX - ISLG App Rebuild. We will need to ensure this implemented before we launch the new application on April 6th.

Further work to integrated some of the more granular tags within the event/tagging documentation will be implemented post-launch.

Thanks,

Morgan 

Hi Anna ,

I've completed my review of the events/tagging documentation sheet here. All my changes are marked in red text and I have inserted comments where appropriate. 

Note I add a whole section detailing the different events in ISLG Reports. I went fairly granular, but I would like to ensure we get quite detailed on what reports users are viewing and exporting within each section.

Let me know your thoughts and perhaps we can have a quick call to discuss implementation.

Thanks,

Morgan

Hi Morgan ,

Congratulations on the new app launch!

I've gone ahead and set up a number of Google Analytics conversion goals last night in preparation for the launch, including getting tracking up for any Enhance Profile, Contact Us, or Trial sign-up form submissions, and any clicks on the "Start Your Trial" CTA button.

I've also set up the two segments we discussed last week with regards to users viewing any People or Organization Profile pages.

I've prepared some documentation here which you can reference to navigate to, and see any important GA reports.

The ISLG Google Ads account should also now be synced with both the Web App and Marketing Site GA views, so any paid campaign data should now be viewable within GA as well (under Acquisition --> Google Ads --> Campaigns). Note, only data going forward from Google Ads will be shown within these new reporting views.

Let me know if you have any other questions or comments -- other marketing site goals such as tracking newsletter sign-ups and webinar registrations will be up by end of week. 

- Anna

cc Manuela  

This is great, Anna . Thank you. I'll get into this in more details later this week, and let you know if I have any questions.

Morgan 

Hi Morgan ,

We've updated the Google Analytics setup so that under the "ISLG Marketing Site (New)" property, you'll see a consolidated view for all pages, as well as separate views for new.islg.com vs. app.islg.com pages. All marketing-level goals have also been set up, with the documentation also being updated. Once the final step is complete (see below), then everything should be good to go. 

We've kept the separate "Web App (New)" GA property as well just in case you did want to keep it for future analysis where you only see yourself checking in on app.islg.com page performance.

Final Step:
There is one last step that's required to ensure that GA treats visits from the same user across the various subdomain pages as a single session (cc Jocelyn )  -- we will need your dev team to update the Google Tag Manager analytics code that was previously implemented on all app.islg.com pages. This is because Google Analytics and all event tracking was originally deployed through Google Tag Manager.

Instructions:
Specifically, please ensure that the following code is implemented within the <head></head> tags (which is already active on all new.islg.com pages) of any app.islg.com pages that are accessible without logging in/marketing site pages that exist on app.islg.com:

<!-- Google Tag Manager -->

<!-- End Google Tag Manager -->

Please then also ensure that this additional line of code is implemented within the <body></body> tags of any app.islg.com pages that are accessible without logging in/market site pages that exist on app.islg.com:

<!-- Google Tag Manager (noscript) -->

Tracking considerations & context
Currently, all app.islg.com pages have a separate Google Tag Manager code snippet implemented -- that's how we're able to get separate tracking for all app pages vs. marketing site pages.

Once the above code is updated, then all marketing-level pages on both new.islg.com and app.islg.com will be passing data back to the same "ISLG Marketing Site (New)" GA property, providing you with a consolidated view into performance.

If you still wanted to keep the in-app reporting separate (i.e. for anyone in a logged in state), then we just recommend updating the Tag Manager codes across the marketing-level app.islg.com pages (as per instructions above).

The alternative is having your dev team implement the codes above across all app.islg.com pages, replacing the app-specific version of the code previously supplied. We still think there's value in at least keeping the app features-side tracking separate, but we'll defer to you to make that final judgement call. In either case, you'll still be able to see the same level of performance detail. The only thing it impacts is whether you see it coming through under the same GA property, or a separate GA property (our previous setup).

Let us know if you have any questions regarding these next steps.

Jocelyn , once that final step is done, any UTM tracking information you're using should be passed from subdomain to subdomain without showing up as two separate sessions.

cc Manuela  

Hi Anna ,

Thanks for the above and apologies for delayed reply. I didn't realize this would need further action from the development side.

Harsh , could you please ensure the code snippets are updated as instructed above within app.islg as soon as possible.

Anna , I agree with keeping the in-app reporting separate; however, can't we integrate this into a views within ISLG Marketing Site (New)? For example, I envision two views with ISLG Marketing Site (New) (renamed ISLG Application (New)):

Currently there is a App.ISLG.com view and New.ISLG.com views in ISLG Marketing Site (New), but this doesn't provide us much utility in the delineating usage between public and subscriber side usage. 

Thanks,

Morgan

Hey Morgan ,

We can create a GA view for logged in state app-level tracking under the same ISLG Marketing Site (New) GA property -- this will just mean implementing the same Google Tag Manager code we shared above across all app.islg.com pages (essentially on every page across the investorstatelawguide.com domain), rather than just the marketing-level ones. 

The previous implementation called for two separate GA properties as we had two separate Google Tag Manager "containers" created to push different types of events (marketing vs. app), and to prevent misreporting, they had to be associated with separate GA properties. This also helps to keep the number of events being tracked within a single Tag Manager "container" manageable and easy to decipher should any new stakeholders in the future look to work within the ISLG Tag Manager account. 

With that being said, since all of the current and future events are logged in the master event spreadsheet for documentation purposes, we can definitely move forward with a single Tag Manager "container". From there, all reporting would exist under a single GA property, with different views for:

Once that Tag Manager code is up across all ISLG.com pages, we can get that final view created and tested.

cc Manuela  

OK. Sounds good, Anna ​. We can do it that way where the subscriber and public pages are tracked in separate properties.

Harsh ​, please proceed with inserting the code according to Anna ​'s instructions where different code is inserted into the public vs. subscriber side pages of app.islg.

Thanks,

Morgan

Hi Anna ,

The following code we need to put in Marketing pages which developed by DEV team right ?

Instructions:
Specifically, please ensure that the following code is implemented within the <head></head> tags (which is already active on all new.islg.com pages) of any app.islg.com pages that are accessible without logging in/marketing site pages that exist on app.islg.com:

<!-- Google Tag Manager -->

'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);

<!-- End Google Tag Manager -->

Please then also ensure that this additional line of code is implemented within the <body></body> tags of any app.islg.com pages that are accessible without logging in/market site pages that exist on app.islg.com:

<!-- Google Tag Manager (noscript) -->

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WFQKRJZ"

For example below is URL :

https://app.investorstatelawguide.com/dispute-document-library
https://app.investorstatelawguide.com/treaty-and-rules-library

Hi Harsh ​,

Yes, there is code snippet to insert into the marketing site pages (e.g., start your trial, browse profile, browse document library, etc.) for app.islg and a separate code snippet for the post-login pages (e.g., subject navigator, full text search, ISLG Reports, etc.).

Thanks,

Morgan

Hey Morgan Harsh ,

Just to confirm, you did want to track everything under the same GA property, but with different views created for post login app.islg.com pages + marketing pages right?

If we're proceeding this way, then you only need to insert that code mentioned up top across all islg.com pages, Harsh.

Morgan, the different code snippet across post-login app.islg.com pages is only if you wanted to keep the post login app.islg.com pages separate from how the rest of the site is tracked. Apologies on any confusion there with the instructions!

Hi Anna ,

Sorry, But I am confused. Please provide updated snipped code here and also provide URL so we can get idea where we need to update code.

Hi Harsh ,

No worries -- apologies for any confusion from the back and forth.

May be worth having Morgan quickly confirm, but my understanding is that we want to just have a single combined Google Analytics property (we currently have two separate ones), with multiple views showing marketing site + post login app page tracking. If this is the desired state, then please follow the instructions below:

Ensure that the following code is implemented within the <head></head> tags of all islg.com domain pages -- this code is already live on all new.islg.com pages, so we just need to have this code replace the previous Google Tag Manager snippet that's currently implemented on app.islg.com pages:

<!-- Google Tag Manager -->

'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);

<!-- End Google Tag Manager -->

Then also ensure that this additional line of code is implemented within the <body></body> tags of the same set of pages as above (so all islg.com pages):

<!-- Google Tag Manager (noscript) -->

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WFQKRJZ"

<!-- End Google Tag Manager (noscript) -->

cc Manuela  

Anna , please give me a call at 604-788-9596 so we can confirm, because we're sending Harsh mixed messages here, and then you can follow-up with specific instructions.

Morgan

Hi Harsh ,

Morgan  and I just regrouped on next steps, and to keep things simple, let's proceed with implementing a single Google Tag Manager snippet across islg.com domain pages. Behind the scenes, we can work to manually exclude any public-facing app.islg.com pages when we create a reporting view in Google Analytics for post-login data. This implementation will ensure that in the future, if any new pages were to be added, we wouldn't need to re-account for them from a tracking perspective. 

Please see implementation instructions below:

Ensure that the following code is implemented within the <head></head> tags of all islg.com domain pages -- this code is already live on all new.islg.com pages, so we just need to have this code replace the previous Google Tag Manager snippet that's currently implemented on app.islg.com pages:

<!-- Google Tag Manager -->

'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);

<!-- End Google Tag Manager -->

Then also ensure that this additional line of code is implemented within the <body></body> tags of the same set of pages as above (so all islg.com pages):

<!-- Google Tag Manager (noscript) -->

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WFQKRJZ"

<!-- End Google Tag Manager (noscript) -->

Hope that clears up any confusion around the instructions, Harsh, but let me know if you have any follow-up questions.

Thanks again for all your help!

Anna

cc Manuela  

Hi Anna and Morgan ,

As per your instruction above, we updated the code snipped in all app.islg pages.

Please check and confirm.

Great. Thanks Harsh .

Anna , could you confirm that everything it setup and tracking data as required?

Also, Manuela , Anna and Martin , would it be possible for us to setup a short 10-15 minute meeting so that we can get oriented on the properties, views and events you've setup through GA and Tag Manager.

Thanks,

Morgan

Thanks Harsh .

Morgan , I can confirm that the setup was successful and that we're seeing data come through accordingly. From here, we'll configure the views created in GA so that post-login app pages are separated out from the public-facing pages -- this update will be made for tomorrow.

I'll defer to Manuela  to set up a time for all of us to connect for that GA and Tag Manager walkthrough. 

Hi Morgan and Martin , we're available to meet in any of the below windows: 

Let me know if either of those works for you both.

Great. Glad to hear it Anna .

Manuela , both those time frames work for me, I'll let Martin confirm on his end.

Morgan

Hello all, how about 4/16 at noon?

Actually, Thursday 4/15 at 1:00pm would work best for me. Sorry for the last minute change.

Thanks both! I'll send an invite shortly for 4/15 at 1pm. Martin could you please share your email address for the invite? 

Manuela my email is mlaporte@tologix.com

Thanks!

Hi Morgan Martin ,

Thanks for taking the time to review the GA implementation today. I've sent out an invite to your emails to access a shared folder where I've moved the GA implementation document into, along with the call recording.

Martin, here is the link to access the events tracking sheet. You should also find this spreadsheet within the Google Drive for the investorstatelawguide@gmail.com account.

I've added some notes to the bottom of the implementation documentation denoting where you can go to access historical information.

Note, for the "All Website Data" view, I just double-checked and the reason why there appeared to be a dip in data for a few days during the second week of launch was actually due to a testing filter that we had applied which was filtering for specific IP addresses -- this filter has now been removed, so from here on out, all page data should be captured across the investorstatelawguide.com domain. However, you can still navigate back to the old "ISLG Web App (New) - Universal Analytics" property to see app usage data from April 5-April 14 (noted at the bottom of the documentation).

Under the same "All Website Data" view, we also applied another filter from April 11th onward that will ensure that pages are showing up with their full URL string (e.g. "app.investorstatelawguide.com/start-your-trial" instead of "/start-your-trial"). That means that you will still see some page URL paths that just start at the subdirectory level (i.e. "/start-your-trial"), which essentially corresponds to older data from April 5-April 11. Moving forward, all page data coming through will indicate the full subdomain information.

Views for marketing campaigns
For marketing campaign purposes moving forward, Jocelyn , the "All Marketing Site Data" view will probably be the easiest to look at since post-login pages have been excluded. I've also sent you an email invite to access the GA documentation accordingly. We had previously synced the older versions of the GA properties with the ISLG Google Ads account, but I'd recommend checking back in on that and making sure the updated/new views are synced, not just the older views.

Let me know if you have any additional questions once you've had a chance to dig into everything.

Cheers,
Anna

cc Manuela  

Great. Thanks Anna .

Jocelyn , during our call tomorrow, we can discuss how (if any) the filtering issues have affected tracking on LinkedIn and Google Ads campaigns, but everything should be tracking properly going forward.

Thanks,

Morgan

Hi Anna and Manuela ,

Jocelyn , Liam and I were reviewing the latest results on Google Ads and LinkedIn and when reviewing GA we discovered that the following goals are not getting registered:

image.png 235 KB • Download

Note we've checked the traffic on GA and there has definitely been traffic on the pages that are supposed to register events for goals 3 (https://app.investorstatelawguide.com/start-your-trial) and 5 (https://investorstatelawguide.us4.list-manage.com/subscribe?u=d1d59f9f148f50a32ad8cca82&id=37d1d3f62d). Also, we've had multiple trial account requests and webinar registrations this week, which should have registered events for goals 4 and 6. 

Could you please investigate and get this resolved as soon as possible, so that we're not continuing to lose data valuable to our campaigns.

Thanks,

Morgan

Hi Morgan ,

We'll investigate this right now and keep you posted on when it's resolved/what the issue is. In the meantime, the "All Website Data" view does appear to be capturing the other form submission actions throughout April, which should help to fill in the gaps for any submissions that were not tracked in the "Marketing Site" view:

ISLG_All_Website_Data_View.png 294 KB • Download

OK. Sounds good. Thanks Anna .

Note I'm still skeptical on goal 6 even with the All Website Data above. Could you confirm that an event should be triggered if the links highlighted in the screenshot below are selected from the Resources & Events page: https://new.investorstatelawguide.com/resources-events/

image.png 416 KB • Download

because this is what we want to track with this goal.

Thanks,

Morgan

Hey Morgan ,

For the resources page, currently, the tracking is set up to log clicks on the "Register" button (i.e. where the button's "click class" within the source code matches "btn btn--quaternary"), but not the "online booking system" link you've shared.

We will need to create a separate event for clicks on "online booking system" since the parameters are a bit different (i.e. no button with a click class in the source code to reference).

Overall, we're investigating the goal tracking for click events. As you can see in this screenshot from the "All Website Data" view, the actual click events have been tracking (for the "Start Your Trial" CTA button as well as the "Register" button) -- however, those event values are not showing up under the goals which effectively reference these events.

ISLG_All_Website_Data_View_Click_Events.png 366 KB • Download

We're just doing another sweep to make sure that the specific form IDs that we've identified for each form, as well as any button source code information we're referencing when we originally set up these events (which were tested and working when we had the two property view setup), are still accurate.

OK. Sounds good, Anna . 

Thanks,

Morgan

Hi Morgan ,

We've gone through the GA environment and located the cause of the tracking issue for the "Marketing View". When we were originally filtering for just marketing/public-facing pages, the "https://app.investorstatelawguide.com/start-your-trial" URL was inputted with a "/" after "start-your-trial", which impacted tracking for the page. We've tested removing the "/", and that appears to have fixed the tracking issue with goals not logging submissions of the form.

We also did another round of testing to ensure that each form is being tracked as it should, as well as resolved the click-tracking issue with the event numbers not showing up under goals. We've tested this across the "Marketing" and "All Website Data" views, and the real-time GA reports seem to be recording these events and goal completions accordingly.

We've also added another section at the bottom of the Analytics Overview document with instructions on how to access the "Events" report, which will show historical data against the events that each goal correspond to. The events have been tracking over time -- especially within the "All Website Data" view, so that would still contain anything that was missed from the "Goals" report over the past few days. 

Apologies for the missing data in the "Goals" view over the past few days -- hopefully the "Events" reports will help to fill in any gaps as they have been actively logging all activity, with the exception of clicks on the "Online Booking System", which we added today. 

Please let me know if you have any additional questions.

Great. Thanks Anna .

I took a quick looks and it appears to be working now:

image.png 187 KB • Download

Thanks for getting that done right away.

Morgan

Our pleasure, Morgan . Apologies for all the back-and-forth, and glad to hear that you're seeing the information come through in the Marketing View. 

Anna