PIING
Reading Piing: AlertsFAQ and troubleshooting
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 bell isn't showing on my storefront
- Events aren't tracking
- Conversions aren't attributing
- A segment shows zero members
- AI copy is greyed out
- Klaviyo or Ometria shows no segments
- A notification won't appear for a specific visitor
- Do I need to touch theme code?
- Where do I change the widget's colours and layout?
- Could the closed feed sit over my page?
Search or browse documentation
Piing: Alerts 13 / 14
FAQ and troubleshooting
Fixes for the most common questions, from the bell not showing and events not tracking to conversions not attributing.
The bell isn't showing on my storefront
Work through these in order:
- Is the embed on? Theme editor, App embeds, switch on Piing: Alerts, then Save. This is required once.
- Is the feed empty? If Hide bell when feed is empty is on under Appearance and the visitor matches no notifications, the bell hides by design. Publish a notification targeted at Everyone to test.
- Floating when you expected it in the header? Placement is set in the theme editor, under App embeds then Piing: Alerts. If auto-detection cannot find your header's icon row, or a custom selector doesn't match, the bell falls back to a floating corner button. Recheck the selector there. See Appearance.
- Right theme? Confirm you enabled the embed on your live theme, not a draft.
Events aren't tracking
- Pixel active? Open Settings, Tracking and attribution, and confirm the pixel active badge. If not, click Activate web pixel.
- Give it a page view. Browse intent records on product, collection, search, and add-to-cart events. Load a product page, then check Analytics.
- Ad blockers. Aggressive blockers can drop pixel calls for some visitors. Widget events flow through the app proxy on your own domain and are more resilient.
Conversions aren't attributing
- Was there a click? A conversion links to a prior card click. Impressions alone don't attribute.
- Inside the window? Only orders within the attribution window after the click count. Starter uses a fixed 72-hour window. Growth and Scale start at 72 hours and can set another window under Settings. See Plans and billing.
- Signed out, then in? Stitching credits a signed-out click to a signed-in purchase, but it has to be the same visitor. A different device or cleared browser storage can break the link.
A segment shows zero members
- Rules segments show live counts once customer data is cached. Run Backfill customers in Settings if you just installed.
- Too strict? Switch Match ALL to Match ANY, or loosen a condition. Behaviour conditions (viewed product, intent score) only populate once the pixel has seen activity.
- Synced segments need a Sync now on the Audiences list after you save them.
AI copy is greyed out
Open Settings, AI, and tick Enable AI-generated notification copy for automations. AI copy is metered by plan. If you've used your monthly allowance, automations fall back to their templates. See AI notifications.
Klaviyo or Ometria shows no segments
- Test the key. Settings, Test connection. A failure means the key is wrong or lacks read access to segments and profiles.
- Ometria endpoints. Some plans expose different API paths. See Integrations.
A notification won't appear for a specific visitor
- Audience. Check the card's audience mode. Signed-in-only cards never show to signed-out visitors, and the reverse.
- Segments. If it targets segments, the visitor has to match at least one.
- Schedule. Before Starts it's scheduled. After Ends it's ended. Both keep it out of the feed.
- Frequency caps. If the visitor converted on it, hit its impression cap, or is inside its cooldown, it's suppressed on purpose. See Frequency capping.
Do I need to touch theme code?
No. Enabling the app embed once is the only theme step. Content, targeting, and styling all ship from the admin with the feed.
Where do I change the widget's colours and layout?
Appearance for colours, copy and how the feed opens, as a drawer, popover or modal on desktop and a full-screen or bottom sheet on mobile. Changes go live on Save. Where the bell sits is set in the theme editor, under App embeds then Piing: Alerts.
Could the closed feed sit over my page?
No. The panel is drawn in its correct closed state before it enters the page, and it ignores clicks while closed, so it cannot cover your content or swallow taps.
Related guides
Was this guide helpful?
Next guide in Piing: Alerts
Plans and billing
Three plans billed through Shopify, with a 14-day trial for new subscribers. What each plan includes, what needs a plan, and how to cancel.
Still need a hand? Contact us