Difference between revisions of "ATC/Current/AdminGuide/Web tracking"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "|Type=Structured" to "|Type=Structured |gif=No")
(Published)
Line 8: Line 8:
 
|sectionHeading=About web tracking
 
|sectionHeading=About web tracking
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=AboutWebTracking
 
|anchor=AboutWebTracking
 
|alignment=Vertical
 
|alignment=Vertical
 +
|gif=No
 
|structuredtext={{MINTYDOCSPRODUCT}} analyzes the paths your visitors take on your website to determine when to trigger action maps and to calculate visitors' outcome scores.
 
|structuredtext={{MINTYDOCSPRODUCT}} analyzes the paths your visitors take on your website to determine when to trigger action maps and to calculate visitors' outcome scores.
 
|fullwidth=No
 
|fullwidth=No
Line 16: Line 16:
 
|sectionHeading=Configure web tracking
 
|sectionHeading=Configure web tracking
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=ConfigureWebTracking
 
|anchor=ConfigureWebTracking
 
|alignment=Vertical
 
|alignment=Vertical
 +
|gif=No
 
|structuredtext=# Click '''Settings > Web Tracking'''.
 
|structuredtext=# Click '''Settings > Web Tracking'''.
 
# Specify the [[#AllowedDomains|allowed domains]].
 
# Specify the [[#AllowedDomains|allowed domains]].
Line 30: Line 30:
 
|sectionHeading=Allowed domains
 
|sectionHeading=Allowed domains
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=AllowedDomains
 
|anchor=AllowedDomains
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=AllowedDomains0131.png
 
|image=AllowedDomains0131.png
 +
|gif=No
 
|structuredtext=In the '''Allowed Domains''' box, indicate which domains are allowed to send data to {{MINTYDOCSPRODUCT}}. These are the domains you want to track.
 
|structuredtext=In the '''Allowed Domains''' box, indicate which domains are allowed to send data to {{MINTYDOCSPRODUCT}}. These are the domains you want to track.
 
* Separate multiple domains with a comma.  
 
* Separate multiple domains with a comma.  
Line 41: Line 41:
 
|sectionHeading=Short ID length
 
|sectionHeading=Short ID length
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=ShortIDLength
 
|anchor=ShortIDLength
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=ShortIDLength2.png
 
|image=ShortIDLength2.png
 +
|gif=No
 
|structuredtext={{MINTYDOCSPRODUCT}} assigns each visit a unique number that is based on a lengthy, automatically generated ID. In the Short ID field, indicate the number of digits that {{MINTYDOCSPRODUCT}} should use for each visit ID.   
 
|structuredtext={{MINTYDOCSPRODUCT}} assigns each visit a unique number that is based on a lengthy, automatically generated ID. In the Short ID field, indicate the number of digits that {{MINTYDOCSPRODUCT}} should use for each visit ID.   
  
Line 51: Line 51:
 
{{NoteFormat|If you find that you need a longer short ID, you can increase the length at any time. Your changes will take effect immediately. |1}}
 
{{NoteFormat|If you find that you need a longer short ID, you can increase the length at any time. Your changes will take effect immediately. |1}}
  
