When using Cookie Consent Placeholder on CMS lists utilizing Finsweet’s List Load attributes, the CMS items loaded in aren’t hiding their placeholder correctly when cookies are accepted.
Is anyone else running into this issue?
Hey @ed.pirone!
We can see what’s happening here — you’ve hit a cross-product timing issue that’s a bit tricky.
The likely cause: Consent Pro’s placeholder logic scans the DOM when the page first loads. When List Load dynamically adds new CMS items later (via load-more or pagination), those new items contain placeholder elements that Consent Pro hasn’t processed yet, so they don’t get replaced when cookies are accepted.
The good news is that Consent Pro has an API method called activateAllElements() that can manually trigger placeholder processing. The challenge is that connecting this with List Load’s rendering cycle requires some custom integration code between the two products.
Here’s what we need from you:
Could you share a read-only Webflow link or staging URL where we can see your Consent Pro + List Load setup? This will help us provide the exact integration approach for your specific implementation. 
Why we’re escalating this:
This is a cross-product scenario that isn’t covered in our standard documentation yet. While the API capability exists to handle this, we want to get you the exact implementation pattern from our team rather than guessing at the integration code.
Let us know and we’ll loop in our team to get you the right solution! 