Offer configuration stays visible
Use Offers to decide what ActiveCampaign receives: product, price, buyer, checkout mode, invoice, and automation context.

Integration
Plandalf integrates with ActiveCampaign as a email, marketing, website, sdk platform.
Product surfaces
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before ActiveCampaign receives checkout, payment, tax, or workflow context.
Use Offers to decide what ActiveCampaign receives: product, price, buyer, checkout mode, invoice, and automation context.
Before ActiveCampaign enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
ActiveCampaign should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
ActiveCampaign can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair ActiveCampaign with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when ActiveCampaign should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when ActiveCampaign belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
ActiveCampaign is a marketing and sales CRM with a visual Automations builder and a Webhook step. The typical promo pattern is embedding a countdown GIF in an email and enrolling contacts via an automation triggered by a tag, list subscription, or form submission.
%EMAIL% merge tag
substitutes at send time and drops into the <img src> query string.Setup templates
Copy-paste setups for the most common ways to wire ActiveCampaign into Plandalf.
promo · email
Paste this <img> tag into any HTML block in your ActiveCampaign
campaign or automation email. %EMAIL% is ActiveCampaign's merge
tag for the recipient.
<img
src="{{ promo.countdown_url }}?ref=%EMAIL%"
alt="Time remaining on this offer"
/>
promo · automation
{{ promo.catch_url }}
contact[email].
If your catch URL expects JSON, front it with a small proxy or
use the Webhooks action in an HTTP POST-capable workflow tool.Automation graph
How ActiveCampaign participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
activecampaign.subscriber_addedactivecampaign.automation_step_reachedactivecampaign.form_submittedactivecampaign.webhookThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
activecampaign.add_subscriberactivecampaign.tagactivecampaign.send_emailactivecampaign.start_automationactivecampaign.custom_api_callEmbeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution
trigger: stripe.payment_succeeded
actions:
- activecampaign.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Platforms whose roles complement ActiveCampaign inside a Plandalf sequence.
ActiveCampaign + beehiiv
Capture a lead on beehiiv, nurture it through ActiveCampaign.
ActiveCampaign + Kit (ConvertKit)
Capture a lead on Kit (ConvertKit), nurture it through ActiveCampaign.
ActiveCampaign + Customer.io
Capture a lead on Customer.io, nurture it through ActiveCampaign.
ActiveCampaign + Drip
Capture a lead on Drip, nurture it through ActiveCampaign.
ActiveCampaign + Flodesk
Capture a lead on Flodesk, nurture it through ActiveCampaign.
ActiveCampaign + Klaviyo
Capture a lead on Klaviyo, nurture it through ActiveCampaign.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use ActiveCampaign with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
Drop the Plandalf embed script into a ActiveCampaign HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
<script src="https://cdn.plandalf.com/embed.js" async></script>
<button data-plandalf-present="offer_abc123">
Buy now
</button>Add an HTML block to any ActiveCampaign email and paste the Plandalf countdown URL. ActiveCampaign's merge tag `%EMAIL%` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
<img
src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref=%EMAIL%"
alt="Time remaining on this offer"
width="600"
height="120"
/>Point a ActiveCampaign form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.
curl -X POST https://api.plandalf.com/v1/intake/activecampaign \
-H "Content-Type: application/json" \
-d '{"email": "{{ form.email }}", "source": "activecampaign"}'Inside ActiveCampaign's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror ActiveCampaign journey logic into Plandalf without re-building the segmentation.
{
"email": "{{ contact.email }}",
"sequence": "post-signup-onboarding",
"source": "activecampaign"
}For anything not covered by a native trigger, configure a ActiveCampaign webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/activecampaign \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d @event.jsonFAQ
Plandalf itself is free to connect. ActiveCampaign's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.
Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and ActiveCampaign's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the ActiveCampaign contact ID and the events Plandalf fired against that contact. Email content stays in ActiveCampaign; Plandalf doesn't mirror your audience or newsletter archive.
Use the generic `activecampaign.custom_api_call` action or the inbound `activecampaign.webhook` trigger. Anything ActiveCampaign's REST API can do, a Plandalf sequence can drive.
Plandalf respects ActiveCampaign's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
ActiveCampaign's homepage at https://www.activecampaign.com links to their developer docs. For Plandalf-side questions about the ActiveCampaign integration, see the Plandalf docs.