What we do
Tools
Industries
Department
How we workLet's talk →
Home/Drip
Drip

A Drip Integration for the Data Your Store App Never Sends

The Drip app for Shopify, or the Drip plugin for WooCommerce, brings in customers, orders, carts and browsing, and the workflows run on it. The loyalty tier held by another app doesn't come along. Neither do wholesale orders a rep enters in a different system, or the support ticket that makes this a bad week for a promotion. Those reach Drip through its API, each by a different route.

Where Drip stops

It can't see anything outside your store platform's data, and that's where the best automation ideas live.

Stuck on Drip? Let's solve it →

Which way into Drip each kind of data goes

Data you want Drip to act on Where it goes in Watch for
Shopify or WooCommerce customers, orders, carts and browsing Drip's Shopify app, or the Drip for WooCommerce plugin Already handled. Don't also send those same orders through the API.
Orders from a custom store, B2B portal or second channel The Shopper Activity API's order endpoint, with a provider name for that source Send refunds and cancellations as well, with refund_amount, so lifetime value comes back down.
Loyalty tier, wholesale flag, subscription status If your loyalty app has no Drip connector of its own: subscriber custom_fields or tags, updated when the other system changes Applying a new tier tag leaves the old one on. Remove it with remove_tags in the same update.
One-off moments: a ticket opened, a reward earned A custom event, sent with an action name and optional properties Fix the spelling of each action. A new spelling is a new action to Drip.
Drip activity that another system should know about Drip's webhooks, such as subscriber.applied_tag or subscriber.performed_custom_event A new webhook sends every event except received email unless you list the ones you want.

Loading past orders into Drip, worked through

Drip's batch endpoints take up to 1,000 records a call, and an account gets 50 batch calls an hour.

Example · a store loading 120,000 past orders
Past orders to load 120,000
Orders per batch call (Drip's batch maximum) ÷ 1,000
Batch calls needed 120
Batch calls allowed per hour ÷ 50
Time to load the history about 2.5 hours

Single requests are capped at 3,600 an hour. Read the X-RateLimit-Remaining header on each response rather than guessing where you are.

Drip workflows that miss the customer they were built for

Nobody enters the workflow

How you'll know: The API call to start subscribers on a workflow succeeds, and the workflow stays empty.

Fix: Drip doesn't add anyone to a workflow that isn't active. Turn it on before the integration starts sending people to it.

Lifetime value that only goes up

How you'll know: Customers who returned everything still qualify for VIP flows.

Fix: Send refunded and canceled order actions with refund_amount, not just placed.

Two tiers on one subscriber

How you'll know: A customer carries both the Silver and Gold tags, and gets both sets of emails.

Fix: Remove the old tier in the same update that adds the new one.

One moment, two triggers

How you'll know: Half the ticket events say 'Opened ticket' and half say 'Ticket opened'.

Fix: Drip can list every custom event action in the account. Run that list, then fix the name at the source.

Store orders counted twice

How you'll know: Revenue in Drip runs ahead of the store.

Fix: Only send orders the store app doesn't, under their own provider name.

A coffee subscription whose VIPs looked like everyone else

Premium coffee subscription · Drip for lifecycle email, loyalty in another app

Before

VIP workflows fired on order count alone, so loyalty members and wholesale accounts got the same messages as everyone else.

After

Loyalty tier and wholesale status now feed Drip's tags.

VIP and wholesale journeys fire on each customer's actual standing.

Drip, the product, and what plugs into it

Is 'Drip' the marketing tool the same thing as a drip campaign?

No. A drip campaign is any series of automated messages sent on a schedule or a trigger, and you can build one in nearly any email platform. Drip is a particular email marketing platform for online stores, at drip.com, that shares the name.

What is Drip used for?

Email marketing automation for online stores: a visual workflow builder, on-site behavior tracking, segments built from tags and custom fields, and campaigns that react to orders and carts.

Does Drip work with platforms other than Shopify?

Yes. There's a Drip for WooCommerce plugin, and Drip's API covers stores without an app: the Shopper Activity endpoints accept carts, orders and products from any source you name.

How is Drip different from Klaviyo or Omnisend?

All three are email platforms built for online stores, with workflows, behavior tracking and store data at the center. The real differences are price, how deep segmentation and reporting go, and how many apps connect to each. Compare them against your own store, since all three change plans and features often. Our Klaviyo and Omnisend pages cover those two.

Who builds a Drip integration for data the store app leaves out?

n-frames builds them: loyalty and wholesale fields written onto subscribers, orders from other channels sent through the Shopper Activity API, custom events from a help desk, and webhooks that carry Drip activity back to the CRM.

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.