PIING
Reading Piing: AlertsSigned-in vs signed-out targeting
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
- Signed-in awareness is automatic
- The first-party pixel
- Intent score
- Identity stitching
- What signed-out visitors can and can't match
Search or browse documentation
Piing: Alerts 9 / 14
Signed-in vs signed-out targeting
How the first-party pixel tracks browse intent, computes intent scores, and stitches identity from signed-out click to signed-in purchase.
Piing: Alerts can target known customers and anonymous visitors from the same feed using first-party storefront signals. It does not rely on third-party advertising cookies.
Signed-in awareness is automatic
The storefront calls the feed through Shopify's app proxy, and Shopify appends the logged-in customer id to signed-in requests. Piing: Alerts reads it with no client-side work. That powers two audience modes in the notification editor:
- Signed-in customers only
- Signed-out visitors only
Signed-in visitors can use the customer fields cached for Alerts targeting, including tags, spend, VIP tier and location. See Segments.
The first-party pixel
Activate it under Settings, Activate web pixel. It also switches on automatically the first time you open the app. It runs as a Shopify web pixel and does two jobs:
- Browse intent: it records product views, collection views, searches, and add-to-cart events as lightweight browse history.
- Conversion assist: it reports
checkout_completed from the checkout pages, where theme code can't run, so purchases attribute even when they finish off-theme.
Why it matters: the pixel makes signed-out visitors targetable and closes the loop from click to purchase.
Intent score
From browse history, Piing: Alerts computes an intent score from 0 to 100. Recent views count most (a view today counts more than one last week), and an active cart adds a bump. It's deliberately simple, so a rule like Intent score at least 60 is easy to reason about.
Use behaviour fields in a rules segment to target signed-out visitors:
- Viewed product and Viewed collection, by handle
- Browse events (last 30d)
- Current cart value
- Intent score (0 to 100)
Identity stitching
The pixel keeps a first-party visitor id and links it across contexts: the anonymous visitor, Shopify's analytics client id, and the customer id once they sign in. So a shopper who clicks a card while signed out and buys while signed in is still credited to that card. See Analytics for attribution.
What signed-out visitors can and can't match
Behaviour fields work signed-out. Customer fields (tags, spend, VIP tier, city) come from the customer record and only apply once someone signs in. Build signed-out audiences on behaviour, and layer customer data on top for signed-in shoppers.
Related guides
Was this guide helpful?
Next guide in Piing: Alerts
Automations
Seven ready-made triggers for new drops, restocks, winbacks, VIP and store welcomes, sale reminders and browse follow-ups.
Still need a hand? Contact us