Consent Pro + Calendly: Show alternative content when cookies are not accepted

Hi everyone,

I hope someone can help me, because I’m currently stuck with this setup.


Current behavior

  • When cookies are not accepted, the Calendly script is correctly blocked.

  • When all cookies are accepted, Calendly loads correctly.

So the basic setup works as expected.


My problem

When cookies are not accepted, there is an empty space on the page where the Calendly embed should be.

Instead of this empty space, I would like to display my regular contact form while Calendly is blocked.

Desired behavior:

  • Cookies not accepted → contact form is visible

  • Cookies accepted → contact form disappears and Calendly is shown


What I already tried

I tried to implement this using the Finsweet placeholder approach

(fs-consent-element=“placeholder”), but I can’t get it to work.

Either:

  • the placeholder stays visible all the time

  • or nothing happens at all


My questions

  1. Is it possible with Consent Pro to show alternative content (e.g. a contact form) while a script like Calendly is blocked?

  2. Is there a clear example, tutorial, or video explaining how to do this?

  3. If someone has already implemented this successfully:

    • What does the correct structure look like (placeholder / target / wrapper)?

    Thanks in advance for your help.

Hey @olivereder03!

The placeholder approach you’re trying is definitely the right way to go! This is part of Finsweet Attributes v2 functionality, not a standalone Consent Pro feature.

For this to work properly, you’ll need two main elements set up correctly:

1. Placeholder Element (your contact form):

<div fs-consent-element="placeholder" fs-consent-categories="marketing">
  <!-- Your contact form content here -->
</div>

2. Target Element (Calendly wrapper):

<div fs-consent-element="target" fs-consent-categories="marketing">
  <!-- Calendly embed code here -->
</div>

If your placeholder isn’t behaving correctly, here are a few things to check:

  • Make sure both elements have the same consent category value
  • Check that your placeholder is visible by default
  • Verify there’s no CSS accidentally hiding your elements
  • Ensure consent hasn’t already been granted (which would hide the placeholder)

A simpler approach might be to use just a basic button as your placeholder instead of a full contact form, which could simplify the implementation :thinking:

Could you share a read-only link to your Webflow project or staging URL so we can take a closer look? @Support-Luis, @Support-Pedro or @jesse.muiruri can help with any specific code adjustments if needed.