WordPress

Add Plandalf checkout buttons, inline embeds, countdown widgets, and customer identity to WordPress pages.

WordPress can host Plandalf through Custom HTML blocks, theme templates, or plugin-managed script injection. Use the simplest block first, then move the script into a theme or plugin once the page works.

WordPress is the page shell

Let WordPress handle content, memberships, and templates. Let Plandalf handle the offer, checkout, promo pricing, invoices, and post-purchase automation.

The path

  1. Put the script in a Custom HTML block for a quick test, or enqueue it from the theme/plugin for a production-wide install.

  2. Use a Custom HTML block or template markup with data-plandalf-present.

  3. Membership and LMS sites should generate identity server-side and call identify() on checkout pages.

  4. Test the real page output because builders, cache plugins, and optimizers can move or delay scripts.

Quick block install

WordPress Custom HTML block

<script src="https://acme.plandalf.com/js/plandalf-sdk.js" async></script>

<button data-plandalf-present="pro-plan">
  Buy Pro
</button>
<div data-plandalf-mount="pro-plan" style="min-height: 480px"></div>
<div data-plandalf-promo="early-bird"></div>

Logged-in users

For membership, LMS, or account-based sites, generate a signed identity token server-side and identify the visitor before checkout.

<script>
  window.addEventListener("load", () => {
    plandalf.identify("SIGNED_JWT_FROM_WORDPRESS");
  });
</script>

WordPress setup choices

Fields
Custom HTML blockpage-level

Fastest way to test one page or one campaign.

Theme templatetemplate-level

Useful when every product, post, or landing page should expose a buying action.

Plugin/script enqueuesite-level

Best for a managed production install, especially when caching or optimization plugins are active.

Builder context

Connect platform setup to the full stack.

Platform docs explain where an external system fits. The related surfaces show how integrations, offers, payments, invoices, and automation stay visible in Plandalf.

The Numi platform settings screen showing connected stack configuration.
Integrations keep external systems visible to the operator.
The Numi integrations settings page showing Stripe, PayPal, Stripe test mode, TaxJar, and Avalara connection options.
Payment processors and tax services are configured before checkout traffic goes live.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.
Automations decide what happens after the connected platform sends or receives purchase context.

Feature detail