I’m rebuilding a client’s website. Their current site already lives in Webflow and does NOT have consent pro set up. They just told me their IT team purchased consent pro (premium) and “connected it to Webflow” and now want me to set up it up for the new site. They are also asking “who should be added as account manager”.
I’ve never set up consent pro or purchased a consent pro plan myself, so I’m not sure what the full purchase process is. When my client bought their plan, would they have needed to say which domain the license should apply to? Is that what they would have meant by “connected it to Webflow”? If I get consent pro functioning on the old (current production) site (where tag manager, analytics, etc are all currently functioning), will I be able to move it to the new site after we launch without running into licensing issues? And finally, does it make sense that I need to be added as “account manager” somewhere, when it relates to consent pro?
Site URL
Under NDA, but let me know if you need it for this situation and I can send privately.
Let me walk through each of your questions so you can head into this setup with confidence.
Licensing and what “connected it to Webflow” means
Consent Pro licenses are tied to a custom domain — one license covers one site. Testing is completely free on .webflow.io staging URLs, so no license is needed until the site goes live on a custom domain.
When the IT team said they “connected it to Webflow,” they were likely referring to installing the Consent Pro app via the Webflow Apps panel and linking the license to the custom domain through the Finsweet dashboard at my.finsweet.com/plans. That part lives on the Finsweet side, not inside Webflow itself.
Can the license move to the rebuilt site?
Users can change the domain for all licenses at any time
Both Lifetime (one-time purchase) & Subscription (monthly or annual)
Who should be “account manager”?
When you launch the Consent Pro app inside Webflow, it’ll prompt you to log in with your own Finsweet account — and there’s no issue accessing the client’s setup that way. You won’t reset or overwrite anything. If a more formal setup is preferred, your client can also add you to their Finsweet Workspace via my.finsweet.com.
One practical tip: since the current production site already has tag manager and analytics running, it’s worth setting up and testing Consent Pro on the .webflow.io staging URL first — it’s free and lets you verify everything before touching production.
Thank you for this! Looking more closely, when I open the Consent Pro app within the current production site, I can see it shows a “premium plan” (even though I’m logged into my own Finsweet+ account not associated with the Consent Pro purchase). When I do the same in the new site still in development, I see “get a plan”.
So I think my remaining question is - if I set up consent pro on the staging domain for the new site under development, I should be able to finalize and launch without issue once we have the production domain moved over?
Yes, that should work
Consent Pro licenses are typically tied to domains and so when you eventually launch with that same prod domain it should work
What you’re currently seeing makes sense. For the current production site that the domain is licensed under, Consent Pro shows premium plan while for the new dev site with a different (staging) domain, that is not yet registered, it shows get a plan
