Difference between revisions of "ATC/Current/AdminGuide/AttributesJourney"
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
Line 1: | Line 1: | ||
{{Article | {{Article | ||
|Standalone=No | |Standalone=No | ||
− | |DisplayName= | + | |DisplayName=Visitor journey attributes |
|Platform=PureEngage, PureConnect, PureCloud | |Platform=PureEngage, PureConnect, PureCloud | ||
− | |TocName= | + | |TocName=Visitor journey attributes |
|ComingSoon=No | |ComingSoon=No | ||
− | |Context= | + | |Context=Visitor journey attributes are actions that all visitors in the group take. For example, completing a form or going to a specific webpage. |
|Section={{Section | |Section={{Section | ||
− | |sectionHeading=About journey attributes | + | |sectionHeading=About visitor journey attributes |
|Type=Structured | |Type=Structured | ||
|anchor=VisitorJourneys | |anchor=VisitorJourneys | ||
Line 13: | Line 13: | ||
|image=VisitorJourneyPEPC.png | |image=VisitorJourneyPEPC.png | ||
|gif=No | |gif=No | ||
− | |structuredtext= | + | |structuredtext=Visitor journey attributes are actions that all visitors in the group take. For example, completing a form or going to a specific webpage. |
− | Define journey attributes for use with {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Segments|display text=segments}} and {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Outcomes|display text=outcomes}}. | + | Define visitor journey attributes for use with {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Segments|display text=segments}} and {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=Outcomes|display text=outcomes}}. |
− | A journey attribute can also reflect a negative event. For example a journey attribute might include all customers who added a product to their shopping cart but did not complete the transaction. | + | 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. |
{{NoteFormat| | {{NoteFormat| | ||
Line 27: | Line 27: | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Types of journey attributes | + | |sectionHeading=Types of visitor journey attributes |
|Type=Structured | |Type=Structured | ||
|anchor=TypesJourneyAttrs | |anchor=TypesJourneyAttrs |
Revision as of 11:59, May 28, 2019
Contents
Visitor journey attributes are actions that all visitors in the group take. For example, completing a form or going to a specific webpage.
About visitor journey attributes
Visitor journey attributes are actions that all visitors in the group take. For example, completing a form or going to a specific webpage.
Define visitor journey attributes for use with segments and outcomes.
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.
- 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.
- If you want to match based on a non-numeric criteria, such as the name of a browser, select the like or not like operator.
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 below. | packageDeliveryStatus |
Custom attributes
A custom attribute targets any extra information that you want to send to Genesys Predictive Engagement through a call toac('record).
For example, an ecommerce site might add a 'packageDeliveryStatus' attribute to segment users whose packages have been shipped.
Segment based on search queries
You can add visitors to segments based on their search queries.
- Under Visitor journey, in the list, select Search query.
- In the operator list, select your operator.
- In the box, type the words or phrases that match the visitor to the segment. Separate items with commas.
