"type": "transformation-name",
"type": "transformation-name",
// ID of the OTQL query to call
// Optional. Title of the series for tooltips and legends
// Optional. Datamart on which to run the query.
// Defaults to current datamart
// Optional. To adapt the query to the current scope
// for example by adding current segment's query
// when dashboard is executed on a segment
"adapt_to_scope": Boolean
// Optional. To run the query in a specific precision
// To be used when charts take too long to load and
// a lower precision is accepted
// Defaults to FULL_PRECISION
"precision": "FULL_PRECISION" | "LOWER_PRECISION" | "MEDIUM_PRECISION"
"type": "activities_analytics",
// JSON representation of the activities analytics query
// Optional. Title of the series for tooltips and legends
// Optional. Datamart on which to run the query.
// Defaults to current datamart
// Optional. To adapt the query to the current scope
// for example by only selecting activities of users
// that were in the segment while doing it
// when dashboard is executed on a segment
"adapt_to_scope": Boolean
"type": "collection_volumes",
// JSON representation of the activities analytics query
// Optional. Title of the series for tooltips and legends
// URI of the JSON data file containing data
// Format "mics://data_file/tenants/1426/dashboard-1.json"
// Path of the property in the JSON that should be used as dataset
// This allows you to have multiple datasets in the same JSON file
// Should use the JSONPath syntax. See https://jsonpath.com/
// For example, "$[0].components[1].component.data"
// Optional. Title of the series for tooltips and legends