What we do
Tools
Industries
Department
How we workLet's talk →
Home/Gorgias/Gorgias Klaviyo Integration
Gorgias + Klaviyo

Gorgias Klaviyo Integration: Three Ticket Events, the Tags on Them, and a Widget With Limits

A shopper writes in on Monday about a late order, and Tuesday's promo email reaches her anyway. The Klaviyo integration for Gorgias is built to stop that: it sends ticket events onto her Klaviyo profile, so a segment can hold her back until the ticket's resolved. It's a partner-built app, connected from Klaviyo's side, and it needs no code. The surprises are in timing, and in which tickets get to show Klaviyo data.

What syncs, and which way

Gorgias to Klaviyo: Opened ticket, Resolved ticket and Satisfaction survey responded, as events on the customer's profile. If there's no profile, one is created, but not subscribed. Ticket attributes such as tags travel with each event.

Klaviyo to Gorgias: SMS and WhatsApp conversations and low-star reviews as tickets, if you turn those on, plus a sidebar widget with the shopper's Klaviyo attributes.

The catch: that widget needs Klaviyo SMS or Klaviyo Reviews on the account, and it only appears on SMS and review tickets. Email and chat tickets don't show it.

Segments that miss the shoppers you meant

The tag went on after the event fired

How you'll know: A segment on a shipping-delay tag catches some tickets and not others.

Fix: Klaviyo reads tags at the moment a ticket is opened, resolved or surveyed. Tags added to a ticket that's already closed never reach it, and Gorgias warns tags added mid-ticket can be missed too. Have a Gorgias rule tag tickets as they're created.

The Klaviyo widget never appears

How you'll know: Agents can see Klaviyo data on SMS tickets, but email and chat tickets show nothing.

Fix: That's how the integration is built. Showing Klaviyo data on every ticket takes a Gorgias HTTP integration that calls Klaviyo's API, which is a custom build.

Suppliers and no-reply senders turn into Klaviyo profiles

How you'll know: Your Klaviyo account fills with vendor addresses and automated senders who once emailed support.

Fix: Every Gorgias contact creates a profile. Gorgias suggests auto-tagging tickets from real customers and building segments on that tag, so the rest never get marketing.

Two brands, and every customer lands in both Klaviyo accounts

How you'll know: A shopper of one brand gets the other brand's segments.

Fix: With two Klaviyo accounts on one Gorgias account, all customers go to both. Tag tickets by the store integration they came through and segment on that tag in each account.

Connecting Klaviyo to Gorgias

  1. 1

    Start in Gorgias and authorize

    Settings All apps Klaviyo Authorize

    You're taken to Klaviyo's settings. Log in if asked, then click Connect to Gorgias.

  2. 2

    Enter your helpdesk URL

    Use the yourdomain.gorgias.com form, the domain you see when you log in to Gorgias.

  3. 3

    Choose what Klaviyo sends back

    Tick Sync SMS Conversations, Sync Reviews (with the star rating that opens a ticket, 3 or below by default) and Sync customer profile information from Klaviyo to Gorgias for the widget. The last one only works if one of the first two is on.

  4. 4

    Authorize and complete setup

    From here, your Gorgias contacts create Klaviyo profiles and ticket events start arriving. Nobody is added to a list or subscribed; segments do that work.

    Watch for: a Klaviyo - DEPRECATED widget in your Gorgias integrations. That's the old integration, unsupported since March 15, 2022. Delete it and connect the current one.

When a tag is too blunt to segment on

Tags are as good as your rules. wrong-size tells Klaviyo the reason, not which product or which order, and a restock or fit email needs both. Gorgias's own article describes ticket attributes like tags reaching Klaviyo, not the order number or SKU the ticket was about.

n-frames builds two things on top of the integration rather than in place of it. One is a listener on ticket events that reads the order and product from the ticket and writes them onto the Klaviyo profile as properties through Klaviyo's API, so a flow can target "asked about the linen shirt, hasn't reordered". The other is a Gorgias HTTP integration that shows the shopper's last flows, campaigns and consent in the sidebar on email and chat tickets.

What the Gorgias Klaviyo app sends, and what it doesn't

Does Gorgias integrate with Klaviyo?

Yes. The partner-built Klaviyo app for Gorgias sends ticket-opened, ticket-resolved and survey-response events onto customer profiles. In the other direction it brings in Klaviyo SMS, WhatsApp and review tickets, and a sidebar widget of Klaviyo attributes on those tickets.

Can I trigger a Klaviyo flow when a Gorgias ticket closes?

Yes. Resolved ticket arrives in Klaviyo as an event, so it works as a flow trigger or a segment condition. A check-in after the fix, or a win-back for a poor survey score, are the common uses.

Does the Gorgias Klaviyo integration pass along what the ticket was about?

Partly. Tags on the ticket come across with each event, read at the moment it fires, so a well-tagged ticket tells Klaviyo the reason. The specific product or order number isn't described as part of the sync, so it needs a separate build if your flows depend on it.

Can Gorgias support multiple Shopify brands with one Klaviyo account?

Yes, by tagging tickets per store integration and building a segment for each brand in that Klaviyo account. If each brand has its own Klaviyo account, connecting them all to one Gorgias account sends every customer to each of them, so tags and segments matter even more.

Who builds the Gorgias and Klaviyo pieces the integration leaves out?

n-frames builds them: the ticket-event listener that puts the product and order on the Klaviyo profile, and the Gorgias sidebar widget that shows Klaviyo data on email and chat tickets, both working alongside the Klaviyo app you already have.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.