Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Setup conversion tracking

Visitors to your website may often go back and forth between your main site or parent domain (such as and a separate blog or subdomain ( The parent and children domains often attract the same audience and display to the audience as a single cohesive experience. Optimizely Content Marketing Platform (CMP) 's conversion tracking lets you have a singular view of activity taken by a user across subdomains, providing a view of the visitor journey. Conversion tracking lets you make informed decisions based on accurate, comprehensive data.

  1. To enable conversion tracking across your organization's parent and child domains, install the JavaScript snippet across your main domain and every subdomain you want to track. CMP's JavaScript Snippet uses Google Tag Manager (GTM) to track events on your website. If you already have Google Tag Manager installed, there should not be any conflicts or impact on your existing setup. 
  2. After installing the JavaScript snippet, work with your CMP technical consultant to create a list of user actions you want to track across domains. Common examples of high-value user actions are metrics that serve as leading indicators of ROI. A B2C company may drive from a blog to a commerce site, whereas a B2B company may track lead generation from completions. If you're having trouble developing actions that seem like a good fit for your business, contact your CMP team so they can work with you to define these goals.
  3. After goals are defined, Optimizely sets up the actions. Twenty-four hours after Optimizely sets up the actions, you can use the Action Analytics tab in the Analytics view to understand your users' interaction with your sites.

You can configure CMP's JavaScript to activate events based on the actions that you decide to track on your blog or main website. When you click a specified action, your last viewed piece of content (stored through a third-party cookie) can be associated with the action event, which powers CMP's Actions analytics feature.

The following image shows some configured and tracked actions. Every time an action occurs, CMP updates the numbers within 24 hours. Suppose an article was the last article that a user consumed within 24 hours of taking an action. In that case, that article is credited for generating the particular action, counted as an action generated by content.


See also Analytics overview in the CMP user guide.