Gladly Source
Source Info
The Gladly Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
Gladly is the only platform purposely built to help the world’s fastest growing brands deliver radically personal customer service. Designed around people and not tickets, Gladly’s all-in-one platform features every channel - from voice to SMS - natively built into a single UI, allowing agents to communicate seamlessly across all channels. Rated the #1 easiest-to-use customer service platform, Gladly is empowering brands of all sizes to deliver and scale exceptional customer and agent experiences and build brand loyalty.
The Gladly Source is an Event Cloud Source that can be used to track when your customers open or closed a conversation with an agent. Not only can you export data into your Segment warehouse, but you can also send the exported data into your other enabled Segment Destinations.
This source is maintained by Gladly. For any issues with the source, contact the Gladly Support team.
Getting Started
- From your workspace’s Sources catalog page click Add Source.
- Search for “Gladly” in the Sources Catalog, select click Gladly, and click Add Source.
- On the next screen, give the Source a nickname configure any other settings.
- Click Add Source to save your settings.
- Copy the
Write keyfrom the Segment UI - Log into Gladly
- Go to Settings -> App Developer Tools -> Apps
- Click Add App and select Segment
- Name your app
- Paste your
Write Keyinto the Segment Private Key field - Save your app
Events
The table below lists events that Gladly sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Gladly includes the userId if available.
| Event | Description |
|---|---|
| Conversation Opened | A conversation was opened and assigned to an agent |
| Conversation Closed | A conversation was closed and required no further action |
Event properties
The table below list the properties included in the events listed above.
| Property Name | Description |
|---|---|
| event | Conversation Status |
| userId | Customer’s Gladly ID |
| customerName | Customer’s Name |
| Customer’s Email Address | |
| phone | Customer’s Phone Number |
| conversationId | Conversation’s ID |
| status | Conversation’s Status |
| topics | List of Topic IDs for a Conversation (only for Conversation Closed) |
| agentId | Assigned Agent’s ID |
| agentName | Assigned Agent’s Name |
| timestamp | Conversation Opened/Conversation Closed time |
Add Destinations
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.
If there are any issues with how the events are arriving to Segment, contact the Gladly support team.
This page was last modified: 27 Oct 2023
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!