Collection Points

A collection point is one place where you collect consent, usually one website domain. It is the unit you configure and publish. Everything a visitor sees on that site, and everything Neostra records about their choice, flows from it.

Open Consent Management > Collection Points. Filter the cards by Status (Active or Archived), sort by name or creation date, and click Customize to open the builder.

Create a collection point

Click Add New and fill in the drawer:

Click Add. In the builder, Edit Collection Point shows the Details card with these fields plus Version Name, and an Edit button.

Draft, Publish, and Discard Draft

Your first change in the builder creates a draft. While a draft exists the header shows Discard Draft and Publish. Visitors keep seeing the last published version until you publish. Both buttons act immediately without a confirmation step, so review the draft first.

Each publish adds an entry under Published > Published History with the version name, date and time, and publisher, and a Latest chip on the newest. There is no rollback; to revert, change the configuration and publish again.

Banner Configuration > Banner

Geolocation Configuration is always shown. Tracking Services and Translations appear once a default banner is selected.

Geolocation Configuration

Under Default Banner, click Edit, pick a banner, and Save. It is served when no jurisdiction rule matches. Without one, the collection point cannot serve a banner.

Under Jurisdiction Rules, click Add Rule to map a Regulation to a Banner. Regulations and the countries or states they cover are managed under Settings > Regulations. When the script loads, Neostra looks up the visitor's country and region from their IP address, finds the regulations that cover it, and serves the banner from the first matching rule in Priority order. Use the arrows to reorder. If nothing matches, or the location cannot be determined, the default banner is served. Each row has preview, edit, and delete actions; deletion is immediate.

Tracking Services

Manage Categories lists the consent categories visitors choose between. Click Add Category:

• Key: lowercase letters, numbers, and underscores only, for example analytics. Unique within the collection point and used in consent signals.
• Name and Description: what the visitor reads. Both are translatable.
• Consent role(s): Essential, Functional, Analytics, Advertising, or Data sharing. Tells the platform how to treat the category in consent signals.
• Required: always on; the visitor cannot switch it off.

Click Reorder, drag categories into banner order, and Save Order. Deleting a category removes it from every service that used it.

Manage Tracking Services lists the cookies, scripts, and iframes on your site. Click Add Service to enter one manually: Vendor Name, Purpose (translatable), Domain, Type (Cookie, Script, or Iframe), Duration (days) for cookies where 0 means a session cookie, and one or more Categories.

Or click Start Scan to crawl the collection point domain. Scans run only when you start one; the button reads Scan in progress while it runs. Results appear under Scan History, and Scan Summary shows Security, Performance, and Privacy scores, Pages Crawled, Scan Duration, and counts of Cookies, Scripts, Iframes, and Sub URLs. Services from the latest finished scan join the list, with a proposed category where the scanner recognised them.

To confirm a service it needs a vendor name, a purpose, and at least one category; then click Confirm. Changing categories on a confirmed service turns the button into Re-confirm. Select several rows to confirm them together. Only confirmed services reach the banner, under the categories they are assigned to.

Translations

A Translation Progress bar sits above two sub-tabs. Categories covers Category Name and Category Description; Tracking Services covers Tracking Service Purpose for confirmed services. Vendor name, domain, type, and duration are not translated. Target languages come from the default banner's Language Settings. If the banner has only its default language, the tab shows Translations Unavailable with a Manage Languages link.

Banner Configuration > Signals

Signals run in the visitor's browser after each consent decision. Each of the four cards shows Enabled or Disabled, an information popover, and Edit. Changes go to the draft; publish to make them live. The browser side of each signal is in the Cookie Consent Modal guide.

Banner Configuration > Webhooks

Webhook Rules fire when a banner submission matches your conditions. Click Add Rule, join one or more conditions with All or Any, and add one or more actions.

Conditions: Accepted All, Rejected All, or Specific Category with Accepted or Rejected.

Actions:

• Call API: choose an API Configuration Name from Settings > API Configuration, where the endpoint and authentication live. Add optional Headers and a JSON Request Body. The receiving side is described in Webhooks.
• Send Email: Recipients, optional CC, Subject, and Body. Banner consent is anonymous, so there is no option to email the data subject.

Variables available in headers, body, subject, and email body: {{tenantId}}, {{collectionPointId}}, {{subjectId}}, {{receiptId}}, {{submittedAt}}, and {{consentChoices}}, a list of category keys with ACCEPT or REJECT.

Preference Center

Attach a published preference center so signed-in data subjects can manage their choices. Click Edit, search under Preference Center, and under Determine Regulation tick Geolocation to detect the applicable regulation from the visitor's location, User Choice to let the visitor pick, or both. The Webhooks entry in this section mirrors banner webhooks, with a Specific Preference condition (Opted-In or Opted-Out), a To the data subject email option, and extra variables such as {{email}}. Preference centers are a plan feature; without them this page shows an upgrade notice.

Attributes

Attributes add context to each consent record. Click Add, enter a Name, and pick a Category:

For the first four, the Key is derived from the name and becomes the field name in the consent payload.

Integration > Scripts

Scripts is the developer hand-off. Until the collection point is published it reads Please Publish Collection Point. Under Banner, copy the script tag and give it to your developer to place on every page. Under Preference Center, copy the public URL to link from your site. An Integrity protected chip means the snippet carries a subresource integrity hash, so browsers refuse a tampered copy of the script. Placement, events, and the JavaScript API are in Cookie Consent Modal.

Preview

Click Preview next to the default banner, or the eye icon on a jurisdiction rule, to open Banner Preview. It renders the current draft with your confirmed services, switching between Layer 1, the first screen, and Layer 2, the detailed category view.

Active and Archived

From a card's menu, choose Archive to retire a collection point or Activate to restore it. Archived collection points cannot be customized. Archiving is separate from publishing and creates no version.