PIING
Reading Piing: AlertsAnalytics and suggestions
Piing: Alerts
- Getting started with Piing: Alerts
- Appearance and branding
- Create and manage notifications
- A/B testing
- Frequency capping and suppression
- AI notifications
- Web push
- Segments and audiences
- Signed-in vs signed-out targeting
- Automations
- Analytics and suggestions
- Integrations and data
- FAQ and troubleshooting
- Plans and billing
In this guide
- The KPI band
- The breakdowns
- How conversions attribute
- Suggestions
- Export
- When reporting starts
Search or browse documentation
Piing: Alerts 11 / 14
Analytics and suggestions
Follow the funnel from impressions to clicks to conversions and revenue, per notification and per segment, with plain-English suggestions.
Piing: Alerts reports the full funnel, from impressions to clicks to conversions to revenue, and breaks it down by notification and by segment. Open Analytics. Pick a range with the 7d / 30d / 90d toggle.
The page reads like Shopify's own reporting: a KPI band across the top, then charts and tables in two columns, so there is far less scrolling to find a number.
The KPI band
Four volume metrics, each with a day-by-day sparkline:
- Impressions: cards shown.
- Clicks: card and teaser clicks.
- Conversions: attributed orders.
- Revenue: attributed order value.
Then four derived numbers beneath them:
- Feed opens: times the bell was opened.
- Click-through rate: clicks over impressions.
- Conversion rate: conversions over clicks.
- Revenue per impression: what one served card is worth.
The breakdowns
- This week vs last: the last 7 days against the 7 before, independent of the range toggle.
- Funnel: impressions through to conversions in one view.
- By notification: every card's impressions, clicks, CTR, conversions, and revenue. CTR cells tint brighter as they climb, so winners stand out.
- Notification performance by audience.
- A/B tests, and teaser A/B tests: per-variant performance for any card running a split, with the winner marked. See A/B testing.
- Control-group lift.
- By audience: the same metrics per segment, with member counts.
- Notification x segment matrix: how each card performs inside each segment. Spot copy that lands with VIPs but flops with new visitors.
- Acquisition cohorts.
- Daily: impressions, clicks, conversions, and revenue by day.
How conversions attribute
A conversion links an order back to the card the shopper clicked. Piing: Alerts attributes two ways and dedupes by order id, so no order is double-counted:
- Server-side: the
orders/create webhook finds the shopper's most recent click inside the attribution window and credits that card and its segments.
- Pixel assist:
checkout_completed reports the order from checkout, where theme code can't run.
Attribution stitches signed-out clicks to signed-in purchases, so a card gets credit even when the shopper signs in between clicking and buying.
Attribution window
Setting your own window is a Growth and Scale feature. On those plans, set it under Settings, Attribution window (hours). The default is 72. An order counts as a conversion only if it lands within that many hours of the click.
Starter uses a fixed 72-hour window. Growth and Scale can keep 72 hours or set another window. See Plans and billing.
Suggestions
The dashboard turns your numbers into plain advice under What the numbers suggest. Each is one of:
- Copy: high impressions, low CTR. The copy isn't landing.
- Winner: a strong card worth amplifying.
- Freshness: a stale feed that needs new cards.
- Coverage: a segment with members but no targeted content.
- Scale it: a champion segment worth widening.
- Exposure: a card that should be a teaser.
Click Refresh insights to recompute, or Dismiss to clear one. Suggestions also refresh on the scheduled ops run.
Export
Notification and audience reporting tables can be exported as CSV for deeper analysis or a retailer's own reporting workflow. The export uses the current report context rather than presenting an unrelated lifetime total.
When reporting starts
Numbers begin the moment the feed goes live and visitors see the bell. An empty report means no impressions yet: confirm the widget is on under Appearance.
Related guides
Was this guide helpful?
Next guide in Piing: Alerts
Integrations and data
Sync Klaviyo and Ometria audiences, push captured signups, write consent to Shopify and understand the Alerts customer cache.
Still need a hand? Contact us