Skip to content
Pilar BKK

Data Trust

Data Trust concerns the definitions, quality checks, ownership and access decisions behind marketing information. The aim is to make it clear what a report represents and who is responsible for maintaining it.

Making reporting data reliable enough to use

A number can be technically correct and still be misleading if its definition is unclear. A purchase might include cancelled orders; a lead might count multiple submissions from the same person. Documenting these choices is part of building a useful reporting system. The review should cover the information needed for the agreed purpose, how it moves between systems and who may view or change it. Product configuration and company procedures both contribute to reliable handling.

How the workflow is structured

Use these points to define the requirements and responsibilities for your setup.

  1. Define and document

    Keep a shared reference for events, measures, source systems and any exclusions. Record changes so a definition update is not mistaken for a performance shift.

  2. Check incoming data

    Look for missing periods, unusual volumes, duplicate identifiers and unexpected changes in values. Decide which issues require investigation before reporting continues.

  3. Assign responsibility

    Name the team responsible for collection, business definitions and corrections. Agree how an issue is reported and how its resolution is communicated.

  4. Review access

    Give people the access their role requires. Include account changes, offboarding and connected tools in the review, alongside the data itself.

Illustrative example

Investigating an unexpected conversion increase

A website release is followed by a sharp rise in recorded enquiries. A review finds that the confirmation event now fires twice. The team corrects the collection rule, documents the affected period and makes the limitation visible in reporting.

Questions for your technical team

A useful discussion covers data sensitivity, hosting expectations, retention, access, connected vendors and incident responsibilities. Confirm the applicable requirements, controls and contractual responsibilities for the proposed setup during technical review.

Discuss your data requirements

Share the business question and the systems involved. We can work through the requirements and define a suitable next step.