−
{{NoteFormat|To make it easier for agents and visitors to discuss the visitor's experience on your website, display the short ID on your site, as shown in the image. For more information on how to do this, see <tt>ac('api.visit.get', function(visit) {console.log(visit); });</tt> in the {{#mintydocs_link:manual=Developers}} . |2}}
+
{{NoteFormat|To make it easier for agents and visitors to discuss the visitor's experience on your website, display the short ID on your site, as shown in the image. For more information on how to do this, see {{Link-SomewhereInThisProduct|version=Current|manual=SDK|topic=Integrate_short_ID}}.|2}}
 
|fullwidth=No
 
|fullwidth=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=Exclude URL query parameters
 
|sectionHeading=Exclude URL query parameters
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=ExcludeURLQueryParameters
 
|anchor=ExcludeURLQueryParameters
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=ExcludeURLQuery0131.png
 
|image=ExcludeURLQuery0131.png
 +
|gif=No
 
|structuredtext=Specify any URL Query Parameters we should ignore. URL query parameters appear near the end of URLs. They can lead to overly-specific tracking data. They can also potentially expose personally identifiable information, which violates GDPR.
 
|structuredtext=Specify any URL Query Parameters we should ignore. URL query parameters appear near the end of URLs. They can lead to overly-specific tracking data. They can also potentially expose personally identifiable information, which violates GDPR.
 
|fullwidth=No
 
|fullwidth=No
Line 65: Line 65:
 
|sectionHeading=Keep URL fragments
 
|sectionHeading=Keep URL fragments
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=KeepURLFrag
 
|anchor=KeepURLFrag
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=KeepURLFrag.png
 
|image=KeepURLFrag.png
 +
|gif=No
 
|structuredtext=Indicate whether {{MINTYDOCSPRODUCT}} should use URL fragments to identify web pages. URL fragments appear after a # in a URL. For example in <tt>"altocloud.com#pagename"</tt>, <tt>#pagename</tt> is a URL fragment.  
 
|structuredtext=Indicate whether {{MINTYDOCSPRODUCT}} should use URL fragments to identify web pages. URL fragments appear after a # in a URL. For example in <tt>"altocloud.com#pagename"</tt>, <tt>#pagename</tt> is a URL fragment.  
  
Line 79: Line 79:
 
|sectionHeading=Site search settings
 
|sectionHeading=Site search settings
 
|Type=Structured
 
|Type=Structured
−
|gif=No
 
 
|anchor=SiteSearchSettings
 
|anchor=SiteSearchSettings
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|image=SiteSearch0131.png
 
|image=SiteSearch0131.png
 +
|gif=No
 
|structuredtext=Type the parameter for search terms on your website. For example, if “?term=Sale#search” is appended to the end of your URL when a customer searches for “Sale,” type “term” in this box.
 
|structuredtext=Type the parameter for search terms on your website. For example, if “?term=Sale#search” is appended to the end of your URL when a customer searches for “Sale,” type “term” in this box.
 
|fullwidth=No
 
|fullwidth=No
 
}}
 
}}
 
}}
 
}}

Revision as of 17:24, March 27, 2019

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

Configure how Genesys Predictive Engagement tracks your visitors as they move through your website.

About web tracking

Genesys Predictive Engagement analyzes the paths your visitors take on your website to determine when to trigger action maps and to calculate visitors' outcome scores.

Configure web tracking

  1. Click Settings > Web Tracking.
  2. Specify the allowed domains.
  3. Specify the short ID length.
  4. Specify any URL query parameters that Genesys Predictive Engagement should ignore.
  5. Indicate whether Genesys Predictive Engagement should keep URL fragments.
  6. Specify any site search settings.
  7. Click Save.

Allowed domains

In the Allowed Domains box, indicate which domains are allowed to send data to Genesys Predictive Engagement. These are the domains you want to track.

  • Separate multiple domains with a comma.
  • Do not include spaces.

Short ID length

Genesys Predictive Engagement assigns each visit a unique number that is based on a lengthy, automatically generated ID. In the Short ID field, indicate the number of digits that Genesys Predictive Engagement should use for each visit ID.

You should choose a short ID length that is long enough to be unique among all visitors that are currently active on your website. The more traffic your site gets, the longer your short ID should be. For example: if you always have less than 10,000 visitors at any time, a short ID length of 4 will suffice. If you could have more than 100,000 visitors at any one time, then you should choose a short ID length of 6.

Important
If you find that you need a longer short ID, you can increase the length at any time. Your changes will take effect immediately.
Tip
To make it easier for agents and visitors to discuss the visitor's experience on your website, display the short ID on your site, as shown in the image. For more information on how to do this, see [[ATC/Current/SDK/Integrate_short_ID|]].

Exclude URL query parameters

Specify any URL Query Parameters we should ignore. URL query parameters appear near the end of URLs. They can lead to overly-specific tracking data. They can also potentially expose personally identifiable information, which violates GDPR.

Keep URL fragments

Indicate whether Genesys Predictive Engagement should use URL fragments to identify web pages. URL fragments appear after a # in a URL. For example in "altocloud.com#pagename", #pagename is a URL fragment.


While URL fragments can identify specific webpages, they can also potentially expose personally identifiable information, which violates GDPR. They can also result in an excess amount of tracking data.

Important
Unless you want to track the URL fragments, do not enable this option.

Site search settings

Type the parameter for search terms on your website. For example, if “?term=Sale#search” is appended to the end of your URL when a customer searches for “Sale,” type “term” in this box.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Web_tracking (2025-06-19 06:13:16)"
Comments or questions about this documentation? Contact us for support!