Connect Zendesk Support to Looker Studio
Directly connect Zendesk Support to Looker Studio,in minutes, and in an easy-to-use format.
Analyze Your Marketing Metrics from Zendesk Support in GDS
About Zendesk Support
About Looker Studio
Why integrate Zendesk Support with Looker 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.
- The advanced visualization capabilities of Google Data Studio enable you to extract more insights from your Twitter Analytics data and make changes to your strategy to maximize your return on investment on social media.
- 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 for Zendesk Support. The Insights are retrieved at the campaign and ad levels.
Once the user successfully logs into the connector he can then choose the metrics and dimensions he is interested to create a report on.
Prerequisites
To set up the connector, the user should have:
- A Zendesk Support advertiser account (Visit our privacy policy and terms of use)
- Google account for Zendesk Support to Google Data Studio integration.
- A Windsor account. Start your free trial now.
How to connect Zendesk Support to Looker Studio?
Do you plan to connect and visualize your Zendesk Support in Google Data Studio? Follow the Tutorial Below:
Select the fields on the right to later use in your data source. For example, you can include metrics such as Cost per Click, Cost per Action or Total Spend. Go to “Select Destination” and choose Looker Studio. Once done, select “connect” and authorize access to your data source. 
Zendesk Support metrics & dimensions available for streaming into Google Data Studio
name type description Agent Wait Time In Minutes (business) NUMERIC Number of minutes the agent spent waiting during calendar and business hours Agent Wait Time In Minutes (calendar) NUMERIC Number of minutes the agent spent waiting during calendar and business hours 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. Assigned At DATE When the ticket was assigned 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. Assignee Stations NUMERIC Number of assignees the ticket had Assignee Updated At DATE When the assignee last updated 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. Custom Status Updated At DATE The date and time the ticket's custom status was last updated 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. First Resolution Time in Minutes (business) NUMERIC Number of minutes to the first resolution time during calendar and business hours First Resolution Time in Minutes (calendar) NUMERIC Number of minutes to the first resolution time during calendar and business hours 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. From Messaging Channel BOOLEAN If true, the ticket's via type is a messaging channel. Full Resolution Time in Minutes (business) NUMERIC Number of minutes to the first resolution time during calendar and business hours Full Resolution Time in Minutes (calendar) NUMERIC Number of minutes to the first resolution time during calendar and business hours 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. Initially Assigned At DATE When the ticket was initially assigned 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. Reopens NUMERIC Total number of times the ticket was reopened. Replies NUMERIC The number of public replies added to a ticket by an agent Reply Time in Minutes (business) NUMERIC Number of minutes to the first reply during calendar and business hourss Reply Time in Minutes (calendar) NUMERIC Number of minutes to the first reply during calendar and business hours Reply Time in Seconds (business) NUMERIC Number of seconds to the first reply during calendar and business hourss Reply Time in Seconds (calendar) NUMERIC Number of seconds to the first reply during calendar and business hours 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. Solved At DATE When the ticket was solved. Status TEXT The state of the ticket. Allowed values are new, open, pending, hold, solved, or closed. Staus Updated At DATE When the status of the ticket was last updated 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. Today DATE Today's date
Easily connect Zendesk Support to Looker Studio
See the value and return on every marketing touchpoint
Providing 50+ marketing data streams, we make sure that all the data we integrate is fresh and accessible by marketers, whenever they want.
Spend less time on manual data loading and spreadsheets. Focus on delighting your customers.