You can now filter responses by hidden variables and contact attributes using the Responses API. This lets you fetch only the feedback you need, such as responses from a specific store, channel or customer segment, without pulling everything and filtering it yourself.

How it works

• Hidden variables: Use the hidden variable name as the query parameter.
  store_location=Downtown,Airport
• Contact attributes: Add the prefix contact_ to the attribute name.
  contact_plan=Pro,Enterprise
• Multiple values: Separate values with commas to match any of them.

You can combine these with existing filters like surveyId, startDate and limit.

Example

GET /responses?store_location=Downtown,Airport&contact_plan=Pro,Enterprise

This returns responses from the Downtown or Airport stores, submitted by contacts on the Pro or Enterprise plan.

Use cases

• Sync feedback for specific locations or regions into your BI tools
• Analyse responses by customer plan, tier or segment
• Build focused reports without extra filtering on your side

View the Responses API documentation → 

We're excited to roll out the Zonka Feedback MCP Server — a new way to work with your customer feedback right inside the AI tools your team already uses, like Claude and ChatGPT.

Until now, getting answers from your feedback meant opening dashboards, building reports, or exporting data. With the MCP server, you just ask — in plain language, from your AI assistant, using your live Zonka Feedback data.

What's New?

🔗 Connect your AI tools to Zonka Feedbackng dashboards, building reports, or exporting data. With the MCP server, you simply ask—in plain language, from your AI assistant—using your live Zonka Feedback data.

Link Claude, ChatGPT, or any MCP-compatible tool to your account in a couple of clicks. Zonka Feedback is listed in the Claude connector directory, so there's nothing to wire up by hand.

🧠 Ask questions in plain language

Query your survey responses, NPS, CES, CSAT, and sentiment, online reviews and reputation, and your AI Feedback Intelligence themes — down to the verbatim quotes behind them — just by asking. No exports, no query language.

🔐 Grounded in your data, scoped to your permissions

Every connection signs in with OAuth and runs with that user's own role and access. The connector is read-only — it reads and analyzes your feedback, and never changes your account.

Why It Matters

• Answers where you already work: pull feedback insights inside your AI assistant, not another tab.
• Skip the export-and-analyze loop: go from question to answer in seconds.
• Trustworthy by design: read-only, permission-aware, and traceable back to real customer responses.

Example Use Cases

📊 Track your metrics — "What's our NPS this quarter, and how does it compare to last?"

🧠 Find what's driving sentiment — "Which themes are behind our negative feedback right now?"

⭐ Watch your reputation — "What's our average review rating this year, and how many did we reply to?"

Plan Availability

Available on all plans. An account admin turns it on under Settings → AI Governance → AI Features → Agents & MCP, after which everyone on the account can connect their own AI tool.

Learn more here

Your CRM and helpdesk can now show more than what customers said. They can also show how customers felt and what they need. 🎯

You can now map Sentiment, Emotion, Intent, and Urgency to fields in Salesforce, HubSpot, Intercom, and every other integration that supports one-to-one field mapping.

How to set it up

1. Go to your survey → Integrations and open the integration you want.
2. Create a new mapping or edit an existing one.
3. Under Map Fields, click + Add Attribute.
4. Choose Sentiment, Emotion, Intent, or Urgency, then pick the field it should sync to.
5. Click Save.

From then on, each new response sends its AI-detected signals to the fields you mapped.

What your teams can do with it

• Sales: flag deals where sentiment from key contacts turns negative.
• Customer Success: build churn-risk views from frustrated or disappointed customers.
• Support: prioritize and route conversations by urgency and intent.

Your teams can act on feedback signals in the tools they already use, without logging into Zonka Feedback.

When Zonka sends a response to a connected tool — creating a ticket, posting a notification, or syncing the full response — it now carries every attribute on that response, not just the survey answers and a fixed set of contact fields.

Now included:

• Contact attributes — email, mobile, name and any other contact fields
• Response attributes — device, location, & agent etc.
• Hidden attributes — values you pass at send time
• Integration attributes — order, ticket and record data from the integration that triggered the survey

Attributes also travel across integrations, not just back where they came from. A Shopify post-purchase survey response now carries its order ID, order total, line items and shipping type into the Zendesk ticket it creates — so your team sees the order behind the feedback without leaving the helpdesk.

This works across ticket creation, notifications and full response sync, in every integration you've connected.

Salesforce mappings used to force a choice up front: create a new record, or update an existing one. Pick wrong and you got duplicate Contacts, or updates that went nowhere.

Custom Mapping now has a fourth action: Create or update a record using an External ID.

Choose a Salesforce field you already use to identify customers — account number, CRM ID, subscription reference — and every response is checked against it. Match updates the record. No match creates one.

Get the identifier onto a response three ways:

• Survey link — ?sf_External_Field_1__c=Get%20Started (sf_ prefix + the Salesforce API name)
• Survey question — pick it in the Match Value dropdown
• Salesforce email trigger — pass the field through and it rides along with the survey

Set it up under Integrations → Salesforce → Add Mapping. Only fields marked as External ID in Salesforce appear — mark yours Unique too, or a value matching multiple records won't sync. Matching is exact, case and spacing included.

Setup guide →

Tested your Salesforce integration in a sandbox? Take it live without rebuilding anything from scratch.

What is Sandbox to Production migration?

From your survey's Integrations → Salesforce screen, select Switch to Production and authorise your production org. Your mappings, filters, email trigger configuration, and synced users all carry over as they were. Zonka then validates the configuration against your production org and shows you a summary of what transferred — and flags anything that needs attention.

Whether you're:

• Moving a fully configured integration to production after UAT
• Preserving complex field mappings you don't want to redo manually
• Carrying over email trigger settings and synced user configurations
• Checking what transferred before anyone goes live

