General Project Settings

Understand the three settings tabs

These settings can change how data is collected or interpreted. Record material changes and test them deliberately rather than treating the page as a collection of display preferences.

General settings

• Project name is the label users see when choosing the project.
• Project timezone overrides the client timezone and determines how activity is assigned to dates and hours in reporting.
• Currency Symbol controls the currency presentation used in reports; it does not convert underlying monetary values.
• Overview provides a short description of the business and project context.
• Primary Domain identifies the main website measured by the project.
• Sub Domains adds other measured domains. Use Add Subdomain for each additional entry.
• Enable Cross Link should be used where a journey needs to remain connected as visitors move between managed domains. Test the complete path after enabling it.

Choose Update Project to save changes made on the General tab.

Advanced: project type and data capture

Project Type can include Ecommerce, B2B, Recruitment or another available type. It affects the analytics, tagging options and features shown for the project, so describe the business model accurately.

Advanced: Meta, retention and analysis

• Facebook / Meta Pixel stores the Pixel ID from Events Manager and unlocks Incendium options that push selected data to Meta.
• Retention — Max Chance sets the maximum predicted conversion chance below which a lead can be considered at risk.
• Retention — Lifetime sets the months since the last visit after which a lead is treated as inactive.
• Retention — Grace Period sets the months after a transaction during which inactivity is ignored before the customer is considered at risk.
• Analyse controls whether the Awareness, Acquisition and Retention insight block appears in reports. It relies on the relevant Reserved Traffic Buckets.

Retention thresholds encode the organisation's commercial definition of risk. Review them against the real repurchase cycle instead of copying values from another business.

Advanced: Custom UTM Mapping

Custom UTM Mapping tells Incendium which query parameters represent Source, Medium, Campaign, Content or Ad Set, Term or Ad, and optional campaign, group and advert identifiers. Incendium checks the mappings until it finds the applicable provider or catch-all configuration.

Default mappings are read only. Add a custom provider mapping only when the publisher uses a different parameter scheme. An incorrect mapping can fragment or mislabel campaign reporting, so validate it in UTM Explorer and Traffic Audit after saving.

Compliance & Consent

These controls are intended for implementations where the cookie banner or consent-management platform does not block the Incendium script before it loads. A conventional blocking banner may not require changes here.

This documentation explains product behaviour, not the lawful basis for a particular organisation. The organisation remains responsible for its consent and privacy configuration.

Choose how consent is captured

Auto-detect supports IAB TCF v2 and Google Consent Mode v2. In the supported mapping, purpose 8 or analytics_storage enables pageviews and Conversions; purpose 7 or ad_storage additionally enables Meta CAPI behaviour.

inc('consent_update', { analytics_storage: 'granted', ad_storage: 'denied' });

Manual values must be granted or denied. Until the first manual update, the tag does not record a pageview.

Choose the no-consent behaviour

Save changes applies the Compliance & Consent configuration. Test consent granted, consent denied and consent unknown states after any change, including Meta delivery where relevant.