The Gladly Lookup API allows your organization to pull Customer information from external systems to populate in the Customer Profile. You can provide a web service that implements the Lookup API and Gladly will call it when that data is needed. If you have any questions, please take a look at the Customer Lookup Guide .
From the Apps page, click Add App > Custom, which will take you to the Custom App setup page.
From the Add New Custom Apppage, enter the following information:
Name – Enter a name that will help you identify the integration.
The app name must be unique and not already used in Gladly.
URL – Enter the URL of your Lookup Adaptor.
You must use an “HTTPS” protocol.
Username – Enter the username which will be used in basic authentication. A basic auth header will be included in requests to your integration if a username or password has been entered.
Password – Enter the password which will be used in basic authentication. A basic auth header will be included in requests to your integration if a username or password has been entered.
Realm (Optional) – Enter realm to run basic auth against.
Signing Key – Enter the key that will be used to sign each request that Gladly makes to your lookup service. When you parse Gladly’s POST request during a Customer lookup, you may choose to parse the request headers this field generates for additional security. Please refer to the Customer Lookup Guide for more information.
HTTPS Headers – There are two columns (Header, Value) required for HTTP Headers (e.g., X-API-Key) to include in every request to your lookup service.
Click Add a header to add a new line.
Click to remove a line.
Search Query Attributes – There are two columns (Attribute, Label) required for Search Query Attributes. These are attributes that you can use to search for a Customer. For example, if you put in “points” here, the UI will display “points” as a search field. When an Agent searches “points,” Gladly sends over an exact copy of what the Agent sent to your lookup adapter and expects a return with a list of matching results. Attributes should not contain spaces (e.g., phonenumber).
Click Add an attribute to add a new line.
Click to remove a line.
Search Results Attributes – There are two columns (Attribute, Label) required for Search Results Attributes. These are attributes displayed in a search result when an Agent does a manual search. Attributes should not contain spaces (e.g., phone number).
email – Corresponds to the first email in the email array response from your lookup adapter.
phone– Corresponds to the first phone number array response from your Lookup Adaptor.
externalCustomerId–Corresponds to the externalCustomeRId field in your lookup adapter response.
All other attributes (e.g., loyaltyPoints) will be retrieved from the customAttributes object returned for each Customer Profile.
Click Add an attribute to add a new line.
Click to remove a line.
Auto-Linking Fields – When an Agent lands on a Customer Profile in Gladly that isn’t already linked to a profile in your external source, Gladly will look up the Customer using the following fields. If your external source responds with a unique profile with at least one auto-linking field match and no conflicts, Gladly will automatically link the profiles without any user intervention.
Customer Email– If checked, match Customer information using their email address.
Phone Number – If checked, match Customer information using their phone number.
Overwrite Existing Values – If activated, overwrite the existing name, address, and editable custom attributes in the Customer Profile with data from your external system.
Note – This cannot be used to modify email and/or phone data already in the Customer Profile (e.g., changing a phone type from HOME to MOBILE). If the email address or phone number already exists in Gladly, that value will remain as is.
Actions – If activated, allow activities/actions to be completed in Gladly instead of an external system. See the Actions tutorial for more information on how to set up Actions.
Click Save App when you’re done. An error will appear if the required fields are not completed; they are highlighted in red. Complete the missing field(s) and click Save App again.
Tip – Use unique Custom Attributes when linking a Profile to multiple systems
If you have multiple systems connected to Gladly, we recommend ensuring you use unique customAttributes to prevent overwriting of Customer Profile data from different systems. As an alternative, enable “Overwrite Existing Values” on an integration you want to use as a primary source.
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.