PIING
Reading Piing: IntelligenceWhere your data goes
Piing: Intelligence
- How Intelligence works
- The fields it writes
- Profile refreshes and legacy units
- Preview your profiles
- Custom fields and prompts
- The storefront pixel
- Run and schedule analyses
- Where your data goes
In this guide
- Profiles live in Shopify metafields
- Your CRM and tools pick them up
- What the app stores, and what it does not
- A note on the storefront pixel
- Next steps
Search or browse documentation
Piing: Intelligence 8 / 8
Where your data goes
The Intelligence data path from Shopify orders and optional pixel signals to AI processing, output controls and app-owned Shopify metafields.
Piing: Intelligence keeps Shopify as the primary customer record. Selected profile values are written back to Shopify metafields, while the app retains the configuration, run, optional pixel and operational records needed to provide the service.
Profiles live in Shopify metafields
Every field the app produces is written to a Shopify customer metafield in the app-owned namespace $app:piing-intelligence. Each customer also gets one intelligence_summary metafield that records every value with its confidence score and whether it came from AI or a rule.
Because these are standard Shopify metafields, they are part of your store's customer records. You can see them in the Shopify admin, query them through the Shopify API, and build customer segments on them directly.
The app pins its field definitions, and Shopify only shows pinned fields on a customer, so the profile is visible on the customer page itself rather than only through the API. That includes the at-a-glance intelligence summary. If a store's customer records look empty while the app shows profiles, Re-sync metafields on the Customers page re-pins the definitions and rewrites every field. It uses no analysis allowance and makes no AI calls. See Run and schedule analyses.
Your CRM and tools pick them up
Metafield-aware tools can use the fields without a separate customer-profile database:
- Klaviyo and Attentive can use the fields when their Shopify data path and merchant configuration expose them.
- Shopify segments can be built on values such as reactivation risk, lifetime value tier, or preferred category.
- Your theme and storefront apps can read the metafields to personalise what shoppers see.
For example, a Klaviyo win-back flow can trigger on a high reactivation risk value, and a Shopify segment can group customers by preferred price band.
What the app stores, and what it does not
The app's own database holds shop configuration, run metadata, optional pixel events, anonymous visitor identifiers and operational logs. It does not store customer names, emails, phone numbers or addresses in its tables.
The selected profile lives in Shopify. To produce AI-inferred fields, product titles, variants, types, vendors, prices and order dates are sent to Anthropic. Names, emails, addresses, payment details and raw customer identifiers are not included in the inference prompt. Rule-based fields are calculated by the app. When the optional storefront pixel is enabled, consented browsing events are sent to Piing and retained for the merchant's configured window.
Note
On uninstall, Shopify removes app-owned metafields. Intelligence deletes run records, revokes its stored access and schedules the remaining shop configuration for deletion after 30 days. Shopify customer and shop redact webhooks handle the relevant customer and shop deletion routes.
A note on the storefront pixel
If you run the storefront pixel, raw browsing events are held for a limited retention window and then deleted. The browsing-based fields derived from them are written to Shopify metafields like the rest of the profile. No names, emails, or IP addresses are stored on pixel rows.
For the full picture of where data lives and what is stored, see the security page.
Next steps
Related guides
Was this guide helpful?
You’ve reached the end of Piing: Intelligence.
Still need a hand? Contact us