Cookie notice exclusions

Last Updated: 13 September 2026 Hits: 22

Hide the initial notice only on specific pages

Alamarte Cookie Consent Pro allows you to define pages where the initial consent notice should not be displayed. Exclusions can be configured using the Joomla! Itemid or site paths.

An exclusion only hides the initial notice.

Excluding a page does not disable Alamarte Cookie Consent Pro. The consent engine continues to operate and saved preferences, the persistent Cookie settings control, tagged content processing and the JavaScript API remain available.

Exclude using Itemid

You can enter the exact Joomla! Itemid corresponding to the page you want to exclude.

The value must be a positive integer.

Example:

In this case, the initial notice will not be displayed when the page has exactly that Itemid.

Exclude using a path

You can also enter an internal site path. The path must always begin with /.

Example:

/privacy-policy

Without a wildcard, the match must correspond exactly to the specified path.

Exclude a group of paths

The * wildcard can be used at the end of a path to include pages located under that prefix.

For example:

/blog/*

This rule applies the exclusion to paths beginning with /blog/.

One rule per line

Enter each exclusion on a separate line.

Itemid values and paths can be combined within the same configuration.

125
218
/privacy-policy
/terms-and-conditions
/blog/*

Exact path matching

When a path does not contain *, Alamarte Cookie Consent Pro uses an exact match after normalising the trailing slash.

For example, these two forms are treated as equivalent:

/legal
/legal/

A rule for /legal does not automatically exclude different paths such as /legal/privacy. To include additional paths, use a rule that explicitly matches them.

Do not use full URLs

Path exclusions should be entered as internal paths rather than complete addresses.

Do not use:

https://example.com/legal

Use:

/legal

Unsupported values

Do not use query strings, URL fragments or regular expressions within exclusion rules.

* or /* by themselves are also not valid rules.

Preferences remain active

If the visitor already has saved preferences, they continue to apply on an excluded page.

Excluding a page does not delete or reset existing consent.

Tagged content remains protected

Content configured using Alamarte Cookie Consent Pro categories continues to respect the current consent state even when the page is excluded from the initial notice.

Excluding a page does not automatically make its optional content authorised.

Remember: exclusions are designed to control where the initial notice appears, not to disable the consent system. If you need to control the loading of specific content, use the blocking features and the corresponding consent categories.