Search the DXM Knowledge Base
You can use targeting groups to help your website visitors focus on items of interest. For example, displaying an East Coast conference to a website visitor from Vermont.
Targeting groups describe which visitors can see your content, based on a set of targeting rules or conditions that you specify and whether or not they match these conditions.
For example, you can deliver optimized and personalized content to visitors who:
DXM offers the best experience to manage, optimize and personalize your visitors’ web experience, directly in DXM since it:
Content authors and editors can vary snippet content that can be applied to Text and WYSIWYG controls, directly within your DXM content.
You can create and manage a targeting campaign by defining your content variants in a WCO snippet, and the associated targeting groups that describe the visitors you want to target. You can manage both new and existing targeting groups via the drag and drop feature, allowing you to select from a number of targeting rules to define the audience or persona they want to target.
DXM's targeting rules fall into the following categories:
To learn more about targeting rules, see WCO Targeting Rules Explained.
DXM provides the following targeting rules to create your targeting groups with:
# Rule Type Use Case Example1 | Time | Targets users based on time of day they visit the site | Target "at work" visitors if they visit during the day and "at home" if they visit in the evening |
2 | Date | Target users based on date or date-range they visit the site | Deliver content before, after or during a campaign; or target a specific holiday |
3 | Device | Target user based on device and browser or on a custom condition in their browser agent | Deliver relevant content to iPhone or Safari users or based on their specific operating system, browser or type of device. This rule checks the user agent string. |
4 | Referrer | Target users based on the previous site they were on prior to arriving at yours | Identify users from search engines, social media sites or partner sites |
5 | Location | Identify and target users from specific regions, states, countries or zip code ranges | Target users in Texas |
6 | Snippet | Target users who view any snippet on any page in your site | Track user interest based on pages viewed |
7 | DemandBase* | Target users with specific DemadBase attributes based on their IP address | Identify competitors, partners, and/or potential customers in various industry segments |
8 | Marketo* | Target users based on their Marketo profile | Optimize your visitor's site experience with data from Marketo |
*Require third party integration
This version of the WCO targeting groups includes a number of common targeting group examples to get you started:
# Targeting Group Name Use Case Example
1 | iPhone Users | Identify users visiting the site on their iPhone | Promote your iPhone app to iPhone users |
2 | Android Users | Identify users visiting the site on any Android device | Display store location information to Android users |
3 | Mobile Users | Identify users visiting the site on any mobile device | Display store location information to mobile visitors |
4 | iPad Users | Identify users visiting the site on their iPad | Promote your iPad app to iPad users |
5 | IE Users | Identify users visiting the site using the IE browser | Deliver optimized CSS or JS based on IE version |
6 | Chrome Users | Identify users visiting the site using the Chrome browser | Deliver optimized CSS or JS based on Chrome version |
7 | Safari Users | Identify users visiting the site using the Safari browser | Deliver optimized CSS or JS based on Safari version |
8 | US Visitors | Identify visitors from the US | Deliver contents exclusive to US visitors |
9 | EU Visitors | Identify visitors from the EU | Deliver contents exclusive to EU visitors |
10 | Canadian Visitors | Identify visitors from Canada | Deliver contents exclusive to Canadian visitors |
11 | East Coast Visitors | Identify visitors from the East Coast of the US | Deliver special announcements and notifications |
12 | West Coast Visitors | Identify visitors from the West Coast of the US | Deliver special announcements and notifications |
13 | Google Visitors | Identify visitors who conducted a Google Search prior to arriving at your site | Highlight Site Navigation and Site Search to help Google Visitors find the content they're looking for |
14 | Bing Visitors | Identify visitors who conducted a Bing Search prior to arriving at your site | Highlight Site Navigation and Site Search to help Bing visitors find they content they’re looking for |
15 | Yahoo Visitors | Identify and target visitors who conducted a Yahoo Search prior to arriving at your site | Highlight Site Navigation and Site Search to help Yahoo visitors find they content they're looking for |
16 | Facebook Visitors | Identify visitors who engaged with your Social Media campaign that redirected them to your site | Extend offers to Facebook visitors |
17 | Twitter Visitors | Identify visitors who engaged with your Social Media campaign that redirected them to your site | Extend offers to Twitter visitors |
18 | LinkedIn Visitors | Identify visitors from LinkedIn who would like to learn more about your company | Redirect LinkedIn visitors to About Us page or Careers section |
Before creating a targeting group, ensure that you've launched a targeting group from the desired asset(s). See above instructions if necessary.
Note: For a singular zip code, select is equal to from the drop-down.
When it comes to targeting variants, WCO will start at the top of your list, and stop matching variants after a match is found. In the in-context or form edit view, the only way to re-order which variant is at the top of the list is to delete and re-add variants to achieve the order you’re interested in.
There's a much easier way to change variant priority, which can be accomplished with the following steps:
The following contains a listing and general information about cookies stored by WCO:
Cookie Name: a
Cookie Domain: snippet.omm.crownpeak.com
The "a" cookie keeps track of IP address recorded for this client's OmmAnonId.
Cookie Name: OmmAnonId
Cookie Domain: .omm.crownpeak.com
The "OmmAnonId`" is a GUID used as the key to the users identity
Cookie Name: ASP.NET_SessionId
Cookie Domain: snippet.omm.crownpeak.com
The "ASP.NET_SessionId" is the session cookie used by WCO
Cookie Name: OmmValues80112474-504a-4bcb-9f86-e212c0b0039a
Cookie Domain: .omm.crownpeak.com
The "OmmValues(key)" is a unique identifier to the specific snippet the cookie is related to.
Note: Cookies do not expire.
Does WCO support AND and OR logical operations?
WCO recognizes any custom parameters included in the snippet’s Javascript call, and exposes these parameters for targeting purposes as Form Field values.
This capability is extremely useful in instances where you need to pass user profile specific attributes to WCO in real-time, or asset specific parameters to the WCO snippet.
Note: This data is not stored in WCO and will not impact your conversion counts. For example, let’s say we need to pass the label or the page that is delivering the WCO snippet. To add this custom real-time attribute to WCO, add the following code to your Output Template:
<%= asset["wco_snippet"].Replace("\" ></script>", "?asset =” + asset.Label + “\" ></script>")%>
The code above will produce the following output:
<script type="text/javascript" src="//snippet.omm.crownpeak.com/s/2c4764a1-b91d-4d37-9aeb-eaabecfa2fc2?asset=Homepage" ></script>
The custom attribute will now be targetable in WCO as a Form Field Value.
How to preview my optimized experiences in DXM?
DXM provides an intuitive interface directly within the authoring experience to preview your content variations for each of the Targeting Groups you’ve defined.
While previewing and/or editing an asset, the [Overview] panel, found in the right side Accordion includes a new [Profile] tab which lists all of the Targeting Groups used on the page. Clicking on any Profile (which is the same as a Targeting Group), will result in re-rending the page in real-time reflecting what the targeted audience would see
How to test geo-location, browser, and device optimized experiences in a browser?Besides testing and validating the content and web experience in Preview mode directly in the CMS, as described in previous tip, you can also test the experience post-publishing in your supported browsers, and devices. You may also test the content and experience from various geographical locations.
To simulate visiting the site from different devices and browsers:
Look for browser extensions that facilitate changing the browser’s User Agent to simulate different devices and browsers.
To simulate visiting the site from geographical locations:
Look for browser extensions that provide Proxy and VPN functions which will simulate visiting the site from different geographical locations.
Search our DXM Forum to find answers to questions asked by other DXM users.
No luck? Ask a question. Our Product and Support teams are monitoring the Forum and typically respond within 48 hours.