Developer
User guidesDeveloper websiteHelp centerLog in
  • Welcome!
  • Organisations structure
    • Datamart
    • Users and roles
  • User points
    • User identifiers
      • Networks IDs
        • Device-based Network IDs
          • Custom Device ID integration
          • ID5
          • First ID
        • User-based Network IDs
          • Custom User ID integration
          • UTIQ martechpass
      • Accounts
      • Emails
      • Device identifiers
    • User activities and events
    • Compartments
    • User profiles
    • User segments
    • Hyper point & Quarantine
  • Data model
    • Defining your schema
    • Computed fields
      • Concepts
      • Setup
      • Development
      • Examples
  • Data ingestion
    • Real time user tracking
      • Website tracking
      • Mobile apps tracking
      • Ads exposure tracking
      • AMP tracking
      • Conversions tracking
      • Email views and clicks
      • Tracking API
      • Event rules
      • Activity analyzers
    • Bulk processing
      • Imports
        • User activities import
        • User profiles import
        • User choices import
        • Segments import
      • Deletions
        • User identifiers deletion
        • Device points deletion
        • User points deletion
      • User identifiers association
      • Integration batch
    • Activities analytics
    • Data warehouse
      • Preliminary setup
        • BigQuery
      • Create data warehouse
  • Querying your data
    • OTQL queries
    • OTQL examples
    • GraphQL queries
    • UserPoint API
    • User activities
    • Activities analytics queries
      • API Quickstart
      • Dimensions and metrics
      • Use cases
    • Funnel API
  • Alerting
    • Alert configurations
  • Data visualisation
    • Quickstart
    • Dashboards
    • Sections and cards
    • Charts
    • Datasets and data sources
      • Using a data file data source
    • Transformations
    • Filters
    • Cookbook
    • Reference
  • Advanced usages
    • Audience segmentation
      • Audience features
      • Segment builders
      • Audience segment metrics
      • Audience segment feed
        • Building new feeds
        • Monitoring a feed
        • Curated Audiences (SDA)
      • Edge segments
      • Cohort-based Lookalike
    • Contextual targeting
      • Setup
      • Activation
        • Google Ad Manager
        • Xandr (through prebid.js)
      • API documentation
    • Exporting your data
      • Query Exports
      • Datamart replication
    • Data privacy compliance
      • User choices
      • Cleaning rules
      • Exercise of user rights
      • Cookies
    • Campaigns
    • Automations
      • Email routers
      • Email renderers
      • Opt-in provider
      • Custom action plugins
      • Usage limits for automations
    • Plugins
      • Concepts
      • Creation & Deployment
      • Coding your plugin
      • Manage existing plugins
      • Layouts
      • Presets
      • Monitoring
      • Throttling
      • Batching (for external feeds)
    • Platform monitoring
      • Resources usage
        • Dimensions and metrics
      • Collection volumes
        • Dimensions and metrics
      • Events ingestion monitoring
        • Dimensions and metrics
    • Data Clean Room
      • Bunker
      • Clean room
  • Resources
    • Tutorial: Data Ingestion
      • Your first events
        • Add the mediarithmics tag
          • Getting the tag
          • Adding the tag
        • Send events using the tag
          • Adding event properties
          • Finding the UserEvent type in your schema
          • Matching your schema
          • Standard events
      • Your first bulk imports
        • API basics
          • Authentication
          • Your first API call
        • Send documents using the API
          • Requirements
          • Sending documents
    • Using our API
      • Authentication
    • Tools & libraries
      • mics CLI
      • JS Tag
      • Plugin SDK
    • Data cubes
      • Creating a report
      • Reference
Powered by GitBook
On this page
  • Quickstart
  • Measure
  • Retention
  • Supported dimensions and metrics
  • Learning more about data cubes

Was this helpful?

Export as PDF
  1. Advanced usages
  2. Platform monitoring

Collection volumes

PreviousDimensions and metricsNextDimensions and metrics

Last updated 11 months ago

Was this helpful?

This page shows you how to get started using the collection volumes mediarithmics API to query the number of elements indexed in mediarithmics.

For each datamart collection, you can get the number of elements which were indexed at a given time.

This API is a mediarithmics and works similarly as .

Quickstart

POST https://api.mediarithmics.com/v1/platform_monitoring/collections

Request Body

Name
Type
Description

metrics*

array

dimension_filter_clauses*

object

dimensions*

Dimensions to group metrics by.

date_ranges*

array

{
    "status": "ok",
    "data": {
        "report_view": {
            "items_per_page": 100,
            "total_items": 7,
            "columns_headers": [
                "date_time",
                "datamart_id",
                "collection",
                "count"
            ],
            "rows": [
                [
                    1637931755000,
                    9999,
                    "USER_POINT",
                    100
                ],
                [
                    1637931755100,
                    9999,
                    "USER_EVENT",
                    50
                ]
            ]
        }
    }
}
{
    // Retrieve the data in the specified date range
    // Mandatory
    // Tip : you can use relative date formats such as "now-7d/d"
    "date_ranges": [
        {
            "start_date": "2021-10-10T00:00:00",
            "end_date": "2021-10-25T23:59:59"
        }
    ],
    // List of dimensions to retrieve
    "dimensions": [
        {
            "name": "date_time"
        },
        {
            "name": "community_id"
        },
        {
            "name": "collection"
        }
    ],
    // Filters on dimensions
    "dimension_filter_clauses": {
        "operator": "AND",
        "filters": [
            {
                "dimension_name": "community_id",
                "operator": "EXACT",
                "expressions": [
                    100
                ]
            }
        ]
    },
    // List of metrics to retrieve
    "metrics": [
        {
            "expression": "count"
        }
    ]
}

Measure

Hereunder is a description of the queries we use to compute the volumes.

Collection name
OTQL query

UserPoint

SELECT @count{} FROM UserPoint

UserAccount

SELECT @count{} FROM UserAccount

UserEmail

SELECT @count {} FROM UserEmail

UserAgent

SELECT @count {} FROM UserAgent

UserProfile

SELECT @count {} FROM UserProfile

UserActivity

SELECT @count {} FROM UserActivity

UserEvent

SELECT @count {} FROM UserEvent

UserSegment

SELECT @count {} FROM UserSegment

UserChoice

SELECT @count {} FROM UserChoice

UserScenario

SELECT @count {} FROM UserScenario

Retention

These aggregated stats are kept for two years.

Supported dimensions and metrics

Learning more about data cubes

Array of to retrieve.

Filters to apply on dimensions before calculating the metric. For more information, see .

to group metrics by.

Periods to analyze. Each date range is an object with a start_date and an end_date. See .

Here is a sample body payload with all the important properties:

Collection counts are retrieved every day through OTQL queries, for each indexed collection. A collection is indexed if it is in your schema. Volumes for non indexed collections are not computed. For more information on collections indexing, see .

The OTQL query is automatically adapted in case the runtime schema is using the .

See for the complete list of supported dimensions and metrics.

This endpoint is a mediarithmics . You can find documentation on how data cubes work and which are available in the specific documentation section.

Data cube
Activities analytics queries API
Data model
Dimensions and metrics
Data cube
Metric
FilterClause
Dimensions
DateRange
report request
@Mirror directive