Digital product from a content site
A publisher sells a paid guide at the end of an article. Each purchase is a Klaviyo event, and a flow on that metric sends the download link and a follow-up.

Checkout embed
Klaviyo forms and tracking run on your WordPress site through Klaviyo's own script. A Plandalf button on that site sends paid buyers to Klaviyo as events.
No credit card required. No coding required.
WordPress
KlaviyoPlandalf has no native Klaviyo step, so the link is a webhook. WordPress hosts a Plandalf button, and a Plandalf sequence posts the buyer to Klaviyo's Events API or profile API with Send Webhook, or through Zapier. Klaviyo's sign-up forms on the same page are Klaviyo's own embed code and are separate.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout opened from a WordPress page | WordPress → Plandalf | The SDK script and a data-plandalf-present button go in a Custom HTML block or the theme. Your Stripe or PayPal account takes the payment. | |
| Checkout completed | Plandalf (paid via Stripe) → Klaviyo | Webhook | Send Webhook POSTs to Klaviyo's Create Event endpoint. The reference needs a private key with the events write scope, a revision header, and a body with properties, a metric name and a profile identified by email. |
| Checkout completed | Plandalf (paid via Stripe) → Klaviyo | Webhook | Klaviyo's profile-import endpoint creates or updates a profile with first name, last name and your own properties, and needs the profiles write scope. |
| Upsell accepted | Plandalf (paid via Stripe) → Klaviyo | Webhook | Record it as its own metric, so a Klaviyo flow starts only for people who added the upgrade. |
| Profile enters a flow | Klaviyo → Plandalf | Webhook | Plandalf's Klaviyo page describes a flow Webhook action that posts to a Plandalf catch URL, so the sequence can run Enroll in Promo for the profile. |
You need a WordPress login that can insert JavaScript, a published Plandalf offer and a Klaviyo private API key.
In the page Code editor or a Custom HTML block paste the Plandalf SDK script and a button with data-plandalf-present and your offer slug. Publish, then open the live page signed out and check that the checkout opens.
Klaviyo's embed-form help says sign-up forms need its onsite tracking script, which many platforms add automatically and a WordPress site without a native connection must add by hand. Embed forms need their code pasted, while popups and flyouts do not.
Make a Klaviyo private API key with the scopes for the calls you use, events write for the event and profiles write for profile import. Keep it out of the page and only in the Plandalf step.
In Plandalf open Automation, then My Sequences, and create a sequence on Plandalf, Checkout Completed and the offer. Pick a recent checkout as the sample on the Test tab.
Add Send Webhook with POST to https://a.klaviyo.com/api/events. Add the Authorization header, the revision header and a Content-Type of application/vnd.api+json. In the body set the metric name, put {{trigger.customer_email}} in the profile and {{trigger.line_items_summary}} in the properties.
Switch on Run on test purchases, buy with your own email, and look for the event on the profile in Klaviyo. Then build a flow that starts on that metric, and switch the test setting off.
A publisher sells a paid guide at the end of an article. Each purchase is a Klaviyo event, and a flow on that metric sends the download link and a follow-up.
A studio sells a class pass from its WordPress schedule page. Pass buyers become Klaviyo profiles with a Class Pass event, which starts a flow of reminders.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Klaviyo help: How to embed a sign-up form on your website, Klaviyo API reference: Create Event, Klaviyo API reference: Create or Update Profile.