Understand connection status
Dashboard labels distinguish a completed connection from a connector that has not yet been observed on the live site.
| Status | Meaning | Next action |
|---|---|---|
| Not connected | No active pairing or the connection was revoked. | Install or generate a new connection. |
| Waiting for runtime | Authorization or pairing completed, but the live connector has not checked in. | Activate the connector, clear caches, and visit the public site. |
| Runtime connected | An active connection has a recorded runtime heartbeat. | Proceed to consent and vendor testing. |
| Action required | The remote installation or credentials need repair. | Follow the message on the integration card and reconnect if requested. |
Shopify
Connect Shopify is disabled
Review the production-readiness panel above the connection form. The server needs a client ID, client secret, valid application origin, and secure credential encryption. In production the origin must use HTTPS. See the credential setup checklist.
OAuth returns to an error page
Confirm that the configured application URL and Shopify allowed redirect URL use the exact same public origin. Check clock synchronization and do not reuse an old authorization link.
The store is connected, but no banner appears
Open the theme editor from the integration card, enable the StrongPrivacy app embed for the live theme, and save. Test in a private window after clearing storefront consent data.
The wrong property is connected
Revoke the connection, select the property whose hostname belongs to the store, then run the Shopify connection again. Never copy another property’s identifier into extension settings.
WordPress
The dashboard says Waiting for runtime
Confirm the plugin is activated and paired to the selected property. Purge WordPress, optimization-plugin, reverse-proxy, and CDN caches, then visit an uncached public page.
The dashboard says Not connected
The pairing is missing or revoked, even if an old runtime timestamp still exists in history. Generate a new pairing code and complete pairing from Settings → StrongPrivacy.
Two banners appear
Disable the banner and script injection in the previous consent plugin. Keep only one source of consent UI while compatible plugins consume the WordPress Consent API state.
Custom sites
Configuration request is blocked
Confirm the runtime’s data-site-id belongs to the selected property and that the exact page origin is allowed. Protocol, subdomain, and port are part of the origin.
A vendor loads before consent
Remove its normal executable script. Use the declarative text/plain format or register it through the browser API, and make sure no tag manager or framework duplicates the original tag.
A registered script does not load
Check the selected category, the current consent object, the unique script ID, browser Content Security Policy errors, and the strongprivacy:error event.
Clean verification run
Use this order to reduce false positives caused by stored choices or stale markup.
- Publish the current property configuration.
- Clear application, platform, CDN, and browser caches.
- Open a private browser window with the network panel recording.
- Load the site without interacting and inspect optional vendor requests.
- Test Reject all, Accept all, granular choices, reload, and withdrawal.
A runtime heartbeat is not a compliance verdict
Connected confirms that the integration is alive. It does not prove that every third-party vendor is classified correctly or that regional legal requirements are satisfied. Review scan findings and obtain appropriate legal advice for your organization.