LoginSign Up
← Back to all sparks
P

Privy

MARKETING
Velocity6.3

Privy keeps bolting integrations onto Flows until it stops being a popup tool.

ecommercelifecycle-marketingflow-automationintegrationssmssegmentation
◆Current state
Privy is an ecommerce email/SMS platform for Shopify and BigCommerce merchants, and the last four months read as one continuous project: make Flows the place where every other app's data lands. Reviews (Judge.me, Junip), loyalty (Rivo, Yotpo), subscriptions (Recharge), support (Gorgias), and signup data (Alia) all now sync into contact properties that can trigger, split, and personalize a Flow. The builder itself has grown the plumbing to match — tag actions, contact-update nodes, exit conditions, Flow-completed triggers, and date-based triggers for birthdays and renewals.
◆Where it's heading
The arc is from lead capture toward full lifecycle automation, and the tell is what got built last: checkout abandonment closed the last obvious gap in the owned-channel funnel, and Facebook Custom Audiences pushed Privy outside owned channels entirely. Integrations have shifted from one-way imports to bidirectional sync — SMS consent flows back from Shopify, replies flow out to Gorgias, segment membership flows out to Meta. Each release adds another data source that only pays off if merchants build the Flows, so the product is compounding on adoption of the builder rather than on new surfaces.
◆Prediction
Expect more outbound destinations for segments now that the Facebook connection proved the pattern — Google or TikTok audiences are the obvious next targets. On the Flow side, the recent triggers all key off external events, so the gap left is a way to author across them without wiring each Flow by hand.

◆Recent moves

  1. 15d ago

    Checkout Abandonment and New Asset Manager

    Checkout abandonment was the last missing trigger in Privy's abandonment ladder, and it arrives with exit conditions so browse and cart Flows hand off cleanly instead of double-messaging. The brand asset gallery is housekeeping for merchants who have accumulated images across Displays and campaigns.

    View source ↗
  2. 1mo ago

    Facebook Custom Audiences, Flow Completed Triggers, and Redesigned Settings

    ⚡ SPARK

    This is the first release where Privy data leaves the platform for a channel Privy does not own. Segments now sync to Facebook for retargeting and lookalikes, while the Flow Completed trigger lets merchants chain journeys instead of maintaining one long Flow.

    View source ↗
  3. 1mo ago

    Dynamic Product Blocks in Campaigns and Improved Contact Management Tools

    Dynamic product blocks graduate from Flow emails to campaigns, so one-off sends get the same recommendation logic as automated ones. The bulk contact actions and Flow-based contact updates are the list-hygiene layer that a growing Flow library demands.

    View source ↗
  4. 2mo ago

    Gorgias & Alia Integrations, SMS Single Opt-In, and Improved Reporting

    Gorgias routing turns inbound SMS replies into support tickets, which is Privy conceding that a two-way SMS channel needs a real inbox behind it rather than one of its own. Alia adds another signup-data source to the growing pile that feeds segments and Flows.

    View source ↗
  5. 2mo ago

    Judge.me Integration, Smarter Product Blocks, and Better Flow Control

    Judge.me brings review data into the same shape as every other integration in this stretch — contact properties, Flow triggers, and Split node branching. Best Selling and Most Viewed product blocks extend the recommendation logic that later reached campaigns.

    View source ↗
  6. 3mo ago

    Recharge Integration

    Recharge subscription data lands as contact properties and Flow triggers, giving subscription merchants churn and renewal messaging without exporting lists. It follows the same integration template as Junip and Rivo before it: sync the customer, expose the properties, trigger the Flow.

    View source ↗