CookieYes URL pattern limitation for Checkout Modal

If you use CookieYes with Fundraise Up's Checkout Modal, configure it carefully. In some CookieYes setups, non-necessary cookie categories are controlled through script URL pattern rules. That approach can create a limitation for Fundraise Up because the same script both loads the checkout experience and sets Fundraise Up cookies.

This issue has been observed with CookieYes configurations that control Fundraise Up at the script URL level. If CookieYes blocks the Fundraise Up script when a donor rejects an optional cookie category, it may block more than cookies alone. In some cases, the Checkout Modal or embedded donation elements may stop loading altogether.

Why this matters

The same Fundraise Up script loads checkout and sets Fundraise Up cookies. Blocking that script to suppress optional cookies can therefore prevent donors from opening or using the Checkout Modal.

If you continue using CookieYes

If you continue using CookieYes without the GTM Consent API, categorize fundraiseup_cid as strictly necessary. Other Fundraise Up cookies should retain their documented categories. Because CookieYes may block the entire Fundraise Up script when applying consent through URL patterns, confirm the implementation with your legal or compliance team and test checkout carefully.

Test checkout after setup

Before publishing your banner changes:

  1. Reject all optional cookie categories.
  2. Open the Checkout Modal and any embedded donation elements.
  3. Continue through checkout far enough to confirm that the donor journey works normally.
  4. Repeat the test after accepting each consent option your banner provides.

Checkout should work whether optional cookies are accepted or rejected. If it works only after all categories are accepted, check whether CookieYes is blocking the Fundraise Up script or related resources.

Still need help?

Need help with something not covered in Support Center? Connect with a support engineer for more assistance.
Email us