Map traits to link customer records
Contents
To see more complete customer profiles in Live Now, use the Traits Mapper to link all records for the same customer.
About traits mapping
Traits are properties, such as "email" and "gender" for a customer. Genesys Predictive Engagement gathers customer traits every time a customer visits a website that you track with the Genesys Predictive Engagement tracking snippet. In some cases, you may have multiple customer records for the same person. For example, if a customer visits your website multiple times and uses a different browser each time. Because Genesys Predictive Engagement creates a separate record for each instance, the separate customer records may contain only a subset of all of the traits information that is actually available for the customer. You can link these separate customer records by mapping the traits information they contain. After you do this, you'll be able to see the complete customer information in Live Now.
After customer records are linked, the traits mapper updates all of the records when new trait information becomes available. Existing or duplicate traits are overwritten with the most current trait information.
View mapped traits in the user interface
After you map traits, they appear here:
- PureCloud > Admin menu > Live Now > Customer summary (admin view)
- Agent user interface > Journey gadget > [[ATC/Current/AgentGuide/Customer_details|]]
Map traits globally
To start mapping traits, define a global traits mapper when you deploy the Altocloud tracking snippet on your website. Specifically, when you call init to initialize the Journey JavaScript SDK, identify which attributes you want to treat as traits. See the following code example. For more information, see Methods that track events and Mappable traits.
Whenever Genesys Predictive Engagement gathers values for these attributes, they are automatically mapped as traits.
You can also map traits based on specific events.
Example
<script>
(function(a,t,c,l,o,u,d){a['_genesysJourneySdk']=o;a[o]=a[o]||function(){
(a[o].q=a[o].q||[]).push(arguments)},a[o].l=1*new Date();u=t.createElement(c),
d=t.getElementsByTagName(c)[0];u.async=1;u.src=l;u.charset='utf-8';d.parentNode.insertBefore(u,d)
})(window, document, 'script', 'https://apps.mypurecloud.com/journey/sdk/js/web/v1/ac.js', 'ac');
ac('init', 'c232166f-0136-4557-8dce-c88339d17a4e', {
region: 'use1',
globalTraitsMapper: [
{
"fieldName": "emailAdddress",
"traitName": "email"
}, {
"fieldName": "sex",
"traitName": "gender"
}
]
});
ac('pageview');
</script>Map traits for a specific event
In addition to mapping traits globally, you can map specific traits locally for specific events. For more information, see Methods that track events and Mappable traits.
The complete set of map traits for a customer is the union of globally mapped traits and locally mapped traits. For example, suppose you map the email address field via the global traits mapper, but on one page, you ask for the customer's Facebook ID. In this case, both the email address and the Facebook ID are mapped to the customer and both appear in the customer's Live Now profile.
If the same data is captured in two places, the most recent trait mapped appears in Live Now. Previous values for mapped traits are not preserved.
Examples of mapped traits
The following examples show how attributes that are mapped traits. Specifically:
- The attributes, "email" and "emailAdddress" are mapped to the trait "email."
- The attributes, "gender" and "sex" are mapped to the trait "gender."
Methods that track events
Traits mapping can occur whenever there is a tracked event on your website. Specifically, events are tracked when you use the following methods:
Mappable traits
Demographic traits
| Trait | Example |
| gender | male |
| birthDate | 01012001 |
Company traits
| Trait | Example |
| companyName | Genesys |
| dunsNumber | 622286318 |
| industry | Technology |
| numberofEmployees | 5025 |
ID traits
| Trait | Example |
| JTS1715@gmail.com | |
| facebookId | JTSmith1715 |
| messengerId | John.Smith .1715 |
| twitterId | @JTS1715 |
| telegramId | 123456789 |
Phone traits
| Trait | Example |
| homePhone | 3179871234 |
| mobilePhone | |
| workPhone |
Name traits
| Trait | Example |
| salutation | Question: Is this title? |
| jobTitle | Manager |
| givenName | John |
| middleName | Thomas |
| familyName | Smith |
| displayName | John |