Privy helps Shopify stores capture more emails and recover carts. This guide covers popup setup and optimization for maximum list growth.
Privy Popups
Why Privy?
Related: Shopify Omnisend Integration: Email & SMS Marketing (2025), Shopify Mailchimp Integration: Complete Email Marketing Guide (2025), Free Favicon Converter.
List-building specialist:
| Feature | Benefit |
|---|---|
| Exit intent | Capture leaving visitors |
| Spin-to-win | Gamified capture |
| Cart saver | Reduce abandonment |
| A/B testing | Optimize conversion |
| Targeting | Show to right people |
Impact on stores:
- 3-5% average popup conversion
- 10-15% cart recovery rate
- Rapid list growth
- More sales from email
Privy Pricing
Related: the Klaviyo connector, Stamped Products, Shopify Seguno Integration: Email Marketing Guide (2025).
| Plan | Contacts | Price |
|---|---|---|
| Free | 100 | $0/mo |
| Starter | 1,500 | $30/mo |
| Growth | 3,000 | $45/mo |
| Growth | 6,000 | $60/mo |
| Growth | 10,000 | $75/mo |
Included in all paid plans:
- Unlimited popups
- Cart abandonment
- Email campaigns
- A/B testing
- Advanced targeting
Getting Started
Related: Fera integration, connect Shopify with Loox, the Rebuy connector.
Step 1: Install Privy
- Go to Shopify App Store
- Search “Privy”
- Click Add app
- Authorize access
- Complete setup wizard
Step 2: Create First Popup
- Click Create New Display
- Choose popup type
- Select template
- Customize design
- Set display rules
- Publish
Step 3: Connect Email
Options:
- Use Privy Email (built-in)
- Connect Klaviyo
- Connect Mailchimp
- Other integrations
Step 4: Set Display Rules
Configure when popups show:
- Timing triggers
- Page targeting
- Visitor targeting
- Mobile/desktop
Popup Types
Exit Intent Popup
Trigger: Mouse moves to close/leave
Best for: Email capture
Offer: 10-15% discount
Conversion: 3-5%
Setup:
- Enable exit intent trigger
- Desktop and mobile options
- Test on various devices
Timed Popup
| Timing | Use Case |
|---|---|
| 3-5 seconds | Quick offer |
| 10-15 seconds | Engaged visitors |
| 30+ seconds | Deep readers |
Scroll Popup
Trigger by scroll depth:
- 25%: Quick engagement
- 50%: Medium interest
- 75%: Highly engaged
Spin-to-Win
Gamified email capture:
- Wheel with prizes
- Higher engagement
- Fun user experience
- Configure prize odds
Prize examples:
- 10% off (high probability)
- 15% off (medium)
- 20% off (low)
- Free shipping (medium)
Flyout
Subtle sidebar popup:
- Less intrusive
- Good for mobile
- Persistent display
- Chat-like appearance
Announcement Bar
Top-of-page bar:
- Sitewide messaging
- Promotions
- Free shipping threshold
- Countdown timers
Cart Saver Popup
How It Works
Cart abandonment flow:
├── Visitor adds to cart
├── Starts to leave
├── Exit intent detected
├── Cart saver popup appears
├── Offer discount to complete
└── Email captured for follow-up
Configuration
| Setting | Recommendation |
|---|---|
| Trigger | Exit intent |
| Minimum cart | $30+ |
| Discount | 10% or free shipping |
| Email required | Yes |
Follow-Up Emails
After cart saver capture:
- Immediate: Cart reminder
- 1 hour: Urgency
- 24 hours: Final reminder
Targeting Options
Page Targeting
| Target | Use Case |
|---|---|
| All pages | General capture |
| Homepage only | Welcome offer |
| Product pages | Product-specific |
| Cart page | Cart abandonment |
| Exclude checkout | Don’t interrupt |
Visitor Targeting
| Segment | Strategy |
|---|---|
| New visitors | Welcome popup |
| Returning | Different offer |
| Non-subscribers | Capture popup |
| Subscribers | Skip popup |
Device Targeting
Configure per device:
- Desktop: Full popup
- Mobile: Flyout or bar
- Tablet: Adapted design
Geographic Targeting
By location:
- Country-specific offers
- Language-based popups
- Regional promotions
Design Best Practices
Popup Design
| Element | Best Practice |
|---|---|
| Headline | Clear, compelling |
| Image | Brand-relevant |
| Form | Minimal fields |
| Button | Action-oriented |
| Colors | Brand consistent |
Mobile Optimization
Mobile requirements:
- Full-screen or flyout
- Large tap targets
- Fast loading
- Easy to close
Copy Guidelines
Effective popup copy:
- Clear value proposition
- Urgency (limited time)
- Specific discount
- Minimal text
A/B Testing
What to Test
| Element | Test Ideas |
|---|---|
| Headline | Different value props |
| Discount | 10% vs 15% |
| Image | Product vs lifestyle |
| Timing | 5s vs 10s |
| Format | Popup vs flyout |
Running Tests
- Create variation
- Split traffic 50/50
- Run for statistical significance
- Pick winner
- Continue testing
Email Campaigns
Built-in Email
Privy includes:
- Welcome series
- Cart abandonment
- Win-back campaigns
- Newsletters
- Automation flows
Welcome Series
Welcome automation:
├── Immediate: Welcome + coupon
├── Day 3: Best sellers
├── Day 7: Social proof
└── Day 14: Last chance for coupon
Cart Abandonment
| Timing | Content | |
|---|---|---|
| 1 | 1 hour | Reminder |
| 2 | 24 hours | Urgency |
| 3 | 72 hours | Final offer |
Integration Options
Email Platforms
| Platform | Integration |
|---|---|
| Klaviyo | Native sync |
| Mailchimp | Native sync |
| Omnisend | Native sync |
| ActiveCampaign | Zapier |
SMS
| Platform | Integration |
|---|---|
| Postscript | Native |
| SMSBump | Native |
| Attentive | Zapier |
Data Flow
Privy captures email
→ Syncs to Klaviyo
→ Tags with source
→ Enters welcome flow
→ Receives campaigns
Analytics
Key Metrics
| Metric | Benchmark |
|---|---|
| Popup views | Track volume |
| Conversion rate | 3-5% |
| Email signups | Track growth |
| Revenue attributed | Track impact |
Reports
Available in Privy:
- Display performance
- Email metrics
- Revenue attribution
- A/B test results
Troubleshooting
Popup Not Showing
Causes:
- Display rules too strict
- Already shown to visitor
- Page excluded
- JavaScript blocked
Solutions:
- Check display rules
- Clear cookies/test incognito
- Verify page targeting
- Check for conflicts
Low Conversion Rate
Causes:
- Poor offer
- Bad timing
- Design issues
- Wrong targeting
Solutions:
- Improve offer value
- Adjust timing
- Redesign popup
- Refine targeting
Privy vs Alternatives
| Feature | Privy | Justuno | OptinMonster |
|---|---|---|---|
| Free plan | Yes | Yes | No |
| Shopify native | Yes | Yes | Via app |
| Built-in email | Yes | Limited | No |
| Spin-to-win | Yes | Yes | Yes |
| Best for | SMB Shopify | Enterprise | WordPress |
Best Practices
List Building
- Offer real value
- Keep forms simple
- Mobile-optimize
- A/B test constantly
Popup Strategy
- Don’t interrupt checkout
- Respect visitor experience
- Show once per session
- Target appropriately
Conversion Optimization
- Test different offers
- Use urgency wisely
- Match brand voice
- Track and iterate
2025 Snapshot
Quick benchmarks for the Privy workflow. Use these as planning ranges, then validate against your own data.
| Data point | 2024 | 2025 | Why it matters |
|---|---|---|---|
| Typical core flow setup (welcome + abandoned cart) | 30–60 min | 20–45 min | Estimates time-to-first-value |
| Abandoned cart recovery benchmark | 5–10% | 5–15% | Sets realistic expectations for automation revenue |
| Email ROI benchmark (industry) | ~$36 per $1 | ~$36–$42+ per $1 | Useful for budgeting and vendor comparisons |
| Recommended cadence (SMB) | 1–2 emails/week | 2–4 emails/week | Balances revenue vs list fatigue |
Practical Implementation Notes
Data sync and ownership
Most Shopify integrations follow the same lifecycle: a one‑time historical import (customers, products, orders) followed by ongoing incremental updates via API/webhooks. In practice, the biggest failures come from identity and mapping—not from missing features. Before you activate anything customer‑facing, decide which system is the source of truth for customer identity (email vs phone), consent flags, segmentation, and lifecycle fields.
Treat the first week as a controlled rollout. Start with a small segment (internal addresses or a low‑risk cohort), validate that events fire exactly once, and then scale automation volume. This approach prevents silent double‑sending, broken attribution, and hard‑to‑debug “it looks connected but nothing happens” situations.
QA checklist (run once, then reuse)
Use a seed dataset (test customers, a few SKUs, a low‑value test order) to run an end‑to‑end path: signup → first purchase → fulfillment → refund. Confirm that reporting matches your store’s order IDs and timestamps.
Operational checks:
- App permissions/scopes match the features you actually use
- Timezone aligns across scheduled sends, reporting windows, and dashboards
- Edge cases are represented correctly (partial refunds, cancellations, multi‑location fulfillments)
- Baselines are captured so you can measure lift after go‑live
Marketing workflow notes
For email/SMS platforms, prioritize two flows first: welcome and abandoned checkout/cart. Keep early versions simple (one goal per message) and add segmentation only after you’ve validated tracking. A practical sequence is: welcome → abandon → post‑purchase education → win‑back.
Decisions that avoid painful rework:
- Frequency caps per channel (and quiet hours for SMS)
- Consent collection and proof (opt‑in method, opt‑out handling, suppression lists)
- Discount strategy (one‑time codes, expiry windows, exclusions for already‑discounted items)
- Attribution rules (what counts as “assisted” vs “last click”)
Next Steps
After setup:
- Create exit intent - Email capture popup
- Set up cart saver - Reduce abandonment
- Connect email - Klaviyo or built-in
- Configure targeting - Right popups to right people
- A/B test - Optimize continuously
Shopify + Privy implementation checklist (2025)
This section adds practical “make it stable” steps you can use after you install the app/connector. It’s intentionally lightweight: the goal is fewer sync surprises, cleaner reporting, and easier troubleshooting.
1) Quick setup checklist
- Permissions first: grant only the scopes you need (orders/customers/products as required) and document who owns the admin credentials.
- Data mapping: confirm how email, phone, currency, and SKU are mapped between Shopify and Privy.
- Historical import: decide how far back to import orders/customers (avoid importing years of data if you don’t need it).
- Deduplication rules: pick one unique identifier per object (usually email for customers, order ID for orders) to prevent doubles.
- Alerts: set a lightweight alert path (email/Slack) for failed syncs, auth expiry, and API rate limits.
2) Data you should verify after connecting
Most integration issues show up in the first hour if you test the right things. Use the table below as a QA checklist (create a test order if needed).
| Data object | What to check | Why it matters |
|---|---|---|
| Customers | Email/phone format, marketing consent fields, duplicates | Prevents double messaging and broken segmentation |
| Orders | Order total, tax, discount, shipping, currency | Keeps revenue reporting and automation triggers accurate |
| Line items | SKU, variant ID, quantity, refunds/returns behavior | Avoids inventory and attribution mismatches |
| Fulfillment | Status changes + timestamps, tracking numbers, carrier fields | Drives customer notifications and post-purchase flows |
| Catalog | Product titles, handles, images, collections/tags | Ensures personalization and reporting match your storefront |
3) Automation ideas for Marketing
- Welcome series: new subscriber → educational sequence + first-purchase offer in Privy.
- Abandoned cart: cart started but not purchased → reminder email/SMS from Privy (timing based on your AOV).
- Post-purchase: order created → delivery/usage tips + cross-sell for complementary products in Privy.
- Win-back: no purchase in 60–90 days → reactivation campaign using Privy segments.
- VIP: customer hits LTV threshold → move into VIP tier and trigger perks via Privy.
API sanity check (Shopify Admin API)
If your integration UI says “connected” but data isn’t flowing, a quick API call helps confirm whether the store is accessible and returning the objects you expect.
# List the 5 most recent orders (GraphQL)
curl -X POST "https://your-store.myshopify.com/admin/api/2025-01/graphql.json" \
-H "X-Shopify-Access-Token: $SHOPIFY_ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d "{\"query\":\"{ orders(first: 5, sortKey: CREATED_AT, reverse: true) { edges { node { id name createdAt totalPriceSet { shopMoney { amount currencyCode } } customer { email } } } } }\"}"Tip: keep tokens/keys in environment variables, and test in a staging store/site before rolling changes to production.
4) KPIs to monitor (so you catch problems early)
- Sync freshness: how long it takes for a new order/customer event to appear in Privy.
- Error rate: failed syncs per day (and which object types fail most).
- Duplicates: number of merged/duplicate contacts or orders created by mapping mistakes.
- Revenue parity: weekly spot-check that Shopify totals match downstream reporting (especially after refunds).
- Attribution sanity: confirm that key events (purchase, refund, subscription) are tracked consistently.
5) A simple 30-day optimization plan
- Week 1: connect + map fields, then validate with 5–10 real orders/customers.
- Week 2: enable 1–2 automations and measure baseline KPIs (conversion, AOV, repeat rate).
- Week 3: tighten segmentation/rules (exclude recent buyers, add VIP thresholds, handle edge cases).
- Week 4: document the setup, create an “owner” checklist, and set a recurring monthly audit.
Related integration guides
More marketing tools: Klaviyo email automation, Mailchimp integration, HubSpot integration.
Sources
For email marketing, see Klaviyo integration. For SMS, check SMS marketing integration.