Privy
Privy integration

Privy in Polar: the revenue it really drove, counted once.

Privy attributes an order to itself whenever it can, so its revenue overlaps with what ads, organic and SMS also claim. Add it up and you have more revenue than you made. Polar re-attributes campaigns and flows against your real orders, so the channel's actual share shows, next to every other one.

/

Retention revenue, re-attributed and counted once.

Campaigns, flows and subscriber growth from Privy, re-attributed against your real orders, so the channel's true share of revenue shows without double-counting the conversions paid and organic also claim.
Campaigns
"What did the send actually make?"
Campaign revenue re-attributed against your orders, counted once.
attributed
Flows & automations
"Which flows carry the channel?"
Automation revenue separated from broadcast, per flow.
flow vs campaign
Engagement to revenue
"Opens don't pay the bills."
Opens, clicks and sends read against orders and AOV.
clicks to orders
List growth
"Is the list worth anything?"
Subscriber growth tied to the revenue it eventually produced.
growth with revenue
Discount cost
"We bought that revenue."
The discount behind each campaign, and what it left in margin.
margin, not revenue
One P&L
"Retention sits in a silo."
Email and SMS next to paid, organic and marketplaces on one statement.
in the P&L
Setup Guide

How to Connect Privy to Polar.

A Polar account with Shopify connected, admin on your Privy account, and Polar's AI Data Engineer, which builds the connector from a plain-language request.
Polar

A Polar account with Shopify

A Polar account with Shopify connected. Privy data only means something read against the orders behind it.

Connect your data →
Privy

Your Privy account

Admin access to Privy, with the campaign, flow and subscriber reporting for the accounts you send from.

Open Privy →

Polar's AI Data Engineer

No native Privy connector yet? Describe what you need in plain language and the AI Data Engineer reads the Privy API, writes the connector and pipes it into your warehouse, in minutes.

1

Ask for the connector ~ minutes

Plain language, no code.
Tell Polar's AI Data Engineer what you want from Privy in plain language. It reads the source documentation, lays out everything the API offers by category, then writes the connector and pipes the data into your warehouse as governed data. No code, and it ships in minutes.
Worth knowing: this also works on connectors you already have. If the Privy API exposes a field, you can have it, down to a single hidden one the standard connector never pulled.
2

Re-attributed, not re-claimed automatic

Counted once.
Polar matches Privy sends and clicks to your Shopify orders and re-attributes the revenue on its own model, so the channel is not credited with orders that paid social and organic also claim.
3

Read against margin the payoff

Engagement, priced.
Campaigns and flows sit next to AOV, discount cost and contribution margin, so a campaign that drove revenue on a heavy discount is visible as what it was.
Get started

Count retention revenue once, not twice.

Bring Privy in, re-attribute it against your real orders, and read it next to paid, organic and everything else.

Side by side

Privy claims the order. Polar decides whether it earned it.

Privy attributes an order to itself whenever it touched the customer, so its revenue overlaps with what paid and organic also claim. Add every platform up and you have more revenue than you made. Polar re-attributes against real orders, once.
Privy

Privy on its ownon its own

Privy+

Privy with Polarblended

Revenue is the platform's own attribution.
Campaign and flow revenue re-attributed, counted once.
Opens and clicks with no line through to margin.
Engagement read against orders, AOV and contribution margin.
The discount behind a campaign is invisible.
Revenue shown after the discount that bought it.
Nothing compares retention to paid on equal terms.
Email and SMS beside every channel, on one attribution.
The Gap

The connector is only half of it.

Once Privy is modelled against your real orders inside Polar, you can use the result wherever you already work. Ask Polar in plain language, pull it live through the Polar MCP, or schedule it into the report your team reads every morning.
Privy

Privy

campaigns, flows, subscribers
Polar

Polar

clean, blended, attributed

Ask Polar

Polar MCP

Scheduled reports

Featured Use Case

What the channel actually earned.

Every platform claims the orders it touched. Polar decides which ones it caused, and prices them after the discount that bought them.
P Attributed retention revenue Illustrative
Metric
This week
WoW
Net revenue
$482,100
+6%
Orders
3,240
+4%
Blended CAC
$38
-9%
New vs repeat
42 / 58
-3pts
Email revenue
$71,400
+12%
Platform-claimed against Polar-attributed, per campaign. Illustrative figures.

Counted once

Attributed

The platform claims every order it can touch. Polar decides which orders it actually caused, so the channel's share adds up to a hundred percent across your stack.

After the discount

No SQL

A campaign that drove revenue on thirty percent off is a different result from one that drove it at full price, and the margin line says which.

Your Prompt Library

15 prompts a connected Privy unlocks.

Attributed campaign revenue, flow performance, discount cost and list value.
Type
Audience
15 of 15
Get started · connect once · counted once

Privy claimed the order. Polar decides whether it earned it.

Bring campaigns, flows and subscribers into Polar, re-attribute them against real orders, and read retention next to every other channel.

Phase 1 ~5 minConnect your data in PolarConnect Shopify and your stack. Polar's semantic layer turns it into governed metrics, then wait for the first sync.
Phase 2 ~ minutesBring Privy inDescribe what you need in plain language; the AI Data Engineer writes the connector and pipes it into your warehouse.
Phase 3 the payoffRead it counted onceRetention revenue re-attributed, next to paid and organic on one P&L.