Difference between revisions of "ATC/Current/AdminGuide/AttributesJourney"
From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
|||
| Line 2: | Line 2: | ||
|Standalone=No | |Standalone=No | ||
|DisplayName=Visitor journey attributes | |DisplayName=Visitor journey attributes | ||
| − | |||
|TocName=Visitor journey attributes | |TocName=Visitor journey attributes | ||
| + | |Context=Learn about the types of attributes that identify visitors based on their shared behaviors. For example, completing a form or going to a specific webpage. | ||
| + | |Dimension= | ||
| + | |UseCase= | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | | | + | |Platform=PureEngage, PureConnect, PureCloud |
| + | |Role= | ||
| + | |Application= | ||
| + | |Prereq= | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=About visitor journey attributes | |sectionHeading=About visitor journey attributes | ||
| − | |anchor= | + | |anchor=AboutVisitorJourneyAttributes |
| − | |||
| − | |||
|alignment=Horizontal | |alignment=Horizontal | ||
| + | |Media=Image | ||
|image=VisitorJourneyPEPC.png | |image=VisitorJourneyPEPC.png | ||
| − | + | |structuredtext=When you create {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger|display text=action maps}}, {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Segments|display text=segments}}, and {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Outcomes|display text=outcomes}}, you use {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=VisitorAttsJourney#Operators|display text=operators}} to define {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_attributes|display text=attributes}}. One type of attribute is a {{GlossaryTooltip|term=visitor journey attribute}}. | |
| − | |structuredtext=When you create {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Segments|display text=segments}} and {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Outcomes|display text=outcomes}}, you | ||
Visitor journey attributes are actions that visitors take on your website. When you define a condition that includes a visitor journey attribute, {{MINTYDOCSPRODUCT}} matches visitors based on whether they do (or do not) take the action. For example, only visitors who complete a form or go to a specific webpage. | Visitor journey attributes are actions that visitors take on your website. When you define a condition that includes a visitor journey attribute, {{MINTYDOCSPRODUCT}} matches visitors based on whether they do (or do not) take the action. For example, only visitors who complete a form or go to a specific webpage. | ||
| Line 25: | Line 28: | ||
Interested in an example? See {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Segment_examples}}. | Interested in an example? See {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Segment_examples}}. | ||
| − | | | + | |structuredtextwide= |
| + | |FAQHeading= | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Types of visitor journey attributes | |sectionHeading=Types of visitor journey attributes | ||
|anchor=TypesJourneyAttrs | |anchor=TypesJourneyAttrs | ||
| − | |||
| − | |||
|alignment=Vertical | |alignment=Vertical | ||
| + | |Media= | ||
| + | |image= | ||
|structuredtext={{{!}} class="wikitable" | |structuredtext={{{!}} class="wikitable" | ||
{{!}}- | {{!}}- | ||
| Line 90: | Line 94: | ||
{{!}}{{!}}packageDeliveryStatus | {{!}}{{!}}packageDeliveryStatus | ||
{{!}}} | {{!}}} | ||
| − | | | + | |structuredtextwide= |
| + | |FAQHeading= | ||
|Status=No | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 19:52, April 30, 2020
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Learn about the types of attributes that identify visitors based on their shared behaviors. For example, completing a form or going to a specific webpage.
About visitor journey attributes
When you create action maps, segments, and outcomes, you use operators to define attributes. One type of attribute is aNo results.
Visitor journey attributes are actions that visitors take on your website. When you define a condition that includes a visitor journey attribute, Genesys Predictive Engagement matches visitors based on whether they do (or do not) take the action. For example, only visitors who complete a form or go to a specific webpage.
A visitor journey attribute can also reflect a negative event. For example a visitor journey attribute might include all customers who added a product to their shopping cart but did not complete the transaction.
Important
- Track these actions as events in your code. To track a more complex visitor journey, add conditions. Genesys Predictive Engagement evaluates all conditions in the visitor journey sequentially, in the order in which you define them.
Types of visitor journey attributes
| Attribute name | Description | Example |
| Event name | Represents the action the customer performed. Our recommended format starts with an object followed by the action performed. |
|
| Page URL | URL of the page | https://www.google.com/search?q=test |
| Page title | Title of the page | Genesys Altocloud lCreate segment |
| Page hostname | Host name of the page's URL | app.genesys.cloud |
| Page domain | Domain of the page's URL | app.genesys.cloud |
| Page fragment | Fragment or hash of the page's URL | #/journey/segment/create |
| Page keywords | Keywords from the HTML<meta>tag of the page | altocloud |
| Page pathname | Path name of the page | /journey/admin/ |
| Search query | Represents the keywords in a customer's search query | test |
| URL query string | Query string that is passed to the page in the current event | q=test |
| Custom attribute | See Custom attributes. | packageDeliveryStatus |
Comments or questions about this documentation? Contact us for support!