Difference between revisions of "ATC/Current/SDK/Destroy"
From Genesys Documentation
m (Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2") |
m (Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2") |
||
| Line 6: | Line 6: | ||
|Dimension= initialization methods | |Dimension= initialization methods | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage-onpremises, PureConnect, | + | |Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud |
|Prereq= | |Prereq= | ||
|Section={{Section | |Section={{Section | ||
Revision as of 12:00, July 15, 2020
This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.
Learn how to use the destroy method to stop all Journey JavaScript SDK activity and remove all tracking information.
Description
The destroy method stops all Genesys Predictive Engagement SDK activity and removes all tracking information.
Signature
ac('destroy')
Arguments
None.
GDPR and destroyed data
The destroy method stops all Genesys Predictive Engagement tracking immediately. In addition to ceasing tracking, the destroy method also removes all cookies set by the SDK; no more proactive engagements will be offered. Use the destroy method if a customer requests that you stop tracking their activities on your website. For more information about using Genesys Predictive Engagement in a GDPR-compliant manner, see GDPR.
Comments or questions about this documentation? Contact us for support!