PIING
Reading IntegrationsConnect Piing to your stack
Integrations
- Connect Piing to your stack
- Connect Shopify
- What Piing reads back from your stack
- Connect Klaviyo
- Connect Attentive
- Connect Rivo
- Connect Yotpo
- Connect LoyaltyLion
- Connect Antavo
- Connect Swym Wishlist Plus
- Award points on check-in
- Webhooks and custom integrations
In this guide
- The core visit flow
- What Piing can write to Shopify
- Current named integrations
- Three connection patterns
- Where to manage connections
- Data boundary
- Testing a connection
- Next steps
Search or browse documentation
Integrations 1 / 12
Connect Piing to your stack
What Piing reads, writes and emits, the current named integrations, and how purchase and no-purchase visits reach downstream tools.
Piing turns an identified store visit into structured events and customer context that the retailer's existing systems can use. The commerce platform, loyalty programme and CRM keep their current roles. Piing adds the visit, the Wallet channel and the link to a later outcome.
The core visit flow
- A kiosk, Piing reader, printed QR sign or Shopify POS action creates a recognition request.
- Piing resolves the identifier and customer context needed for that route.
- A completed check-in records the store, time, source and customer reference.
- Enabled destinations receive the event and the Wallet or staff view updates.
- A later order inside the merchant's configured attribution window creates a purchase outcome. If the window closes without an order, Piing can create a no-purchase outcome.
The same underlying check-in model applies regardless of which recognition route the store uses.
What Piing can write to Shopify
Piing can write selected visit context to Shopify customer metafields, including:
- lifetime and recent visit totals;
- last visit time and store;
- visit source;
- loyalty tier and supported programme values;
- Wallet pass status;
- selected wishlist or customer context.
Shopify Flow, Shopify customer segments and other metafield-aware tools can use those values. The receiving workflow still needs to be configured by the merchant.
Current named integrations
CRM and messaging
Klaviyo, Attentive, Ometria and HubSpot receive typed visit and outcome events for configured workflows.
Loyalty
LoyaltyLion, Rivo, Yotpo and Antavo can provide points and tier for the Wallet pass and staff context. Reward availability depends on the provider; the direct Yotpo connection does not read a redeemable-rewards catalogue. Point awards are a separate setting and only happen when the merchant enables them.
Wishlist
Swym Wishlist Plus, Wishlist King and supported customer metafields can provide saved-item context for staff, Wallet messages and attribution.
Commerce and staff
Shopify remains the customer and order record for the native product. Shopify POS provides the staff extension and one recognition route. Retail ID handles non-Shopify and bespoke stacks through a scoped implementation.
Fuego can work alongside Piing as a mobile-commerce layer. It is not treated as the loyalty engine.
Three connection patterns
Native connectors
A named connector understands the destination's authentication and data model. The merchant provides the required credentials, chooses the enabled behaviour and can send a test where that connector supports it.
Shopify metafields
Some customer context already lives in Shopify. Piing can read supported values from customer metafields, and Intelligence writes its selected output there. Any tool using those fields reads the Shopify record rather than a separate Piing profile.
Signed webhooks
A custom endpoint subscribes to selected events and receives a signed JSON payload. Delivery status and failures remain available for support and diagnosis. See Webhooks and custom integrations.
Where to manage connections
On Shopify, use Integrations inside the Piing app. The page shows the available routes, connection status and controls relevant to each connector.
For Retail ID, the integration surface and credentials are part of the contracted implementation. The exact commerce identity route and destinations depend on the retailer's stack.
Data boundary
Piing sends the identifier and event context required for the enabled workflow. It does not need a bulk migration of the retailer's entire customer database to create a visit event. The commerce platform remains the primary customer record, while Piing stores the operational visit, routing and delivery records needed to provide the service. See Security.
Testing a connection
Use a known test customer and verify the whole path:
- Record a check-in from the route being deployed.
- Confirm the event appears against the correct customer and location.
- Confirm each enabled destination receives the expected event.
- Place a test order inside the configured window and confirm the purchase outcome.
- Run a separate no-purchase test through the full window.
- Check the Wallet pass, Shopify metafields and staff context that the workflow is meant to update.
Next steps
Related guides
Was this guide helpful?
Next guide in Integrations
Connect Shopify
How Piing uses Shopify customers, orders, metafields and webhooks for recognition, attribution and staff context.
Still need a hand? Contact us