Skip to main content

I’m running into an issue when trying to suppress the GDPR banner for rescheduling events using the embedded widget integration.

Calendly documentation indicates the GDPR cookie banner can be hidden using the “hide_gdpr_banner” GET parameter when calling the embedded popup integration. However, the banner still appears when I have the parameter set in the URL. 

The parameter is working correctly for embedded popup widgets to create an event and to cancel an event, but doesn’t work for rescheduling.

Is this a bug in the Calendly integration?

Hi @Travis16241!

Thanks for reaching out on this! Could you tell me a little more on what you’re running into? As I’m understanding, the parameter is working for the embed code, however, when attempting to reschedule events from your account or Calendly directly, the cookie popup still appears - Is that correct? Let me know so I can dig into this further for you.


Hi @David ,

Yes, that’s correct. When I trigger the popup widget using the reschedule URL and include the “hide_gdpr_banner” parameter, the cookie popup still appears. 

 

Including the same parameters for scheduling a new event or canceling an event, the cookie banner does not appear when the “hide_gdpr_banner” parameter is set to true.

Thanks for your help!

Travis


Hi @Travis16241,

Thanks again for confirming. I’ll take some time to look into the further from here - Could you share a snippet code you’re using or the webpage you have this embedded currently? I’ll get back once I have more info from my end. 

Thanks!


<button class="btn btn-primary" onclick="Calendly.initPopupWidget({url:'https://calendly.com/reschedulings/f1c98405-f32f-4595-b989-b98b0ede5f1d/?hide_gdpr_banner=1'});return false;">Reschedule meeting</button>

This the HTML and JavaScript I’m using to invoke the popup widget. The event referenced in this code snippet is a test event for development purposes. 


Hi @David,

 

I’m just checking in to see if you happened to learn more about this issue?

 

Thanks!


Hey ​@Travis16241! Thanks for reaching out again.

Apologize for the delay, we’re digging into this a bit further to figure out where this issue is coming from. I’ll reach out again once we have an update.

Thanks for your patience Travis!