Umbraco Engage
CMSCloudHeartcoreDXP
13.latest (LTS)
13.latest (LTS)
  • Umbraco Engage Documentation
  • Release Notes
  • Support
  • Installation
    • System Requirements
    • Installation
    • Licensing
    • Verify your Engage installation
  • Upgrading
    • Upgrade Umbraco Engage
    • Version specific Upgrade Notes
    • Migrate from uMarketingSuite
  • Getting Started
    • Getting Started
    • For Marketers and Editors
      • Cockpit
      • Marketing Resources
    • For Developers
      • Infrastructure sizing
      • Load Balancing and CM/CD Environments
      • Content Delivery Network recommendations
      • Cockpit
      • Content Security Policy nonce configuration
      • Troubleshooting installations
  • Marketers and Editors
    • Introduction
      • The Umbraco Engage Section
      • Content Apps
      • The Umbraco Engage Cookie
    • Analytics
      • What is measured by default
      • Client-side Events
      • Types Of Clients
      • Campaigns
      • Device Type
      • Location
      • Referral Traffic
      • Forms
      • Videos
      • Scroll Heatmap
      • Google Analytics vs Umbraco Engage
      • Search Terms
    • A/B Testing
      • What is A/B testing
      • Types of A/B Tests
        • Single-page A/B Test
        • Multiple Pages Test
        • Document Type Test
        • Split URL Test
      • Setting up the A/B Test
      • Previewing an A/B Test
      • Monitor the A/B Test
      • A/B Test Distribution Algorithm
      • Front end Rendering
      • Finish an A/B Test
    • Personalization
      • Creating a Segment
      • Setting up Personalization
      • Cockpit Insights
      • Implicit and Explicit Personalization
        • Setting up the customer journey
        • Personas
        • Implicit Personalization scoring explained
        • Content Scoring
        • Campaign Scoring
        • Referral Scoring
    • Profiling
      • Profile detail
      • External profile data
    • Reporting
    • Settings
      • Goals
      • IP Filtering
      • Configuration
      • Permissions
  • Developers
    • Introduction
      • Dataflow Pipeline
        • Data Collection
        • Data Storage
        • Data Parsing
        • Reporting
      • The Umbraco Engage Cookie
        • Module Permissions
      • Performance
    • Analytics
      • Request tracking
      • Bot detection
      • Capture location data
      • Extending forms
      • Video tracking
      • Scroll Heatmap
      • Client-side events
        • Additional measurements with analytics scripts
        • Bridging Library for Google Analytics
        • Bridging Library for Google Tag Manager
        • Google Analytics Blocker Detection
        • Create your own events
      • Extending Analytics
        • Getting the Correct IP Address
        • Sending data to the GTM Datalayer
    • A/B testing
      • Retrieving A/B test variants in C#
    • Personalization
      • Implement your own segment parameters
      • Retrieve segment information from code
      • Add custom scoring
    • Profiling
      • External Profile Data
    • Reporting
    • Settings
      • Custom goals scoring
      • Configuration
    • Headless
      • Using the Engage API
      • Headless Example
  • Security and Privacy
    • Security and privacy
    • Retention periods of data
    • Anonymization
    • GDPR & EU regulation
      • How to become GDPR compliant using cookiebot
    • How it works
  • Tutorials
    • Overview
    • How to Get Started with Personalization
    • How to Create a Persona
    • Create a Personalized Popup in 5 minutes
    • How to set up an A/B Test
    • Marketing Resources
      • Generic Topbar Template
      • Generic Popup Template
      • Generic Exit Intent Popup Template
Powered by GitBook
On this page
  • Installation via NuGet
  • Installing using the terminal
  • Next steps
  • Umbraco Forms
  • Clientside tracking
  • Cockpit
  • Optional Extras
  • Cookie consent
  • Load balancing and CM / CD environments
  • The first run

Was this helpful?

Edit on GitHub
Export as PDF
  1. Installation

Installation

Learn about the different ways available for installing Umbraco Engage on your project.

