PIING
Reading Piing: AlertsIntegrations and data
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
- Klaviyo audience sync
- Ometria audience sync
- How members are matched
- Capture to Shopify
- Push captured signups to a list
- Customer cache
- Product permissions
- Deletion and retention
- Next steps
Search or browse documentation
Piing: Alerts 12 / 14
Integrations and data
Sync Klaviyo and Ometria audiences, push captured signups, write consent to Shopify and understand the Alerts customer cache.
Piing: Alerts is Shopify-only. Shopify remains the customer and order record, while Alerts stores the customer cache, segment membership, first-party engagement and attribution records needed to render and measure the feed.
Klaviyo audience sync
- Create a Klaviyo private API key with the profile and segment read access required by the connection.
- In Alerts Settings, add the key and test the connection.
- Save the connection.
- Under Audiences, create a Klaviyo-synced segment and choose the external segment.
- Run Sync now and confirm the expected member count.
Alerts can also receive signed membership updates from a configured Klaviyo flow webhook, reducing the need to wait for the next scheduled sync.
Ometria audience sync
- Create an Ometria API key with contact and segment access.
- Add it in Alerts Settings and test the connection.
- Create an Ometria-synced audience.
- Run Sync now and validate membership.
Ometria endpoints can be configured where an account uses different paths. Confirm the correct API version for the retailer.
How members are matched
A synced Klaviyo profile or Ometria contact is matched to the relevant Shopify customer using the external identifier, with email as the documented fallback against the Alerts customer cache. Synced membership applies when the storefront request resolves the signed-in Shopify customer.
Capture to Shopify
An in-feed form can create or update a Shopify customer, set email marketing consent and add the merchant's chosen tag. The form can optionally collect first name and phone. SMS consent is only set when the shopper actively ticks the merchant's SMS consent line and supplies a valid phone number.
Klaviyo, Ometria and Attentive can then receive the Shopify customer through their normal Shopify routes.
Push captured signups to a list
A notification can additionally push its captured signups directly to selected Klaviyo or Ometria lists. The notification can use the store default, choose specific lists, or keep the direct push off. The Shopify customer and consent record are still created when direct list push is off.
Delivery failures should not silently undo the Shopify capture. Review the integration status and logs for the external list delivery.
Customer cache
Alerts caches the Shopify customer fields needed for fast audience evaluation, including relevant tags, metafields, spend, location and VIP tier. The initial customer load can be extended with the documented backfill control, and Shopify customer and order webhooks keep the cache current.
The cache is a product data store and should be treated accordingly in the merchant's privacy and retention review. It is not accurate to claim that all customer data stays only in Shopify.
Product permissions
The app uses Shopify access appropriate to the enabled features:
- customers for capture and customer-aware audiences;
- orders for attribution;
- products for product-driven cards and automations;
- Shopify pixel and customer-event capabilities for first-party behaviour and checkout signals;
- theme app extension capabilities for the feed.
The exact Shopify approval screen is the source for the scopes requested by the installed version.
Deletion and retention
Uninstall, subscription cancellation and data deletion are separate events. Alerts handles Shopify customer and shop deletion routes and removes or retains operational records according to the product's documented retention and legal requirements. Do not assume every event already delivered to Shopify, Klaviyo or Ometria is deleted from those systems when Alerts is removed. See Security.
Next steps
Related guides
Was this guide helpful?
Next guide in Piing: Alerts
FAQ and troubleshooting
Fixes for the most common questions, from the bell not showing and events not tracking to conversions not attributing.
Still need a hand? Contact us