Info
| Version: | 10.3.0.25603 |
| Author(s): | Richard J. Cabral |
| Last Update: | Friday, June 16, 2023 |
| .NET Fiddle: | Create the first Fiddle |
| Project Url: | https://constellation4sitecore.com/feature/page-analytics-scripts/ |
| NuGet Url: | https://www.nuget.org/packages/Constellation.Feature.PageAnalyticsScripts |
Install
Install-Package Constellation.Feature.PageAnalyticsScripts
dotnet add package Constellation.Feature.PageAnalyticsScripts
paket add Constellation.Feature.PageAnalyticsScripts
Constellation.Feature.PageAnalyticsScripts Download (Unzip the "nupkg" after downloading)
Dependencies
- Constellation.Foundation.Data(>= 10.0.1.23619)
- Constellation.Foundation.ModelMapping(>= 10.0.6.24075)
- Constellation.Foundation.PackageVerification(>= 10.0.1.16481)
- Sitecore.Mvc(>= 10.0.0)
Tags
Requires .NET Framework 4.8
Constellation is a collection of utilities for .NET CMS implementers.
The Feature.PageAnalyticsScripts namespace contains controllers that will render 3rd party analytics and reporting
scripts to the page.
To get the controllers and supporting Data Templates, the included Sitecore package must be installed
This should happen automatically when you build and deploy your project.
After installation, some configuration within Sitecore is required.
1. You need to select a location for Page Analytics Scripts Items.
2. For each of the Controller Renderings provided in the package, you need to set the Datasource Folder field to
the above location.
3. It is recommended that you create placeholders for the Html Header tag as well as the top and bottom of the Body
tags.
You can then assign the provided Controller Renderings to those locations in the Standard Values of your most
basic Page Items.
This module isolates the analytics script kit from actual pages, so you may share scripts on multiple pages (typically
every page on a site references the same datasource). You can also "stack" scripts by adding multiple instances of the
controller renderings with different datasources.
This module does not directly support page/experience editor because:
1. Scripts are invisible
2. Their location in the HTML document may make it difficult to provide access to the rendering.
Because maintaining these scripts requires knowledge of Javascript and Marketing Technology, it is recommended that only
users familiar with the Presentation Details dialog maintain these objects.