Fix the Fingerprint Error on Sparkforge Order Forms in WordPress

By Sparkforge Support Team ·Last reviewed May 3, 2026

Fingerprint errors come from blocked cookies in the customer's browser, or from the funnel using the same subdomain as the WordPress site. Use a different subdomain (e.g. funnels.example.com) for the funnel.

If your Sparkforge order form embedded in WordPress shows a fingerprint error, one of two things is happening. Diagnose by checking whether it's affecting one customer or every customer.

Scenario 1: Only some customers see it

Cause: that customer's browser is blocking cookie/storage access.

Fix: Have the customer enable cookies in their browser settings. This is rare and tied to specific browser configurations, not your setup.

Scenario 2: Every customer sees it on every device

Cause: the funnel domain is misconfigured. The order form runs in an iframe inside WordPress, and payment processing needs cookie access — which browsers block across mismatched domains.

Fix: Use the same root domain on both the WordPress site and the Sparkforge funnel, but with different subdomains.

Example: WordPress site is www.example.com. Don't use www.example.com or example.com for the funnel. Use a different subdomain like funnels.example.com.

Why the domain has to match

The order form renders inside an iframe. Browsers refuse cross-domain cookie access during checkout, which kills payment processing. Same root domain + different subdomain keeps the cookies in scope while letting the funnel sit on its own host.

Add the funnel domain

  1. Go to Settings → Domains. Add the same root domain as your WordPress site, with a different subdomain. Make sure nothing else is hosted on that subdomain.
  2. Open Funnel Settings for the funnel you're embedding. Set the new domain and save.
  3. Verify the funnel loads on the new subdomain before going further.

Repair an existing WordPress embed

  1. Go to your Sparkforge WP plugin settings. Hard-refresh if it was already open. Click the API Key save button.
  2. Click Edit on the funnel page you need to fix.
  3. Wait for it to finish loading — fields auto-populate.
  4. The preview URL should now show the correct subdomain matching your WordPress root domain. Click Save.

Frequently Asked Questions

Can I host the funnel on a totally different domain than WordPress?
No. The iframe-based order form needs the same root domain on both sides for cookies to work during payment. Different subdomain is required, different root domain breaks checkout.
Why does the funnel use an iframe instead of native rendering?
It's how the WordPress integration embeds the funnel page. The iframe handles funnel rendering while WordPress controls the surrounding page.
What if a different site is already hosted on the subdomain I want?
Pick a different subdomain. The subdomain must be exclusive to the funnel — anything else hosted there will conflict.
How do I verify the fix worked?
Open the WordPress page with the embedded funnel, fill in a test order, and check that the fingerprint error is gone before processing real payments.

Was this article helpful?