Using RevLogic

Build Klaviyo segments from RevLogic statuses

How RevLogic's status tags reach Klaviyo, the segments worth building, and how to keep automated marketing off your key accounts.

RevLogic works out which of your customers are key accounts, which are drifting into winback, and whose spend is going up or down. If you send email from Klaviyo, you can use those same statuses there — to build a segment, or, more usefully, to keep automated email away from the accounts your sales team is already phoning.

First, check which route you’re on. There are two ways RevLogic’s intelligence reaches Klaviyo, and you should use one of them, not both:

  • If you’ve connected Klaviyo in RevLogic Settings, segment on the revlogic_* profile properties instead of on tags. They’re richer and they arrive faster — see RevLogic properties in Klaviyo. Stop reading here.
  • If you haven’t connected Klaviyo, this article is your route. The bridge is the Shopify customer tag: nothing to install, nothing to connect on RevLogic’s side.

Don’t build segments on both. A tag-based segment and a property-based segment will disagree with each other for a few minutes at a time whenever one updates before the other, and you’ll spend your time working out which is right instead of calling anybody.

How the connection works

RevLogic can keep a tag on the Shopify customer record for each status:

StatusTag
Key accountRevLogic Key Account
GrowingRevLogic Growing
ShrinkingRevLogic Shrinking
WinbackRevLogic Winback

Klaviyo’s own Shopify integration syncs customer tags one way — Shopify to Klaviyo — in near real time, and drops them into a profile property called Shopify Tags. So once RevLogic maintains a tag in Shopify, Klaviyo can segment on it without any extra work.

Two things follow from it being one-way. Editing Shopify Tags inside Klaviyo changes nothing in Shopify and gets overwritten on the next sync. And Klaviyo does not sync Shopify customer metafields, so the revlogic.* values described in RevLogic in Shopify Analytics are for Shopify’s own reports, not for Klaviyo. Tags are the route into Klaviyo.

Turn on the tags you need

Each tag has its own switch in RevLogic Settings, and each is off until you turn it on:

  • Winback tag in Shopify — the RevLogic Winback tag.
  • Status tags in Shopify — key account, growing, and shrinking.

Turn on only the ones your email platform actually segments on. Switching one on asks you to confirm first, then tags everyone who currently qualifies in one background pass — and turning it off again removes the tag from every customer RevLogic put it on. RevLogic only ever removes the tag it applied, so a tag one of your team added by hand with the same spelling is never stripped.

Full detail on the statuses themselves is in Customer statuses and key accounts and Churn risk and winback.

A segment of your key accounts

In Klaviyo:

  1. Go to Lists & Segments and choose Create segment.
  2. For the condition, pick Properties about someone.
  3. Choose the Shopify Tags property.
  4. Set the operator to contains and the value to RevLogic Key Account.

Save it. The segment stays current on its own as RevLogic adds and removes the tag.

Keeping marketing off your key accounts

This is the reason most teams turn the key-account tag on, and it works the other way round from a normal segment: you want these people out of the send, not in it.

Add a flow filter to your automated flows — or the same condition on the campaign segment:

  • Shopify Tags → doesn’t contain → RevLogic Key Account

Now your automated email skips your most important accounts and a salesperson calls them instead. Nothing costs more goodwill than a generic discount email landing on an account your sales team is mid-negotiation with.

If your sales team owns winback calls too, add the same exclusion for RevLogic Winback.

A light-touch winback segment

If you’d rather your winback customers get an email as well as a call, build the segment the same way — Shopify Tags contains RevLogic Winback — and keep the message light, so it supports the call rather than competing with it.

This one clears itself: when a winback customer places an order, RevLogic removes the tag and they drop out of the segment. Nobody who has just ordered keeps receiving “we miss you” email.

Growing and shrinking

Two more worth a flow each:

  • Shopify Tags contains RevLogic Shrinking — a check-in email while there’s still time to ask what changed.
  • Shopify Tags contains RevLogic Growing — the audience for a new-range or new-line announcement, because these accounts are already buying more.

What to expect

  • Timing. Setting a customer’s key-account state by hand — to Always or to Never — reaches the tag within a few minutes, in both directions: Never removes RevLogic Key Account from a customer who would otherwise qualify. Changing your key-account thresholds in Settings lands within a few minutes too. Everything else rides RevLogic’s regular passes — in practice the same day, not instantly — and a customer keeps a tag until the next pass removes it, so build flows that can tolerate a few hours’ lag either way.
  • Your key-account segment includes accounts with no recent orders. A customer set to Always carries the tag even when their last order predates your lookback window — often exactly the account you most want held back from automated email. They will have little or no other RevLogic data attached, so don’t build a flow that assumes a recent order date.
  • A tag is a signal, not a score. Tags filter; they don’t rank. Klaviyo can tell you who is a key account, not who your top ten are. RevLogic’s own Customers and Winback pages are where you get them ordered by value.
  • One contact, one profile. If a business buys through a single purchasing contact, the tag sits on that contact’s record — so it describes the contact you email, not each individual buyer behind them.

One footnote for the technically minded: RevLogic can also write values straight into Klaviyo as profile properties, which is the connected route described in RevLogic properties in Klaviyo. Tags are the supported path for stores that haven’t connected.

Next steps