Description
Hey team,
I’ve just set up consent pro for a client website, and trying to pull up the debugger to make sure it’s all working correctly. However, when in the Webflow app and clicking ‘test it on live website’ it will open up in the staging domain, with the console errors attached.
Would love some guidance on this please! Wondering if I’ve set this up wrong.Tried with refreshed cache, and private browsing with the same behaviour. One thing to note is that I keep needing to check off four pending items related to generating documents every time I launch (I don’t need to do this as the client had their own written).
Site URL
- Staging URL: https://custodian-labs-staging-site.webflow.io/
- Production URL: can’t provide this currently as I’m limited to two links as a new user (staging.+ Loom)
- Webflow Read-only link: I can send this privately, please let me know whom to send to?
Steps to Reproduce
- Open up the consent pro app in Webflow
- Click actions
- Click test it on live website
- Check console
Expected Behavior
When clicking on ‘test it on live website’ I expect it to open the production domain with the Consent Pro debugger tool
Actual Behavior
When clicking on ‘test it on live website’ It opens the staging domain with no debugger tool, and console errors present
Video/Screenshots
Additional Context
- Browser: Arc Version 1.155.1 (83244)
- Device: Desktop
Hey @Matthew
On the staging vs. production question — this is expected behavior. The “test it on live website” feature is designed for your production domain where a Consent Pro license is active. Without a licensed domain connected, it falls back to staging, and the debugger returns a 403 because the domain isn’t authorized. Make sure your production domain is linked to your Consent Pro subscription at my.finsweet.com/plans.
Once the production domain is linked to your Consent Pro subscription & the script is installed on your site as you’ve already done
<!-- Consent Pro script -->
<script src="https://api.consentpro.com/v2/cdn/runtime/YOUR_SITE_ID.js" type="text/javascript" finsweet="consentpro" siteid="YOUR_SITE_ID"></script>
and the site is published, the Consent Pro app will scan your setup. You’re looking for a “You are all set” success message. Until that appears, the debugger won’t have a functioning instance to attach to.
Can you confirm whether you’ve purchased a license for the production domain https://www.custodianlabs.io/
On the 4 pending items — if your client already has their own legal documents (Privacy Policy, T&Cs, etc.), you can dismiss those action items manually in the app. They reappear because the app tracks outstanding setup actions, but they’re not blocking your core config.
Hey @jesse.muiruri , thank you for the response!
I can confirm I have added the consent pro script, have an active subscription (basic plan), and have added https://www.custodianlabs.io/ as an authorised domain. Everything in the Consent Pro app looks correct, with the ‘You’re all set’ message in the actions tab (after checking off those 4 pending legal documents).
Any ideas on what else I can check?
Cheers,
Matthew
Hey @matthew
I’ve forwarded this to the relevant team
I’ll keep you posted
Thanks
Thanks @jesse.muiruri, appreciate it. Looking forward to hearing back!
Hey @matthew
The dev teams involved with ConsentPro have clarified that the debugger opens in staging & works in staging only, never in production
It’s like that by design, here’s their exact wording
We pushed an update to enforce this behaviour of a feedback review from Webflow to remove extra scripts injection in live sites
Let me know what works with you, always happy to help
Thanks
Hey @jesse.muiruri ,
Thanks for your and the teams response. I understand that it’s not intended to work on the production site, however, the debug tool still fails to launch on the staging domain as well.
So clicking ‘test on live site’ with all actions resolved, it will open Custodian Labs | Build and deploy AI agents in 5 lines of code but still not launch the debugger and shows the console errors in my original screenshot.
Any ideas from here?
Thanks,
Matthew
Hey @matthew looks like a typo crept up you, this is the correct param name
custodian-labs-staging-site.webflow.io/?consent-pro-debugger=true
Let us know, thanks!
Hey @jesse.muiruri
Appreciate the continued support. Was hoping it would be something simple like this, unfortunately not!
The ‘test on live website’ is the one that generated the typo, interestingly. Anyway, going directly to the link you provided its still not working for me with the below console error.
Tried on a private tab and on a different network as well. No dice.
Are you able to confirm if it’s working for you, or if it’s working on other website where consent pro has been implemented?
Thanks!
Hey @matthew so sorry this has dragged on longer than expected
We have identified a bug and are working with Webflow to fix this
Please keep it here for updates
Thanks
Hey @matthew
The debugger should now load on the staging domain, kindly update if that’s the case on your end
Just a lil heads-up, the license check is failing at the moment though the team is on top of things & should be resolved soon
This might just be what you see on your screen
Hey @jesse.muiruri, yes, I noticed a couple of days ago that it was working by accident! Thank you so much to you and the team for looking into it. It’s a great tool, so glad to see it working (mostly) correctly now.
Ok awesome @matthew thanks for the confirmation