PreviousSystem RequirementsNextLicensing

Last updated 5 months ago

Was this helpful?

This article covers two ways to install Umbraco Engage:

  • Via NuGet, or

  • Via a terminal.

Check the requirements before you start installing Umbraco Engage.

Installation via NuGet

Install Umbraco Engage via Nuget in your IDE such as Visual Studio, JetBrains Rider, or VSCode (With C# DevKit).

The example shown below uses the Nuget Package Manager in Visual Studio.

  1. Open the project in Visual Studio.

  2. Go to Tools -> NuGet Package Manager -> Manage NuGet Packages for Solution.

  1. Navigate to the Browse tab.

  2. Search for the Umbraco.Engage package.

  3. Select the package.

  4. Choose which project to install it into.

  5. Install the package.

Installing using the terminal

You can install Umbraco Engage using a terminal, like the Package Manager Console in Visual Studio. The steps for doing so are outlined below.

  1. Open the project in Visual Studio.

  2. Find and open the Package Manager Console from the Tools menu.

  3. Type the following into the terminal:

PM> install-package Umbraco.Engage

Alternatively, Umbraco Engage can be installed via the console on your operating machine.

  1. Open a terminal window on your operating system.

  2. Navigate to the folder containing your Umbraco website.

  3. Install the Umbraco Engage Nuget package with the following command:

dotnet add package Umbraco.Engage

If you have any trouble, please go to Troubleshooting installs.

Next steps

When you have installed Umbraco Engage, build or restart your website, and the Engage section will appear in the backoffice, as shown above.

The next step is to configure a license.

It is recommended to consider the information detailed in the section below, to get the best out of Umbraco Engage.

Umbraco Forms

If you have installed Umbraco Forms as well and want to automatically track submissions of Umbraco Forms. Install the package Umbraco.Engage.Forms via NuGet or using your preferred approach as above.

PM> install package Umbraco.Engage.Forms
dotnet add package Umbraco.Engage.Forms

Clientside tracking

To capture events that happen on the clientside (frontend) of your website, you need to add the clientside tracking script. This is done by including the following snippet on all of your pages.

<script src="/Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.js"></script>

Cockpit

Cockpit is a tool to help with testing segments and diagnose the data Umbraco Engage collects. It can be viewed on the frontend of your website, only if you are logged into Umbraco as well.

Install cockpit on your website by adding the following Razor Partial View in your templates in Umbraco before the closing </body> tag

@Html.Partial("Umbraco.Engage/Cockpit")</body>

Learn more what Cockpit is and how you can use it.

Optional Extras

Here are some optional extras you can do to improve your experience with Umbraco Engage.

  • Add a Google Analytics bridging script that automatically sends events that you send to Google Analytics, to Umbraco Engage as well.

<script src="~/Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.ga4-bridge.min.js"></script>
  • Add the Google Analytics blocker detection script. This gives you insights in which page traffic Umbraco Engage will track, and Google Analytics will not track.

<script src="/Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.blockerdetection.js"></script>

Cookie consent

If you need to influence the default The Umbraco Engage cookie behaviour please go here. Or go to an example implementation using Cookiebot which can be used as an example for other cookie consent providers.\

If you change the default cookie behaviour make sure to perform a client side reload of the initial page after cookie consent. If this is not done, visitor referrer and/or campaigns will not be tracked.

Load balancing and CM / CD environments

Are you using a load-balanced setup or separate CM and CD environments? Please check our documentation about this topic.

The first run

When you visit your site locally for the first time, Umbraco Engage will begin tracking page views, visitors, etc. If you go to Engage -> Analytics, you won't see any data until the first reporting run. By default, reporting data will be generated at 04:00 AM automatically.

To generate reporting data manually on your local installation, go to Engage -> Configuration. Scroll down to Reporting section and click the red Regenerate button.

Use the Regenerate button only in non-production environments because it can cause temporary performance degradation.

NuGet
Umbraco Engage Package
Engage section in the Umbraco Backoffice.
Regenerate button