Merge pull request #1 from erikaele/main

Update third-party-guideline.md

articles/third-party-guideline.md

@@ -65,7 +65,7 @@ With the move in 2022 to Google Tag Manager, there are some guidelines we'd like
 Particularly with analytics, there are a lot of different packages we use to get data about how someone uses our site. If there is already a product on the site that tells you what you need to know, we favor that approach instead of adding another vendor's analytics package. If it's a question of accessing this information, we are happy to help get you what you need.
 
 #### What pages does the tool need to be active on?
-We favor an approach where we implement third party tools only on the page templates where they are needed. For example, if you want to see session replay for the project guides, the session replay package would only need to be active on project guide pages and *not* on other pages like the home page, category pages, or standard article pages.
+Each brand (as of 6/14/2023) potentially has three domains: the content site (www.), the marketing and purchase pages (subscribe.), and our learning products (courses.).  Based on the purpose of the tool, determine which domain it should be active on.  In addition, we favor an approach where we implement third party tools only on the page templates where they are needed.  For example, if you want to see session replay for the project guides, the session replay package would only need to be active on project guide pages and *not* on other pages like the home page, category pages, or standard article pages.
 
 #### How does the tool support business goals?
 Is there a business cost associated with not using the tool. In other words, is there some critical, actionable insight we will miss without the information collected by the product. If there isn't something really important to be gleaned from the information the tool collects, consider if it's really needed.