💡 Key Use Cases

Zero-rebuild go-live Switch orgs with one authorisation step and keep everything intact. Example: A RevOps team spent two weeks mapping custom fields and configuring triggers in sandbox — they switch to production in minutes, nothing lost.

Automatic field validation Zonka checks every mapped field against your production org and surfaces mismatches immediately. Example: A field that existed in sandbox but wasn't deployed to production gets cleared automatically — the rest of the mapping keeps working without interruption.

Pause and recover missing objects If an entire object is missing in production, that mapping is paused rather than deleted. Example: A custom object wasn't deployed yet — once it's created in production, use Re-validate to bring the mapping back without reconfiguring it.

Available on all Salesforce Plans

Slice your Response Inbox and survey reports using the Salesforce data already attached to your responses — no extra configuration needed.

What is Salesforce response filtering?

Any Salesforce merge field you've selected on a survey's automated email trigger is automatically available as a filter under + Add Filter → Salesforce Merge Fields. Conditions adapt to the field type, so you get the right operators for text, dates, numbers, and picklists — including the actual values held in Salesforce.

Whether you're:

• Filtering by account owner to review responses by rep
• Segmenting by a date field to track a specific campaign window
• Narrowing down by picklist value like region or plan tier
• Combining a Salesforce field with an NPS segment and a date range

💡 Key Use Cases

Segment by account or ownership Filter responses to a specific account owner or team directly from your report. Example: A CX lead wants to see all detractor responses from accounts owned by the enterprise sales team — done in two clicks.

Track campaign or lifecycle cohorts Use date or ID fields from Salesforce to isolate responses tied to a specific onboarding batch or renewal cycle. Example: Filter by Onboarding Start Date to see feedback from customers in their first 30 days.

Build and share focused views Combine Salesforce filters with existing ones, save the result as a view, or share it via URL with your team. Example: An ops manager shares a pre-filtered report with the customer success team every Monday — no manual exports.

Worth knowing: filters are survey-specific and only show merge fields on that survey's own trigger. Responses collected outside Salesforce — via web link or SMS — will appear as Not Filled.

Available on all Salesforce Plans

What does the Klaviyo integration do?

Every survey response can now automatically update a Klaviyo profile, add a respondent to a list, or trigger a flow — with no manual exports or data wrangling. The integration works both ways: pull Klaviyo contacts into Zonka to survey them, or push feedback back into Klaviyo to personalize your campaigns.

Whether you're:

• Syncing NPS, CSAT, or CES scores to Klaviyo profiles for real-time segmentation
• Adding respondents to lists like NPS Promoters or detractors-to-win-back on submit
• Embedding a survey question directly into a Klaviyo email campaign
• Triggering survey sends automatically from a Klaviyo flow
• Keeping contacts in sync across both platforms without manual imports

💡 Key Use Cases

Segment by feedback, not just behaviour Map survey scores to Klaviyo profile properties and build segments the instant feedback lands. Example: Detractors from your post-purchase NPS flow automatically enter a win-back sequence — no manual tagging needed.

Embed surveys inside Klaviyo emails Drop a question, button, or hyperlink into any campaign using ready-made HTML. Responses tie back to the Klaviyo profile, so you can act on them without switching tools. Example: A one-click CES question inside your onboarding email, with scores synced to the contact's profile.

Keep both platforms in sync Two-way sync pulls Klaviyo profiles into Zonka as contacts and keeps them current — automatically or on demand. Example: A new list segment in Klaviyo is available in Zonka for survey targeting within minutes, with no CSV in sight.

🔗 View Integration Guide →
🔗 Find us on the Klaviyo Marketplace →

Available on Growth plan and above.

Export the responses behind any theme or sub-theme as a CSV — filtered, column-picked, and delivered to your inbox.

Click the export icon on the filter bar, next to a theme title, or on any sub-theme card. Select a date range, choose your columns, and you're done. Each row is one response × one sub-theme, so sentiment stays accurate even when a response is tagged under multiple sub-themes.

💡 Key Use Cases

Theme-level exports for focused analysis Export exactly the responses tagged to a theme or sub-theme — nothing else. Example: A CX manager spots a spike in "Billing Confusion" and exports just those responses to share with the Finance team.

Accurate sentiment per tag Because each row is one response × one sub-theme, a response tagged under three sub-themes appears three times — each with its own sentiment intact. Example: A response mentioning both "Onboarding" and "Support Speed" shows up under each, so neither theme's sentiment gets diluted.

Flexible column selection Choose only the columns relevant to your audience before exporting. Example: A quarterly review export includes response text, NPS score, and account name — nothing else cluttering the sheet.

Worth knowing: the CSV is delivered by email and the download link is valid for 5 days.

Available on Growth and Enterprise plans with Intelligence Hub addon.

You can now see exactly what your integrations are doing — every event, every status, in one place with Integration Logs. They are useful in the following ways.

• Confirming a sync ran after a specific response came in
• Checking whether a failed event affected a particular record
• Auditing which responses triggered your integration over a date range
• Troubleshooting before raising a support request

💡 Key Use Cases

Know when something goes wrong — before it becomes a problem Failed events surface immediately with enough context to act. Example: Three responses didn't sync to your CRM — the log shows exactly which ones, so you can follow up without waiting on support.

Confirm your setup is working After configuring a new integration, verify it's firing correctly without guessing. Example: A new Klaviyo integration was set up yesterday — the log confirms responses are syncing to the right profiles.

Answer audit questions yourself 30 days of history means you don't need to raise a ticket every time someone asks "did this run?". Example: Confirming whether a webhook fired for a specific account before a customer call.

Available on all plans