Plandalf

Affiliates overview

Use Plandalf attribution context to carry referral data from campaign links into checkout sessions and invoices.

Affiliate and referral workflows depend on one thing: preserving attribution from the first click through checkout completion.

Attribution path

  1. A visitor clicks a campaign, partner, or affiliate link.
  2. The URL includes a reference such as pf_ref.
  3. The SDK captures the reference and keeps it with the visitor identity.
  4. Checkout opens with the same visitor and campaign context.
  5. Purchase events, invoices, webhooks, and integrations can use that context.
<a href="https://example.com/pricing?pf_ref=partner_123">
  View offer
</a>

Checkout with attribution

await plandalf.present("pro-plan", {
  metadata: {
    partner: "partner_123"
  }
});

Builder context

Keep building from here.

Use the related Plandalf pages to connect this doc to offers, checkout, timers, integrations, automation, and implementation recipes.

The Numi offer editor with product, theme, automation, invoice, and checkout controls.
The offer editor is the central product surface for checkout and commerce setup.
The Numi platform settings screen showing connected stack configuration.
Integrations connect the offer to the rest of the stack.
The Numi sequences screen showing automated workflow configuration.
Sequences route work after checkout.
Offers Checkout and offer composition. Timers Deadline and promo engine. Automations Work after purchase. Integrations Connect the stack around the sale.

Feature detail