Script catalog

The script catalog is where you list the third-party scripts running on a site and tag each one with a consent category. You manage it per site at /settings/sites/[id]/consent/scripts. As the page itself puts it: "Register 3rd-party scripts and assign them a consent category. Pulse will block registered scripts until the visitor grants the matching category."

Open the catalog from the Scripts tab of a site's Consent settings. You can also reach it from the Cookie scan results, where any recognized vendor that is not yet in your catalog shows an Add to catalog link back to this page.

Registering a script

Click Add script (in the toolbar above the table, or in the empty state). A dialog titled Add script opens with these fields:

• Name — a label for the script, for example Google Analytics 4. Required, up to 255 characters. A blank name returns "Name is required".
• Script URL — the full URL of the third-party script, for example https://www.googletagmanager.com/gtag/js?id=G-XXXXX. Required. It must be an absolute https:// URL (up to 2048 characters); http:, protocol-relative, and other schemes are rejected with "Script URL must be an absolute https:// URL".
• Consent category — one of Analytics, Marketing, or Personalization. The category is what the visitor's consent choice is matched against. Defaults to Analytics.
• Active — include in embed payload — the toggle that controls whether this entry is sent to your CMP snippet. On by default.

Click Add script in the dialog footer to save, or Cancel to discard. The catalog is ordered oldest-first, so a new entry appears at the bottom of the table.

Reading the catalog table

Once you have at least one entry, the catalog renders as a table with five columns: Name, Source URL (shown in monospace, truncated with the full URL on hover), Category, Active, and Actions. The toolbar above the table shows the script count and the Add script button.

The Active column shows an Active or Inactive badge. Each row's Actions column holds an edit (pencil) and a delete (trash) button.

Before you register anything, the page shows an empty state titled No managed scripts yet with its own Add script button.

Editing and removing entries

The pencil button on a row reopens the same dialog, now titled Edit script and pre-filled with the entry's values. Change any field and click Save changes.

To stop a script being sent to your snippet without losing the record, edit it and turn off Active — include in embed payload. Inactive entries are excluded from the catalog payload your CMP reads, so the script is not injected on the next page load.

The trash button removes an entry. It first asks for confirmation — "Remove "[name]" from the script catalog? This soft-deletes the entry." The removal is a soft delete, so the row leaves the table but the underlying record is retained rather than erased.

How the catalog reaches your site

Your CMP snippet (pulse-cmp.js) fetches the active catalog for the site it is installed on. Only entries that are active and not removed are included, and each entry carries its name, source URL, and consent category. The snippet then injects each script onto the page only after the visitor grants its category. That payload is cached at the edge for 60 seconds, so a toggle or removal you make in the dashboard takes effect on the next page load within roughly a minute.

Injection is one-way: once a script has loaded for a visitor, a later consent downgrade or catalog change applies on their next page load rather than mid-session. For the snippet to be present, install the CMP script on the site first. See Sites for the snippet tags, and Consent banner for the banner a visitor uses to grant or decline each category.