PIING
Reading IntegrationsConnect Klaviyo
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
- What you get
- What Klaviyo receives
- Before you start
- Connect it
- Test the connection
- Ideas to build
- Example: follow up two hours after check-in
- If something looks wrong
Search or browse documentation
Integrations 4 / 12
Connect Klaviyo
Send in-store tap events to Klaviyo so flows and segments react to real shop-floor behaviour, with separate signals for browsers and buyers.
Connecting Klaviyo lets your email and SMS flows respond to in-store visits, not just online activity. Enable check-in delivery to send recognised visits to the matching customer profile. Your Klaviyo flow controls the audience, delay and message.
What you get
- A Klaviyo metric for every in-store check-in, attributed to the matching customer profile.
- Separate purchase-attributed and no-purchase events, so you can treat customers with a qualifying order differently from those without one in the configured window.
- An attribution window after each visit, so you can measure online orders that follow an in-store tap.
What Klaviyo receives
Piing sends the selected event and the resolved Shopify customer identifiers Klaviyo needs to attach it to the correct profile. The outbound profile properties can include Piing visit context and selected Piing customer fields, according to your destination settings.
This connection does not import arbitrary Klaviyo profiles, custom properties or Klaviyo order history into the Piing staff view. Shopify, your configured loyalty source and merchant-selected Shopify metafields remain the inbound sources for that experience. See what Piing reads back from your stack.
Before you start
- A Klaviyo account with a private API key. You create keys in Klaviyo under Settings then API keys. Grant the key at least the events:write scope (to send check-ins) and the metrics:read scope (so Piing can verify the key when you save it).
- Piing set up and at least one recorded check-in, so you have something to test against. See Install the Shopify app on Shopify, or Set up Retail ID for a scoped non-Shopify implementation.
Connect it
- In Piing, go to Integrations and find Klaviyo.
- Paste your Klaviyo private API key and save.
- Piing verifies the key and queues the check-in events you enable for delivery to Klaviyo.
Note
Piing matches each tap to a customer using the same identity it already resolves in your store, so events land on the right Klaviyo profile without you mapping anything by hand.
Test the connection
- Record a test check-in from Hardware & Check-ins then First Tap, using an email that exists as a Klaviyo profile.
- In Klaviyo, open that profile's activity feed and confirm the check-in metric appears.
Once the metric is flowing, you can build flows and segments on it like any other Klaviyo event.
Ideas to build
- A welcome-back flow triggered by a check-in, with a delay your team chooses.
- A browser follow-up flow on tap-without-purchase, nudging customers who came in but did not buy.
- A frequent visitor segment for customers with several check-ins in a rolling window, for early access or VIP treatment.
Example: follow up two hours after check-in
- Enable the check-in event for the Klaviyo destination and confirm it arrives on a test profile.
- Use that event to start a Klaviyo flow, then add a two-hour delay. This is an example timing, not a Piing default.
- Before sending, check whether the customer has placed an order since entering the flow. Skip this follow-up if they have.
- Apply your existing consent, suppression and frequency rules, then send a useful message such as an offer of help from the store.
The delay starts at check-in, not when the customer leaves. Piing does not detect departure.
Alternatively, use Piing's no-purchase event as the trigger. Its window can be configured separately from purchase attribution; if no separate window is set, it follows the attribution window. The event is emitted by a periodic background check, so delivery is not guaranteed at an exact minute. That trigger already waits for its configured window: only add another CRM delay if you intend to wait longer.
If something looks wrong
- No metric appearing? Re-check the API key in Integrations, and make sure the test email matches a real Klaviyo profile.
- Events on the wrong profile? Confirm the customer's email on your commerce platform, Shopify for example, matches the one in Klaviyo.
- Still stuck? Contact us and we will help trace the event.
Piing connects to other CRM and messaging tools the same way, including Attentive, Ometria, and HubSpot. See the full list on the integrations page.
Related guides
Was this guide helpful?
Next guide in Integrations
Connect Attentive
Send in-store tap events to Attentive so SMS and email journeys respond to real shop-floor visits, matched to the right subscriber.
Still need a hand? Contact us