Connect Zendesk Support to Google Data Studio with Windsor.ai
Directly connect Zendesk Support to Google Data Studio, in minutes, and in an easy-to-use format.
All your marketing data in one place, just in a few clicks.
Automate and save time.
Use all your data where and when you need it.
About Zendesk Support
Zendesk is a service-first CRM company designed to improve customer relationships. Zendesk Support, one of Zendesk’s core products, provides a central location for businesses to receive, track, and respond to customer inquiries, complaints, and feedback collected across various channels, including email, phone, chat, and social media. The platform has a reputation for being user-friendly and customizable, with many integrations available to help businesses streamline their customer support workflows. More than 160,000 companies of all sizes, from small startups to large corporations, utilize Zendesk to enhance their customer service and customer experience across 160 countries.
Learn more about Zendesk Support
About Google Data Studio
Looker Studio or formerly known as Google Data Studio is a data visualization platform that helps businesses convert data into customizable informative reports and dashboards. It provides a simple and intuitive interface for users to create interactive reports and visualizations with their data. Data analysis using Google Data Studio provides businesses with valuable information that they can use to make informed decisions about their operations.
Learn more about Google Data Studio
Why integrate Zendesk Support with Google Data Studio?
- Google Data Studio can help you create customized dashboards and reports that allow you to monitor key metrics like ticket volume, response time, and resolution rate in one place.
- Visualizing Zendesk Support data in Google Data Studio can enable you to easily spot trends and patterns in your customer support data such as spikes in support tickets on certain days of the week or during certain times of the year and help you make better decisions about staffing, training, and other aspects of your support operation.
- By integrating Zendesk Support with Google Data Studio, you can automate data collection and reporting, reducing the risk of errors and freeing up time for your support team to focus on other tasks.
- Connecting Zendesk Support to Google Data Studio can allow you to identify areas where your support team may be experiencing challenges or where your processes could be optimized that can increase efficiency and reduce costs.
About the Zendesk Support Google Data Studio Connector
The Zendesk Support Google Data Studio connector pulls metrics and dimensions from Zendesk Support. The insights are retrieved at the account, campaign, placement and line item level.
Once the user successfully logs into the connector it’s possible to choose the metrics and dimensions to create a report.
Prerequisites
To set up the connector, the user should have:
- Access to a Zendesk Support account.
- Google account for Zendesk Support to Google Data Studio integration.
- A Windsor account. Start your free trial now.
(Visit our privacy policy and terms of use)
How to connect Zendesk Support to Google Data Studio?
You need to select Zendesk Support as a data Source and grant access to Windsor.ai. You should need to enter Zendesk subdomain alongside your e-mail address and password to grant access.
Select the fields on the right to later use in your data source. For example, you can include metrics such as Status, Subject, or Tags.
Go to “Select Destination” and choose Google Data Studio.
Once done, select “connect” and authorize access to your data source.
Windsor.ai: All your marketing data in one place
Power up your marketing performance with result-driven marketing solutions
- Connect all your marketing, CRM, and analytics data from 50+ platforms and stream it to any spreadsheet tool, BI platform, or data warehouse.
- The setup is done in minutes. No coding is required.
- Currently, we support more than 3000 dimensions and metrics.
- See the value and return on every marketing touchpoint.
- Our marketing attribution software platform provides marketers with a 15-44% increase in marketing ROI.
Google Data Studio Templates for Zendesk Support
Do you plan to connect and visualize Zendesk Support data in Google Data Studio?
These free and customizable Google Data Studio Zendesk Support templates will assist you in visualizing your data for easy reporting and analysis.
Google Data Studio Tutorials for Zendesk Support
Would you like to take your Google Data Studio Zendesk Support dashboards to the next level?
Here are some of our favorite tutorials to help you:
Available Zendesk Support Metrics and Dimensions
| Name | Type | Description |
|---|---|---|
| Allow Attachments | BOOLEAN | Permission for agents to add add attachments to a comment. Defaults to true. |
| Allow Channelback | BOOLEAN | Is false if channelback is disabled, true otherwise. Only applicable for channels framework ticket. |
| Assignee Email | TEXT | Write only. The email address of the agent to assign the ticket to. |
| Assignee Id | TEXT | The agent currently assigned to the ticket. |
| Attribute Value Ids | TEXT | Write only. An array of the IDs of attribute values to be associated with the ticket. |
| Brand Id | TEXT | Enterprise only. The id of the brand this ticket is associated with. |
| Collaborator Ids | TEXT | The ids of users currently CC'ed on the ticket. |
| Collaborators | TEXT | POST requests only. Users to add as cc's when creating a ticket. |
| Comment | TEXT | Write only. An object that adds a comment to the ticket. |
| Created At | DATE | When this record was created. |
| Custom Fields | TEXT | Custom fields for the ticket. |
| Custom Status Id | TEXT | The custom ticket status id of the ticket. |
| Date | DATE | Alias for Created At. |
| Description | TEXT | Read-only first comment on the ticket. When creating a ticket, use comment to set the description. |
| Due At | DATE | If this is a ticket of type task it has a due date. |
| Email cc Ids | TEXT | The ids of agents or end users currently CC'ed on the ticket. |
| Email ccs | TEXT | Write only. An array of objects that represent agent or end users email CCs to add or delete from the ticket. |
| External Id | TEXT | An id you can use to link Zendesk Support tickets to local records. |
| Follower Ids | TEXT | The ids of agents currently following the ticket. |
| Followers | TEXT | Write only. An array of objects that represent agent followers to add or delete from the ticket. |
| Followup Ids | TEXT | The ids of the followups created from this ticket. Ids are only visible once the ticket is closed. |
| Forum Topic Id | TEXT | The topic in the Zendesk Web portal this ticket originated from, if any. The Web portal is deprecated. |
| Group Id | TEXT | The group this ticket is assigned to. |
| Has Incidents | BOOLEAN | Is true if a ticket is a problem type and has one or more incidents linked to it. Otherwise, the value is false. |
| ID | TEXT | Automatically assigned when the ticket is created. |
| Is Public | BOOLEAN | Is true if any comments are public, false otherwise. |
| Macro Id | TEXT | Write only. A macro ID to be recorded in the ticket audit. |
| Macro Ids | TEXT | POST requests only. List of macro IDs to be recorded in the ticket audit. |
| Metadata | TEXT | Write only. Metadata for the audit. In the audit object, the data is specified in the custom property of the metadata object. |
| Organization Id | TEXT | The organization of the requester. You can only specify the ID of an organization associated with the requester. |
| Priority | TEXT | The urgency with which the ticket should be addressed. Allowed values are urgent, high, normal, or low. |
| Problem Id | TEXT | For tickets of type incident, the ID of the problem the incident is linked to. |
| Raw Subject | TEXT | The dynamic content placeholder, if present, or the subject value, if not. |
| Recipient | TEXT | The original recipient e-mail address of the ticket. Notification emails for the ticket are sent from this address. |
| Requester | TEXT | Write only. |
| Requester Id | TEXT | The user who requested this ticket. |
| Safe Update | BOOLEAN | Write only. Optional boolean. Prevents updates with outdated ticket data (updated_stamp property required when true). |
| Satisfaction Rating | TEXT | The satisfaction rating of the ticket, if it exists, or the state of satisfaction, offered or unoffered. The value is null for plan types that don't support CSAT. |
| Sharing Agreement Ids | TEXT | The ids of the sharing agreements used for this ticket. |
| Status | TEXT | The state of the ticket. Allowed values are new, open, pending, hold, solved, or closed. |
| Subject | TEXT | The value of the subject field for this ticket. |
| Submitter Id | TEXT | The user who submitted the ticket. The submitter always becomes the author of the first comment on the ticket. |
| Tags | OBJECT | The array of tags applied to this ticket. |
| Ticket Form Id | TEXT | Enterprise only. The id of the ticket form to render for the ticket. |
| Type | TEXT | The type of this ticket. Allowed values are problem, incident, question, or task. |
| Updated At | DATE | When this record last got updated. |
| Updated Stamp | DATE | Write only. Datetime of last update received from API. |
| URL | TEXT | The API url of this ticket. |
| Via | TEXT | For more information, see the Via object reference |
| Via Followup Source Id | TEXT | POST requests only. The id of a closed ticket when creating a follow-up ticket. |
| Via Id | TEXT | For more information, see the Via object reference |
| Voice Comment | TEXT | Write only. See Creating voicemail ticket. |