Embed a funnel on an external page
Funnel embed lets buyers continue an upsell or downsell flow on your own website instead of only on an AtomicPay-hosted page. This is useful when the post-purchase experience should match your site design or when the next offer appears on a custom thank-you page.
Use embed only after the funnel is built, previewed, and tested inside AtomicPay. If the funnel itself is still unstable, fix broken funnel paths before embedding.
What funnel embed controls
| Area | Purpose |
|---|---|
| Embedded funnel step | Shows the next offer on an external page. |
| Accept and decline behavior | Moves the buyer through the funnel path after a decision. |
| Button rendering | Uses AtomicPay buttons or your own custom triggers. |
| Script loading | Loads the funnel upsell script on the external page. |
| Buyer continuity | Connects the external page to the configured funnel step and offer. |
Embed modes
| Mode | Use it when |
|---|---|
| AtomicPay buttons | You want AtomicPay to render the default accept and decline buttons |
| Custom buttons | You want your page design to control the buttons and only use AtomicPay triggers |
Before you embed
- Build and test the funnel in build funnels, upsells, and downsells.
- Confirm each step has the correct product, plan, and offer.
- Publish related checkout pages.
- Decide whether you will duplicate the funnel for experiments instead of changing the live embed.
- Align UTM and campaign links before traffic starts.
Get and install the embed code
- Confirm you are in the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the product funnels area.
[Screenshot: Product funnels page — funnel list visible.]
- Select the funnel you want to embed.
[Screenshot: Target funnel row selected for embed.]
- Open the funnel embed dialog.
[Screenshot: Funnel embed dialog — embed options visible.]
- Choose AtomicPay buttons or Custom buttons.
[Screenshot: Embed mode selector — AtomicPay or custom buttons chosen.]
- Copy the embed code.
[Screenshot: Embed code copied to clipboard.]
- Paste the code on the external page where the funnel step should appear.
[Screenshot: External page editor — embed script pasted in HTML.]
- Publish the page change.
[Screenshot: External page published — embed live on site.]
- Test every accept and decline path.
[Screenshot: Embedded funnel test — accept and decline buttons working on page.]
- Confirm purchases appear in Sales and reporting in Financial Overview when applicable.
[Screenshot: Sales detail — embedded funnel purchase recorded.]
Custom button mode
When using custom buttons, your page needs trigger elements with the expected classes:
- Accept trigger:
atomicpay-payment-trigger - Decline trigger:
atomicpay-refuse-trigger
The funnel script still must load on the page. Multiple trigger elements can exist when the funnel design requires them.
What to verify before launch
| Check | Why it matters |
|---|---|
| Funnel step has the correct offer | Wrong offer breaks trust and reporting. |
| Accept and decline paths have no dead ends | See broken funnel paths. |
| Mobile layout works on the external page | Use mobile checkout preview patterns where relevant. |
| Checkout pages are published | Unpublished steps break embedded flows. |
| Attribution still makes sense | Compare Campaigns after first traffic. |
Best practices
- Test the funnel internally before embedding externally.
- Keep a naming convention for embedded pages and funnel variants.
- Retest after pricing or offer changes.
- Use duplicate funnels for experiments when possible.
- Document which external URLs use which funnel embed.
Common mistakes
- Embedding before the funnel works inside AtomicPay.
- Missing script or wrong trigger classes on custom pages.
- Pointing accept or decline to the wrong step.
- Changing the live funnel during a campaign without retesting the embed page.
- Assuming embed fixes checkout layout issues on the first step.
FAQ
Should I embed before testing the funnel internally?
No. Test the funnel flow inside AtomicPay first, then embed only after all paths work.
What usually breaks embedded funnels?
Missing script, wrong trigger classes, unpublished checkout steps, inactive offers, or accept and decline paths pointing to the wrong step.
Can I embed on multiple pages?
Yes, but document each page and retest attribution and funnel branches for every use case.