New subdomain site (not Webflow site) Questions

Consent Pro
1

Description

We currently have ConsentPro implemented and live on www.firstcarolinabank.com.

We are preparing to launch an Investor Relations site at ir.firstcarolinabank.com (hosted outside of Webflow) and would like to maintain the same consent experience and behavior across both sites.

A few questions:

  1. Does ir.firstcarolinabank.com require a separate ConsentPro plan/property/license, or can it be added under the existing firstcarolinabank.com configuration?
  2. If a separate property is required, can the existing configuration be cloned/copied rather than recreated from scratch?
    • Same banner
    • Same categories
    • Same consent behavior
    • Same appearance/settings
  3. We confirmed our current consent cookies appear to be scoped at .firstcarolinabank.com.
    Can the IR implementation honor and reuse those existing consent preferences across subdomains so users are not prompted again?
  4. If IR is hosted externally, is there anything special required to ensure:
    • consent persistence across subdomains
    • proper cookie domain configuration
    • correct handling of analytics/scripts based on consent
  5. Once configured, can you provide the official install script for ir.firstcarolinabank.com for the vendor to place globally across all pages?

Thank you!

Site URL

Required: Please provide a staging/production URL where we can see the issue

Steps to Reproduce

  1. [First step]
  2. [Second step]
  3. [Third step]
    …

Expected Behavior

[What did you expect to happen?]

Actual Behavior

[What actually happened?]

Video/Screenshots

Required: Please provide a short screen recording showing the issue

  • Video link: [Loom/Screen recording URL]
  • Screenshots (if applicable): [Upload or link to screenshots]

Additional Context

  • Browser: [e.g., Chrome 120, Safari 17]
  • Device: [e.g., Desktop, iPhone 14]

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

2

One follow-up: our current Finsweet/ConsentPro plan shows the domain configured as www.firstcarolinabank.com, however our consent cookies appear to be scoped to .firstcarolinabank.com.

Can you confirm whether consent preferences will be honored across ir.firstcarolinabank.com, or whether an additional domain/property configuration is required?

If a new property is required for ir.firstcarolinabank.com, will the generated script automatically continue using the shared parent-domain consent cookie (.firstcarolinabank.com)?

3

Hello @amyhynes!

At the moment, Consent Pro does not natively support implementation on non-Webflow sites, although this is on our roadmap.

To achieve a similar experience and maintain a consistent banner design across both websites, you’ve already identified the key requirement: the consent cookie is configured for cross-domain sharing, meaning the consent state is available across your subdomains as well.

Your development team can integrate with that shared consent state by reading and updating the cookie directly. Our custom integration documentation explains how to interact with the consent state and keep preferences synchronized between both websites:

https://docs.consentpro.com/v2/developer/custom-integration

Regarding the banner UI itself, this approach is not currently documented, but it is technically possible. Since your banner configuration for https://www.firstcarolinabank.com/ is loaded from the homepage, your non-Webflow site could fetch the homepage HTML, extract the element with fs-consent-element="internal-component" (which contains the banner structure), and load the associated CSS. Your team would then need to implement the JavaScript required to handle user interactions and consent updates.

It’s important to note that this approach only allows you to share the consent state and replicate the banner experience. Cookies and trackers running on http://ir.firstcarolinabank.com/ would not be automatically managed or scanned by Consent Pro, as content within that subdomain is currently outside the scope of what Consent Pro can analyze and categorize.

Please let us know if you have any questions or need clarification on the implementation approach.

4

Thank you! Our logging is also using an Endpoint URL to store consents. Would the IR site hit that data source?

5

@amyhynes You can configure your custom script to fire the IR consents to the same data source :white_check_mark:

Only the Webflow project running Consent Pro will natively forward the consents to your Endpoint URL. The non-webflow site will need custom script to replicate the same.

6

To confirm: based on the custom integration approach, we do not need an additional ConsentPro license/property or changes to our existing www.firstcarolinabank.com ConsentPro configuration to support ir.firstcarolinabank.com production implementation?

7

Hey @amyhynes! For this particular setup, no, a second license should not be required.