Difference between revisions of "ATC/Current/SDK/Traits mapper"

From Genesys Documentation
Jump to: navigation, search
(Published)
m (Text replacement - "Genesys Engage" to "Genesys Multicloud CX")
Line 30: Line 30:
 
*Genesys Cloud > Admin menu > Live Now > {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Customer_details}}
 
*Genesys Cloud > Admin menu > Live Now > {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Customer_details}}
 
*Agent user interface > Journey gadget >  
 
*Agent user interface > Journey gadget >  
**{{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=GenesysEngage|anchor=VisitorInfo|display text=Visitor information (Genesys Engage)}}
+
**{{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=GenesysEngage|anchor=VisitorInfo|display text=Visitor information (Genesys Multicloud CX)}}
 
**{{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=PureConnect|anchor=VisitorInfo|display text=Visitor information (PureConnect)}}
 
**{{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=PureConnect|anchor=VisitorInfo|display text=Visitor information (PureConnect)}}
 
|Status=No
 
|Status=No

Revision as of 21:12, November 9, 2021

This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.

Learn how to map multiple records for the same customer to see more complete customer profiles in Live Now.

Important
This article only applies to customers using web chat. If you are a Genesys Cloud customer, we encourage you to use the new web messaging feature to replace web chat.

About traits mapping

Traits are properties, such as a customer's email address or phone number. Genesys Predictive Engagement gathers customer traits every time a customer visits a website that you track with the Genesys Predictive Engagement tracking snippet. It's possible to have multiple customer records for the same person. For example, when 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 the available customer traits. You can map the traits that the separate customer records contain to link the records. Then, you can see the complete customer information in Live Now.

Important
When the traits mapper links customer records, it preserves the separate customer records. It doesn't consolidate them into a single customer record. Instead, the traits mapper updates all linked customer records with the current traits information.

After linking customer records, the traits mapper updates all the records when new trait information becomes available. It overwrites existing or duplicate traits with the most current trait information.

View mapped traits in the user interface

After you map traits, they appear here:

AI-381 Replace image in previous section

View mapped traits in user interface

Map traits globally

To start mapping traits, define a global traits mapper when you deploy the Genesys Predictive Engagement tracking snippet on your website. Specifically, when you call init to initialize the Journey JavaScript SDK, identify which attributes to treat as traits. See the following code example.

For more information, see Methods that track events and Mappable traits.

When Genesys Predictive Engagement gathers values for these attributes, they map 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": "emailAddress",
        "traitName": "email"
      }, {
        "fieldName": "sex",
        "traitName": "gender"
      }
    ]
  });
  ac('pageview');
</script>

AI-381 Replace example in previous section

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": "emailAddress",
        "traitName": "email"
      }, {
        "fieldName": "company",
        "traitName": "companyName"
      }
    ]
  });
  ac('pageview');
</script>

Map traits for a specific event

You can map specific traits locally instead of globally 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 and locally mapped traits. For example, suppose you map the email address field using the global traits mapper, but on one page you ask for the customer's phone number. Both the email address and the phone number map to the customer and both appear in the customer's Live Now profile.

If Genesys Predictive Engagement captures the same data 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 to map attributes as traits. Specifically:

  • The attributes, "email" and "emailAddress" map to the trait "email."
  • The attributes, "gender" and "sex" map to the trait "gender."


Attributes traitsMapper Traits
{

    "email": "firstname.lastname@somemail.com",

    "gender": "male",

    "comment": "This is great",

    "section": "support"

}

[

   {"fieldName": "email"},

   {"fieldname": "gender"}

]

{

    "email": firstname.lastname@somemail.com",

    "gender": "male"

}

{

    "emailAddress": "firstname.lastname@somemail.com",

    "sex": "male",

    "comment": "This is great",

    "section": "support"

}

[

{

    "fieldName": "emailAddress",

    "traitName": "email"

   }, {

      "fieldname": "sex",

      "traitName": "gender"

}

]

{

    "email": firstname.lastname@somemail.com",

    "gender": "male"

}


AI-381 Replace previous section

The following examples show how to map attributes as traits. Specifically:

  • The attributes, "email" and "emailAddress" map to the trait "email."
  • The attributes, "company" and "companyName" map to the trait "companyName."
Attributes traitsMapper Traits
{

    "email": "firstname.lastname@somemail.com",

    "companyName": "ABC corporation",

    "comment": "Here is a comment",

    "section": "support"

}

[

   {"fieldName": "email"},

   {"fieldname": "companyName"}

]

{

    "email": firstname.lastname@somemail.com",

    "companyName": "ABC corporation"

}

{

    "emailAddress": "firstname.lastname@somemail.com",

    "company": "ABC corporation",

    "comment": "Here is a comment",

    "section": "support"

}

[

{

    "fieldName": "emailAddress",

    "traitName": "email"

   }, {

      "fieldname": "company",

      "traitName": "companyName"

}

]

{

    "email": firstname.lastname@somemail.com",

    "companyName": "ABC corporation"

}

Methods that track events

Traits mapping can occur whenever there is a tracked event on your website. Specifically, Genesys Predictive Engagement tracks events when you use the following methods:

Mappable traits

ID traits

Trait Example
email JTS1715@gmail.com

Phone traits

Trait Example
homePhone 3179871234
cellPhone 3179871235
otherPhone 3179712356
workPhone 8179874321

Name traits

Trait Example
salutation Mr.
jobTitle Manager
givenName John
middleName Thomas
familyName Smith
Retrieved from "https://all.docs.genesys.com/ATC/Current/SDK/Traits_mapper (2024-11-09 15:04:30)"
Comments or questions about this documentation? Contact us for support!