Skip to main content
Notes on specific parameters of each event:
  • Event Type: Select one of the configured input types for the project
  • Date Range: Start and end date of the event
  • Tracking ID (optional): This field can be used to specify an external reference ID for the event, which the production models can use when processing the data. For example, the invoice/weighbridge number of a delivery can be captured as the event’s Tracking ID.
  • Locations: Choose the origin and destination for the trip from the project’s locations, or add a new location from either dropdown. Mangrove maps the route between the two and, with Update distance and attach route map as evidence ticked, fills in the event’s distance data point and attaches a route map as evidence. This field appears on event types with Requires locations enabled; see Track transport events.
  • Add Evidence (optional): You can optionally add multiple files or URLs to an event to provide evidence for the events tracked.

​
Adding Evidence

Evidence serves as supporting documentation to back up the data collected and reported to auditors. Auditors can review this evidence to determine the accuracy of your reporting and validate the claims made in your events.

​
Evidence Types

Evidence can be provided in two formats:
  • Files: Upload physical documents, images, videos, or other file types directly to the event
  • URLs: Provide links to external resources or documents hosted elsewhere

​
Supported File Types

The platform supports a wide range of file formats for evidence uploads: When adding evidence, ensure that your files clearly support the data and claims made in your event. High-quality, relevant evidence will help streamline the verification process and build trust with auditors.
If your project has Evidence Checks enabled, uploaded evidence will be automatically checked against your datapoint values using AI. You’ll see validation results directly on each datapoint.