App and software trials
Buyers of a trial checkout get an App trial tag and a started_trial event. The Customer Journey sends the onboarding emails, and the tag lets you leave current trialists out of the sales newsletter.
Native integration
Stripe takes the payment, and the paid Plandalf checkout adds the buyer to your Mailchimp audience, tags them and starts the right Customer Journey.
No credit card required. No coding required.
MailchimpPlandalf connects them with native Mailchimp steps; Plandalf does not sync Stripe with Mailchimp directly. A Plandalf checkout takes payment through your Stripe account, then a sequence adds the contact to an audience, tags them and records an event. Mailchimp events can also start Plandalf sequences.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → Mailchimp | Native step | Add Tags to Contact puts the buyer in the audience first if they are not there, so no separate create step is needed. A tag typed into the step can include variables such as the offer name. |
| Checkout completed, event recorded | Plandalf (paid via Stripe) → Mailchimp | Native step | Record Event sends a custom event such as started_trial that a Customer Journey can begin on. Mailchimp events carry no revenue and Plandalf does not use Mailchimp's ecommerce API, so the sale does not show up as a Mailchimp order. |
| Invoice paid | Plandalf (paid via Stripe) → Mailchimp | Native step | Covers renewals and invoices you send. Add or Update Contact can write a merge field such as PLAN each time, as long as the field already exists on the audience. |
| Invoice refunded | Stripe → Mailchimp | Native step | Remove Tags from Contact takes off the tags the purchase sequence added. If the email is not in the audience the step is skipped instead of failing. |
| Contact subscribed | Mailchimp → Plandalf | Native step | Saving the trigger adds a webhook to the audience that you can see under Audience, Settings, Webhooks. A common follow-on is Enroll in Promo, which starts a countdown for each new subscriber. |
| Unsubscribe step | Plandalf → Mailchimp | Native step | Unsubscribe Contact ends marketing email for a contact while leaving them in the audience as unsubscribed. It is skipped when the email is not in the audience. |
You need a Stripe account and a Mailchimp login that can open Extras, then API keys.
Authorize your Stripe account in Plandalf, attach a Stripe-backed price to an offer and publish it. Payments are processed by Stripe and paid out to your Stripe account.
In Mailchimp open your profile menu, then Extras, then API keys, and choose Create A Key. Copy the whole key, including the data-centre ending such as -us21, because Plandalf needs that part to find your account.
In Plandalf open Automation, then Marketplace, and click Connect on Mailchimp under Available now. Paste the key into API Key. Plandalf loads your account to check it and shows Mailchimp connected.
Create a sequence under My Sequences with Plandalf, Checkout Completed and your checkout under Offer. Add Mailchimp, Add Tags to Contact, pick the Audience, set Email Address to {{trigger.customer_email}}, add a tag such as App trial and set First Name to {{trigger.customer_first_name}}.
Add Mailchimp, Record Event on the same audience and email. Set Event Name to started_trial and add an Event Properties pair of plan and {{trigger.line_items_summary}}. Then, in Mailchimp, build a Customer Journey with an Event starting point that uses exactly that name.
Under Automation, then Templates, add Remove access on refund for the same checkout and set its Remove Tags from Contact step to the Audience and tags you applied. The trigger fires on a full refund only, including one made in the Stripe dashboard.
Turn on Run on test purchases, buy through the test link with a Stripe test card, then check the contact, tag and journey entry in Mailchimp and turn the setting off. A step test on its own changes a real contact, so use your own address.
Buyers of a trial checkout get an App trial tag and a started_trial event. The Customer Journey sends the onboarding emails, and the tag lets you leave current trialists out of the sales newsletter.
A shop with several digital products keeps a single audience and adds one tag per product from separate sequences filtered by Offer. A merge field such as PLAN, filled by Add or Update Contact, covers anything a tag is too coarse for.
Contact Subscribed on the waitlist audience starts a sequence that enrolls the new subscriber in a promo, so each person sees their own countdown. When they pay, the purchase sequence tags them and the waitlist emails can stop.
-us21 or similar is rejected before it is saved.Checked October 26, 2026 against Plandalf's own setup guides.