Difference between revisions of "ATC/Current/AdminGuide/Campaign Attributes"
From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
Line 4: | Line 4: | ||
|Platform=PureEngage, PureConnect, PureCloud | |Platform=PureEngage, PureConnect, PureCloud | ||
|TocName=Campaign attributes | |TocName=Campaign attributes | ||
+ | |ComingSoon=No | ||
|Context=Campaign attributes are special visitor attributes that you use to track activity for specific campaigns. | |Context=Campaign attributes are special visitor attributes that you use to track activity for specific campaigns. | ||
|Section={{Section | |Section={{Section | ||
Line 21: | Line 22: | ||
{{!}}{{!}}Campaign name | {{!}}{{!}}Campaign name | ||
{{!}}{{!}}'utm_campaign' | {{!}}{{!}}'utm_campaign' | ||
+ | {{!}}- | ||
+ | {{!}}{{!}}Campaign content | ||
+ | {{!}}{{!}}'utm_content' | ||
{{!}}- | {{!}}- | ||
{{!}}{{!}}Campaign term | {{!}}{{!}}Campaign term |
Revision as of 09:55, May 15, 2019
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Campaign attributes are special visitor attributes that you use to track activity for specific campaigns.
Enable campaign tracking
To enable UTM tracking for your website:
- Work with your ad network to set up your ad campaigns and identify the UTM parameters you will track. For example, suppose you want to create a new ad campaign called, "SpringSale'.
- For each UTM parameter you want to track, create a corresponding segment in Genesys Predictive Engagement. For example, create a segment called SpringSale. For the visitor attribute, specify "Campaign name like SpringSale".
- When a visitor arrives at a site via a campaign link, Genesys Predictive Engagement automatically assigns the SpringSale segment.
Important
UTM parameters are specific to campaign tracking. If you want to use UTM capabilities, be sure to select a parameter with a name that starts with Campaign.Comments or questions about this documentation? Contact us for support!