Here is an example of this error when submitting an order form:
Scenario 1:
If you only experience this with some of your customers randomly, this means it is likely due to the customer's browser settings, and we are not able to access cookies for the purchase. There are very rare chances of this issue.
Solution: A quick fix would be to guide the customer through updating their browser settings and enabling cookie access.
Scenario 2:
If a client faces this issue repeatedly on every device and multiple browsers, it means the funnel domain is not configured correctly.
Solution: If the website is hosted on WordPress and they are using our order form funnel inside that as a separate path, then the WordPress website domain and the funnel domain should be the same, but the subdomain should be different.
Suppose your WordPress website is configured with www.example.com#####rep...#####, where example.com is your domain, and www is your subdomain. So now, you should not use www.example.com ; or example.com as the funnel domain. Instead, use a different subdomain (e.g., funnels.example.com ) in the funnel.
Note: Per our current implementation, we use iFrame to render funnel pages inside WordPress. For payment, we need access to web browser cookies (storage), and the web browser may not allow access over a cross-domain.
1. Go to Settings > Domains and add the same domain (as WordPress website) with a different subdomain. (Make sure that no other Website is hosted on that subdomain)
2. Go to Sites > Funnels > Select the Funnel and go to Settings (choose the funnel you want to use in WordPress). Configure the domain and save it.
3. Verify that funnel is successfully connected & working with that subdomain.
Go to your LeadConnector WP settings and hard refresh the page if it has already opened. Then click on the API Key save button.
Click the pencil icon to edit the funnel page/step you want to fix.
Wait for the loading to finish, and the step will auto-fill.
Now, you will be able to see the same WordPress website domain (the subdomain will be different) in the preview URL. Click “Save Page” to save the changes.
Browser Settings: For customers experiencing the “Fingerprint is missing” error intermittently, advise them to check their browser settings and ensure cookies are enabled. This can often resolve the issue if it’s related to specific browser configurations.
Domain Configuration: Ensure the funnel and WordPress site are on the same primary domain but different subdomains. This setup helps avoid cross-domain cookie access issues. For instance, if your WordPress site uses www.example.com#####rep...#####, use a subdomain like funnels.example.com for your funnel.
Subdomain Addition: When adding a subdomain for the funnel, ensure no other websites are hosted on it. This avoids potential conflicts and ensures proper funnel functionality.
API Key Update: After making domain changes, always hard refresh the LeadConnector WP settings page and re-save the API Key. This ensures that any new configurations are properly applied.
Q: What does the “Fingerprint is missing” error indicate?
A: This error suggests that the funnel cannot access cookies, which may be due to browser settings or domain configuration issues.
Q: How can I resolve the error if it happens with only some customers?
A: Guide the affected customers to update their browser settings to enable cookie access. This is a rare issue but can be fixed by ensuring cookies are allowed.
Q: What should I do if the error occurs on all devices and browsers?
A: Ensure that the funnel domain is correctly configured. Use a subdomain different from the main WordPress domain to avoid cross-domain cookie access issues.
Q: How do I add a subdomain for the funnel?
A: Go to Settings > Domains, add the domain with a different subdomain, and ensure no other sites are hosted on that subdomain. Then configure this subdomain in your funnel settings.
Q: What steps should I follow to fix an existing funnel in WordPress?
A: Refresh the LeadConnector WP settings page, re-save the API Key, edit the funnel page/step, and ensure the preview URL reflects the correct subdomain. Save the changes to apply them.
