Klaviyo
Tell Klaviyo when a known shopper comes back, so your flows reach people Klaviyo no longer recognizes.
What AdsPing sends
Klaviyo can only email a visitor it recognizes. It recognizes a browser through its own cookie, set when someone fills a Klaviyo form or clicks a Klaviyo email. When that cookie is gone (a new device, a cleared browser, or Safari deleting it after 7 days), Klaviyo sees an anonymous visitor and none of your browsing flows can start.
AdsPing keeps its own record of who each browser belongs to, built from the moments a shopper gives their email on your store: a checkout, a sign-up, an order. When that browser comes back, AdsPing tells Klaviyo with one of two events:
- AdsPing Visitor Identified: a known shopper is back on your store. Sent the moment they arrive, with the page they landed on and, if they added to a cart in the last 24 hours, that cart.
- AdsPing Browse Abandonment: a known shopper viewed a product and left without adding anything to the cart. Sent 30 minutes after their last page view, with the product they looked at: name, image, price, link and, when it's on sale, the compare-at price.
Each event goes to the shopper's Klaviyo profile, matched by email, so you don't get duplicate profiles. Each event fires at most once per browser per day, and these events never count toward your AdsPing plan's event allowance.
What AdsPing never sends
Orders, carts, checkouts and product views keep coming from Klaviyo's own Shopify (or WooCommerce) integration. AdsPing does not send Placed Order, Started Checkout, Added to Cart, Viewed Product or Active on Site. Your revenue numbers, attribution and existing flows in Klaviyo stay exactly as they are.
The two AdsPing events have their own names, so they show up as two new metrics in Klaviyo. They never merge into Klaviyo's own metrics.
Connect in two minutes
- In AdsPing, open your pixel and go to Destinations. Find the Klaviyo card under Email marketing and click Connect with Klaviyo. You can also start from Klaviyo's app listing: Install brings you to
adsping.io/dashboard/integrations/klaviyo, where you pick the pixel if you have more than one. - Sign in to Klaviyo if asked and choose the Klaviyo account for this store. You need to be its owner, an admin or a manager.
- Review the access and click Allow. AdsPing asks for two things only: reading your account name (Accounts: Read) and creating events (Events: Write). It can't read your lists, profiles, campaigns or flows.
- You land back on the pixel with Klaviyo marked Connected.
- Confirm the email AdsPing sends to the account owner. Because Klaviyo receives shoppers' email addresses, customer details start flowing 24 hours after you confirm. This wait protects you if someone else ever gets into your AdsPing account.
To disconnect, click Disconnect on the Klaviyo card. AdsPing stops sending and removes its access in Klaviyo at the same time. Removing the app in Klaviyo (Integrations → My apps) works too.
pk_).Build your flows
- In Klaviyo, go to Flows → Create flow → Build your own.
- Pick Metric as the trigger and choose AdsPing Browse Abandonment (or AdsPing Visitor Identified). The metric appears after the first event arrives.
- Add a flow filter such as Placed Order zero times since starting this flow, so a shopper who buys in the meantime doesn't get the email.
The product arrives under the same property names Klaviyo's own Viewed Product event uses, so product blocks you already built keep working: {{ event.ProductName }}, {{ event.ImageURL }}, {{ event.URL }}, {{ event.Price }}, {{ event.CompareAtPrice }}, {{ event.Brand }} and {{ event.SKU }}.
Klaviyo's consent rules still apply: AdsPing doesn't change anyone's subscription status, and Klaviyo only sends marketing emails to profiles that can receive them.
Safari and the custom domain
Safari deletes cookies written by scripts after 7 days, and that includes both Klaviyo's cookie and AdsPing's own. With a custom tracking domain (Pro plan and above), AdsPing's cookie is set by your own server instead, so Safari keeps it for up to two years. That is the setup where AdsPing recognizes the most returning shoppers Klaviyo has lost. Without a custom domain, AdsPing still helps whenever its record and Klaviyo's cookie disagree, for example when a shopper checked out but never clicked a Klaviyo email on that browser.
Common questions
I use Shopify and Klaviyo already sends my store data. Will this create duplicates?
No. Klaviyo's Shopify integration keeps sending orders, carts and product views. AdsPing sends only its two named events, which Klaviyo doesn't have, and every event carries a unique ID so a retry is never counted twice. The one thing to watch is two browse abandonment flows running side by side (see the warning above).
What does AdsPing add on top of Klaviyo's Shopify integration?
Klaviyo's browsing flows only start for visitors carrying its cookie. AdsPing starts them for shoppers Klaviyo has stopped recognizing: returning customers on a cleared or Safari-expired browser, and customers who bought or signed up but never clicked a Klaviyo email on that device. Those are usually your warmest visitors, and without AdsPing they browse anonymously.
Will my Klaviyo bill go up?
Usually not. Klaviyo bills by active profiles, and AdsPing matches events to profiles by email. On a store with Klaviyo's Shopify integration, someone who checked out or signed up is almost always already a profile. If Klaviyo doesn't have that email yet, it creates the profile when the first AdsPing event arrives.
Does it count toward my AdsPing plan?
No. Visitor Identified and Browse Abandonment events are not counted toward your monthly event allowance.
How do I check it's working?
In Klaviyo, open Analytics → Metrics and look for the two AdsPing metrics, or open a profile you know and check its activity feed. In AdsPing, the Klaviyo connection shows the last delivery and any error Klaviyo returned.