Connect Learning Available in eLearning format in Connect Learning
Comply with data regulations by managing and deleting Customer data, including Contacts, Conversations, and Customer Profiles based on storage duration.
Review the following before you delete Customer data or change Data Retention settings:
See Data Subject Requests to learn how data deletion is handled and processed in Gladly.
See the developer tutorial on automating the deletion of Customer Profiles. If you need to delete more than 50 Customer Profiles and are unable to set up the deletion method via API, send an email to [email protected]. Otherwise, you may delete Profiles one at a time.
Configure Gladly — on a platform level — to either retain all Customer Profile data indefinitely or to automatically delete all Customer Profile data (i.e., Conversations, attachments, recordings, etc.) that exists in Gladly after a <customizable> number of days has passed.
Watch Out – Deleted data can’t be recovered
Deleted Customer Profiles and all the data about a Customer cannot be recovered.
Click on the top left corner of the screen.
Click Settings.
Under the Security and Compliance category, click Customer Data Retention.
Choose from the Customer Data Retention page if you’d like to keep Customer data indefinitely or if it is to be deleted automatically.
Use Default Settings – All Customer Profile data is retained, and no automatic deletion occurs.
Use Custom Settings – Set the number of days Customer Profile data is automatically deleted, counting from their last Contact date. A minimum of 365 days is required.
Click Save.
If you choose to use a custom setting, you’ll be prompted to confirm that you understand the ramifications of this option. Click I Understand, use custom settings to complete your update.
Note – Custom settings and deletion jobs
Deletion jobs – Remember that the countdown to delete Customer Profile data begins on the day of their last Contact. So if you have 365 days configured, any Customer who doesn’t have additional Contacts for 365 days after the date of the last Contact is automatically deleted. This means data deletion jobs may be ongoing as this is a rolling period.
Last activity vs. last Contact – Apps (e.g., Stella, Klaviyo, etc.) that post activity/events in a Profile are excluded from the definition of “last Contact.” For example, if the last Contact with a Customer was on July 11, 2021, and they responded to Stella’s CSAT survey on August 8, 2021, we’ll continue to use July 11, 2021, as the last Contact date.
Delete Customer Profiles independent from your platform-level data retention settings. See Customer Profile level deletion to learn what is deleted.
Watch Out – Deleted Profiles can’t be recovered
Keep this in mind before you delete a Customer’s record.
Open the Profile of the Customer you want to delete from Gladly.
Next to the Customer’s avatar, click, then click Delete Customer.
Note – Customer Profiles with an open Conversation can’t be deleted. This prevents possible errors (e.g., wrong Liveboard status), such as putting phone calls in a bad/unknown state if the Profile is deleted while there’s an active phone call.
You’ll be asked to confirm your deletion request. Click Delete Customer Profile to confirm.
Delete individual messages/Contacts without deleting other records contained in the Profile. For example, you can delete credit card numbers sent as a message that contains PII.
You can only delete one item at a time. See Contact level deletion to learn what is deleted.
Open the Customer’s Profile where you need to delete an item.
From the item (e.g., a Contact), click, then click Delete Message.
You’ll be asked to confirm your deletion request. Click Delete Message to confirm.
Deleted messages appear as “This item has been deleted” in the Conversation Timeline.
Note – Deleting email threads
Deleting an email thread deletes all the messages contained in the thread, including images and attachments contained in the thread.
Delete call recordings or Conversation attachments #
Customers may have the right to access information and data about them. When requested, Compliance Admins can export a JSON file containing all your information about a Customer. Information like their:
Name
Contact information
Address
Custom attributes
Tip – JSON format
JSON stands for JavaScript Object Notation. It’s a plain text format that allows for storing and transporting data while allowing the portability of data. Programs like TextEdit (Mac) and Notepad (PC) can open a JSON file. Open the Profile of the Customer you want to export data for from Gladly.
Open the Profile of the Customer you want to export data from Gladly.
Next to the Customer’s avatar, click, then click Export Customer Profile.
A JSON file is downloaded to your local folder.
The JSON file can be shared with Customers and opened with programs like TextEdit (Mac) and Notepad (PC). The JSON structure can be found on our developer guide.
GDPR, CCPA, and other privacy requests to retrieve a copy of Customer data collected can be performed by you — Gladly’s Customer — through API. When a Customer of yours requests access to their Gladly data for GDPR, CCPA, or any other privacy reason, you can use the Gladly API to retrieve a JSON file containing their entire user history.
Using your preferred API client, create a request to Find Customers. The API response is a portable JSON file that can be shared with the Customer who requested access to their Gladly data. Here’s a curl example of the request:
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.