Properties & Domains

A property in eConsent represents a website or application where you capture consumer consent.

Each property has its own domain whitelist, field capture settings, consent selector mappings, and expiration configuration.

Property configuration

Each property includes the following settings:

Setting	Description
Name	A friendly name for the property (e.g., “Main Website”, “Landing Page A”)
Origin	The whitelisted domain URL (e.g., https://example.com)
UID	A unique identifier assigned by eConsent
Masked fields	CSS selectors for additional fields to capture (values are hashed)
Consent selectors	Mapping of consent types to CSS selectors on the page
Session expiration	How long session recordings are retained
Certificate expiration	How long certificates are retained

Creating a property

1. Log in to app.econsent.org.
2. Navigate to Properties.
3. Click Add Property.
4. Enter the property name and origin domain URL.
5. Save the property to receive your unique Property ID.

Domain whitelisting

The tracker validates its origin against your property’s registered domain before activating. This prevents unauthorized websites from using your Company ID and Property ID to generate certificates.

How origin verification works

When the tracker script loads on a page, it performs the following verification:

1. The tracker sends a POST /api/verify-origin request with the page’s origin (e.g., https://example.com) and your company_id.
2. The server performs a Redis lookup: origins:{origin}:{company_id}.
3. If the origin matches a registered property, the tracker activates and begins recording.
4. If the origin does not match any registered property, tracking does not activate. No sessions or certificates are created.

Caution

The origin must match exactly. If your property is registered with https://example.com, the tracker will not activate on https://www.example.com or http://example.com. Register all domain variations as separate properties or ensure your site redirects to a canonical URL.

Updating a property’s origin

To change the whitelisted domain for a property:

1. Navigate to Properties in your dashboard.
2. Select the property to edit.
3. Update the Origin field with the new domain URL.
4. Save. The change takes effect immediately.

Masked fields

Masked fields are additional form fields that eConsent captures beyond the default core PII fields. Values from masked fields are hashed before storage and are never stored in plain text.

Masked fields are defined as CSS selectors on the property configuration. You can set them in two ways:

1. Whitelist Inspector. Use the visual Whitelist Inspector tool to click elements on your page and generate selectors automatically.
2. Manual configuration. Enter CSS selectors directly in the property settings.

Example masked field selectors:

#ssn-field
input[name="annual_income"]
.loan-amount-input

Consent selectors

Consent selectors map HTML elements on your page to eConsent’s four consent types. These can be configured in two ways:

1. Consent Selector tool. Use the visual Consent Selector in the dashboard.
2. HTML attributes. Add data-consent-type attributes directly to your HTML elements.

The four consent types mapped by selectors:

Type	CSS selector maps to
main-implied	Primary consent language paragraph/text
main-explicit	Primary consent checkbox or interactive element
secondary-implied	Secondary/partner consent language
secondary-explicit	Secondary consent checkbox

Expiration settings

Both session recordings and certificates have configurable expiration periods, set independently per property:

Duration option	Use case
7 days	Testing and development
30 days	Short-term campaigns
60 days	Standard campaigns
1 year	Extended compliance
3 years	Long-term retention
5 years	Maximum retention for litigation protection

Note

TCPA claims can be filed up to 4 years after the alleged violation. For full litigation protection, set both session and certificate expiration to 5 years.

To configure expiration:

1. Navigate to Properties in your dashboard.
2. Select the property.
3. Update the Session Expiration and Certificate Expiration settings.
4. Save.

Usage tracking

Each property tracks usage metrics that are visible in the dashboard:

Metric	Description
Session count	Total number of sessions recorded
Certificate count	Total number of certificates generated
Verification count	Total number of verification API calls

These metrics are available per property and aggregated across your account.

Multiple properties

You can create multiple properties under a single company account. Common use cases:

• Multiple websites. One property per domain
• Staging vs. production. Separate properties for different environments
• Landing page variants. Track consent separately for A/B test pages

Each property has its own independent configuration (whitelist, consent selectors, expiration). Changes to one property do not affect others.

Managing Properties and Domains

Walk through creating a property, configuring domain whitelisting, setting retention policies, and viewing usage metrics.

~3 min

Next steps

• Script Installation. Install the tracker on your property’s website
• Whitelist Inspector. Visually select fields to capture
• Consent Selector. Map consent types to page elements
• Retention Management. Configure retention quotas and auto-retention