If the banner doesn’t show or the plugin shows Not Connected (classic settings screen: Pending or Inactive), the site usually isn’t linked to your Cookie Compliance app correctly. The fix is to (1) publish your latest settings in the app, (2) paste the correct App ID and key into WordPress and click Connect Your Site (already-connected sites: Save and Connect in the Domain Info card; classic settings screen: Save Changes), so the status turns Active.
What you need
- Access to the Cookie Compliance application (dashboard).
- Access to your WordPress admin with the Cookie Compliance for WordPress plugin installed.
Quick fix (most cases)
- Publish your latest settings in the app
A domain you add in the Cookie Compliance dashboard is published when you add it. After you change settings, open the application → Configuration → Publish Now for the correct domain/workspace. - Copy your App ID / App Secret Key
In the app, go to Integrations (left sidebar) and copy the App ID and App Secret Key for this site. - Paste into WordPress and save
In WordPress, open Compliance. On a site that isn’t connected yet, open the Overview tab, enter them in the App ID and App Secret Key fields and click Connect Your Site. On a site that is already connected, use the App ID and App Secret Key fields in the Domain Info card and click Save and Connect (classic settings screen: Save Changes).
After saving, the status should switch to Active and the banner should display for anonymous visitors.
Symptoms and what they mean
- Classic settings screen shows Pending
Onboarding didn’t finish or the domain isn’t published yet. Publish in the app, then click Save Changes on the classic settings screen. - WordPress shows “Not Connected” (classic settings screen: “Inactive”)
WordPress doesn’t have a valid link to your app (missing/incorrect App ID or Key) or the connection needs a refresh. Paste the correct values: on a site that isn’t connected, use App ID and App Secret Key on the Overview tab and click Connect Your Site; on a connected site, use the Domain Info card and click Save and Connect (classic settings screen: Save Changes). - The WordPress setup keeps asking you to Sign In
You may be logged into a different account than the one that owns the app for this domain. Confirm you’re using the right email, or register/log in directly in the application (not via WP onboarding) and link the site with the correct App ID and App Secret Key. - Banner used to show; now it’s gone
Re-publish in the app and click Pull latest settings in the Domain Info card (connected sites only; the classic settings screen has the same button) to refresh the handshake. This resolves most “it worked before” cases.
Find your App ID / App Secret Key (exact place)
- Application → Integrations → select the site/app → copy App ID and App Secret Key.
- Paste both into WordPress → Compliance. On a site that isn’t connected yet, open the Overview tab, enter them in the App ID and App Secret Key fields and click Connect Your Site. On a site that is already connected, use the App ID and App Secret Key fields in the Domain Info card and click Save and Connect (classic settings screen: Save Changes).
Tip: If you manage multiple domains, double-check you copied the keys for the correct property.
If the status doesn’t turn Active
Work down this list in order:
- Confirm the account
Make sure you’re logged into the same app account that owns the site. If you can’t find the property, you might have registered with a different email. Log in with the correct account or register in the app and onboard the site there. - Re-publish + re-save
Click Publish Now in the app, then immediately click Pull latest settings in the Domain Info card (connected sites only; the classic settings screen has the same button) to refresh the link. - Re-paste keys
Remove any extra spaces when pasting the App ID or App Secret Key. Save again.
Verify it’s working
- In WordPress: after Connect Your Site or Save and Connect, the Domain Info card shows Protection: Active (classic settings screen: the statuses show Active after Save Changes).
- On the site: the banner appears on first visit; DevTools shows our inline init and
//cdn.hu-manity.coloader at the top of<head>.
Was this article helpful?
YesNo