CYBEXO Pulse
Last updated November 20, 2026
Use Pulse to find consent setup issues visible in the HTML a website serves. A report shows which pages Pulse could read, which source rules found an issue, and what to check after a repair. You can use the public scanner with CYBEXO, another consent management platform (CMP), or a custom setup. Open the public scanner
Run a public scan
Section titled “Run a public scan”- Enter a website you own or are authorized to check. Use a hostname such as
example.comto discover pages from links and sitemaps. Use a complete HTTPS URL such ashttps://example.com/offers/to check only that landing page. - Select Scan website and keep the page open for the result. Pulse processes a new scan during the request and returns a shareable link when the report is ready. If your connection ends before you receive the link, starting again creates a separate request.
- Review Scan scope and Page inventory together. Select an affected page to see the rule, supporting details and repair guidance. Keep the original public URL if you plan to retest an exact page.
A website scan can check up to 300 pages, with a 100 MiB total download budget. Robots rules, access failures, response size, request counts and time limits can reduce coverage. Discovery covers reachable URLs. Campaign and regional pages missing from navigation or sitemaps may need an exact-page check or inclusion in your monitored inventory.
Read the report
Section titled “Read the report”| Page outcome in the public scanner | What the evidence supports |
|---|---|
| No source issues found | Pulse read the HTML and found no issue among its covered source rules. Some questions, including the order of Google commands loaded through another script, may remain open. |
| Source issue found | At least one covered source rule found an issue. Open the page details for the reason and suggested repair. |
| Couldn’t scan | Pulse could not assess the HTML. Review the reason, such as a denied request, a robots exclusion or a non-HTML response. |
| Not scanned | The page was left unchecked when the scan exhausted its data budget. Check the scan scope for other limits and omitted URLs. |
Open the page details for the recorded rule results. When Google consent order is undetermined, the HTML did not establish the sequence of the commands. Older reports may have a page outcome without individual rule results. Read that outcome at its original scope.
Source rule catalog
Section titled “Source rule catalog”Catalog 1.0 covers the pulse-source-v1 inspection method. Each finding describes the HTML Pulse could read for a particular page and scan time. Check the individual rule even when the page summary says No source issues found. For example, the page can pass its loader check while Google consent order remains undetermined.
| Rule in page details | What Pulse can establish | What to do with the result |
|---|---|---|
Page availability · site_availability |
Readable HTML passes. An observed server error can fail availability. A challenge, access restriction or timeout can leave availability unknown. | Check the reported URL, HTTP status, redirects and robots settings. Repeat the same check when access is restored. |
Google consent order · google_consent_source_order |
Pulse looks for an explicit global consent default and Google configuration in classic inline scripts. When it can establish configuration first, it records google_tags_before_consent. External containers, conditional code and missing commands can leave order undetermined. |
Check the script positions in the evidence and the published template or container. Validate the effective order and choice updates in Google Tag Assistant. |
CYBEXO loader settings ID · cybexo_settings_id_missing |
A direct cmp.cybexo.com/loader.js needs a settings ID in the tag or query string. An empty value or the placeholder UNKNOWN_SETTINGS_ID can trigger the finding. A nonempty value establishes presence only. |
Check each loader against the intended property’s published snippet. After fixing the template, rescan the exact URL. |
Direct marketing tags · marketing_tag_without_consent_signal |
Pulse looks for a covered tag embedded in the HTML and a recognized consent signal. A custom control may be invisible in source. A visible signal alone cannot establish that it controls the tag. | Inspect when the tag sends requests in a fresh browser session. If it needs consent, use your current CMP or tag manager to hold it until the visitor allows its category. Retest accepting, declining and withdrawing. |
Monitored landing page · landing_page_verification |
In a confirmed monitoring inventory, a readable page passes this coverage check even if a content rule fails. An unassessable page can leave the check unknown. | Read the individual findings on that page. Use the acquisition reason to investigate any gap. |
Saved public reports and the source issues recorded for a monitored page keep the wording from the original scan. For current repair guidance, open the finding in the CYBEXO Customer Dashboard. Scan the page again for a new observation. In the Dashboard, the Direct marketing tags and CYBEXO loader settings ID checks show repair instructions only when the individual check fails.
Recognized CMP scripts
Section titled “Recognized CMP scripts”Pulse recognizes the following script hostname and path combinations in page source. A single recognized provider can be named. If several providers match, the report flags multiple signals. A custom loader, an indirect installation or a tag added in the browser can leave the provider unidentified.
| Provider | Recognized script |
|---|---|
| CYBEXO Consent Runtime | cmp.cybexo.com/loader.js |
| Cookiebot | consent.cookiebot.com/uc.js |
| OneTrust | cdn.cookielaw.org/scripttemplates/otSDKStub.js |
| Usercentrics | app.usercentrics.eu/browser-ui/latest/loader.js or web.cmp.usercentrics.eu/ui/loader.js |
| Didomi | sdk.privacy-center.org/{key}/loader.js with an alphanumeric, underscore or hyphen key |
| iubenda | cdn.iubenda.com/cs/iubenda_cs.js |
| CookieYes | cdn-cookieyes.com/client_data/{key}/script.js with a lowercase hexadecimal key |
Covered marketing tags
Section titled “Covered marketing tags”The marketing rule recognizes Meta’s connect.facebook.net paths ending in /fbevents.js and its www.facebook.com/tr image endpoint, TikTok’s analytics.tiktok.com/i18n/pixel/ paths, and LinkedIn’s snap.licdn.com/li.lms-analytics/insight.min.js. It inspects eligible source elements. A tag delivered through a first-party proxy or external container can fall outside this scope. A site with only essential functions can legitimately have no covered direct marketing tags.
Registry dates and limits
Section titled “Registry dates and limits”A listing describes a provider on a particular reference list. When available, the raw public report includes scan.cmp_registry_version and scan.cmp_registry_updated_at. The latter is the time Pulse fetched its reference lists. Compare that timestamp with the scan time and the seven-day refresh window. The lists can change between refreshes. An older report without a fetch date cannot establish how current a badge was. Google web listing and IAB TCF listing are separate observations. Website certification, legal compliance and actual visitor behavior require different evidence. Google publisher CMP list · IAB CMP list
The public report, its CSV and Download evidence show a listing only when the supporting reference was fresh at scan time. A stale reference keeps its known date. When the date is missing or the references conflict, the report keeps the recognized provider name and explains that a dated listing is unavailable. In a new scan, a recognized provider can also carry its own snapshot identifier and fetch date. The raw API supplies membership flags only when it has a fresh reference for that page. A missing flag means unknown. Open source JSON opens the saved API response. Earlier reports can retain historical flags. Compare their original reference and scan dates before interpreting them.
Understand coverage gaps
Section titled “Understand coverage gaps”Count pages with findings separately from URLs Pulse could not assess. For example, if eight URLs are discovered, six pass, one has a missing settings ID, and one is unreadable, the scan assessed seven pages and found one failing page. Its coverage is partial. The missing settings ID is still actionable.
A fresh public report identifies its method as source_html and its target as page or site. Historical shared reports may contain browser observations, a versioned verification result, or fewer coverage fields. Use their recorded method, date and scope. A later source pass cannot establish recovery of an earlier issue observed after a visitor’s choice.
Monitor your landing-page list
Section titled “Monitor your landing-page list”For recurring checks, open Pulse → Monitoring in the customer dashboard. Select a published property, or use Independent websites and verify control of the exact hostname through DNS. Confirm the public HTTPS landing pages you want to monitor, review notification preferences, and activate monitoring. The confirmed list supports up to 500 URLs per inventory. Open the customer dashboard
Pulse checks the confirmed pages from source every four hours for eligible active monitoring. The schedule is visible in Settings. You can also run a manual check. Compare the latest result with the dates and evidence behind open findings. For a historical finding, look for the observing method, run and time. If the original observation cannot be identified, its provenance is unavailable. An older browser finding may remain open after all pages pass their current source checks. A one-time public scan creates its own report. Enrollment, recurring checks and alert delivery are managed in your account.
Verify consent and Google tag gateway
Section titled “Verify consent and Google tag gateway”When the page details identify a source defect, repair the affected template and repeat the same check. If the question concerns actual tag execution or timing after a choice, use a fresh browser session and inspect the consent default, the update after the choice and the tags that fired. For Google Tag Gateway, verify the configured domain and measurement path. Finding repair guide · Google Tag Gateway guidance · Google Tag Assistant
Public report links and privacy
Section titled “Public report links and privacy”Anyone who has the public report link can view it. New public reports expire within seven days. Use the report’s expiry time for the exact deadline. Older monitoring links may follow a different retention policy. Downloaded copies persist after expiry.
Choose a public page that anyone can open anonymously. Omit credentials, personal identifiers and signed links from the address. Pulse fetches the original URL. In the report, it replaces query values with [redacted] and masks any URL path segment containing @ or its encoded form %40, or longer than 80 characters in the encoded URL. Other path segments, query parameter names and installation details can still identify a page. Review them before sharing.
The same masking applies when you reopen an older public report or download its CSV or evidence JSON. The original observation and verdict retain their recorded values. Files downloaded earlier keep the content they contained at the time. To repeat an exact-page check from a saved report with a query or masked path, re-enter the original public HTTPS URL. To request removal, provide the report link to support. Privacy policy · Contact support
Troubleshooting and API access
Section titled “Troubleshooting and API access”If a saved link is missing or expired, you can run a new authorized scan. If a page was unreadable, check its reported HTTP status, content type and robots policy first. Developers can submit the same source checks and retrieve saved results through the public API. Public Scan API and OpenAPI download