Use a custom DataLayer
Send structured business events and values from a bespoke website implementation.
Updated 9 August 2026When to use a DataLayer
Use a custom DataLayer when a bespoke website or application needs to describe events that cannot be inferred reliably from URLs alone. Incendium can use structured pageview and sales information without forcing the implementation into a generic page-only model.
A clear DataLayer preserves business meaning at the point where the event occurs—for example an application completion, qualified enquiry or subscription purchase—so later reporting and conversion rules do not have to reconstruct that meaning from fragile selectors.
Plan the contract first
- Give each event one stable business name.
- Define when it fires and whether repeat firing is valid.
- Specify required values such as amount, currency, order identifier or product.
- Use stable IDs rather than presentation text that editors may change.
- Exclude passwords, payment details and unnecessary personal information.
- Document how browser and server events are deduplicated.
Implement and connect
Write the event specification
Agree names, fields, types and examples with the website and analytics owners before development begins.
Push events at the source action
Emit the structured event when the application knows the outcome occurred, not when an unrelated visual element happens to appear.
Configure the DataLayer integration
Open Settings → Connections → Integrations, choose DataLayer and map the supported pageview or sales data required by the project.
Test positive and negative cases
Confirm the event fires once when it should, does not fire on validation errors, and carries the expected values.
Verify in Incendium
Check recent activity, the intended Location and any dependent conversion. Compare identifiers and values with the originating system. If a release changes the application flow or payload, retest the contract before relying on the affected reports.