In this scenario, marketers define campaigns and measure their results in the interface of the Kentico application. However, the content targeted by the campaign is served on the MVC website, so developers need to take additional steps to ensure that the MVC site logs page visit conversions for campaigns.
Registering campaign tracking on MVC sites
Perform the following steps to register campaign tracking functionality for your MVC application:
Open your MVC project in Visual Studio.
- Install the following integration packages into your MVC project:
Edit the application's App_Start/ApplicationConfig.cs file.
Add a using statement for the Kentico.CampaignLogging.Web.Mvc namespace.
using Kentico.Web.Mvc; using Kentico.CampaignLogging.Web.Mvc;
Call the predefined UseCampaignLogger method (from the ApplicationBuilder instance in the RegisterFeatures method). This ensures that the application sends all actions through a campaign logger before they get to controllers.
- Enable logging of all activity types for your MVC application (both membership and page related activities).
When a visitor arrives on the MVC website through a campaign link with the required UTM parameters, the system can now log campaign page visits and other conversions.
Adding MVC pages to campaigns
Adding pages to campaigns works differently if you only use Kentico as a content platform, with the website presented by a separate MVC application. In these scenarios where the Kentico site is "content only" (i.e., created using the MVC Blank Site template), you cannot select pages from the content tree or create new pages from the campaign interface. MVC sites also do not display the published status of pages.
Moreover, adding the Page visit activity as a conversion or a campaign journey step works also differently for campaigns on MVC sites. See Setting up campaigns on MVC sites for more information.
Important: To track campaign page visits for content hosted on a separate MVC website, your site in Kentico must have its Presentation URL set to the domain (and virtual directory) where the MVC site is running.
Hashing of page visit activities
The system hashes the URLs of Page visit conversions/journey steps and activities on MVC sites to be able to put data for reports together as quickly as possible.
By default, the hash function removes the protocol and all query strings from the URL. The campaign then works regardless of the used protocol (for example, for both http and https). However, the default hash function does not work for sites where displaying of pages is performed via query strings or component identifiers (for example, if the URL of a page on your site looks like http://www.mysite.com/index.html?viewpage=123). More specifically, the noted address will be trimmed to www.mysite.com/index.html, and all pages trimmed to this "URL root" will be logged as conversions for one page. Therefore, SEO-friendly URLs are recommended.
If your site displays its content using query strings or uses any uncovered scenarios, and you want to use campaigns, you can customize the hash function to fulfill your needs. To customize the default hash function, see Customizing the page visit hash function for campaigns in MVC. On the referred page, there is also an example of a hash function that removes the culture code in the page URL so that the campaign works as expected on multilingual MVC sites.
To improve the performance of report calculation, create a database index on the ActivityURLHash column in the OM_Activity database table. The index should be non-clustered and non-unique. See the Create Nonclustered Indexes article for more information.
Was this page helpful?