# Guide for data teams

This guide is for analysts and data teams.

## Map your data layer

Markalit can read your tag manager's data layer.
On the **Data layer** page, choose which data layers to capture, then map your fields to Markalit's standard fields, such as `k_order_value` and `k_order_transaction_id`.
Mapped fields appear in Analytics under the same names on every site.
See [Existing tags and data layers](/docs/data-capture/existing-tags-and-data-layers).

## Tune page and click types

Review the rules Markalit proposes on the **Page types** and **Click types** pages, and confirm or turn them down.
Press **Publish** to send your changes to Analytics.
They apply to all of your history.

## Build on the explores

Markalit Analytics has 21 explores over your events, from Page views and Visits to Attribution, Cohorts and Trends.
Markalit maintains the semantic layer behind them, so metrics are defined once and mean the same thing in every chart.
See [Explores, metrics and the semantic layer](/docs/analytics/semantic-layer), which links each explore's page and its dictionary of dimensions and metrics.

## What to know about the numbers

- A visitor is one browser or device, not a person.
- Bot traffic and events without consent are left out of Analytics.
- Each query can read up to 500 MB, and returns up to 5,000 rows.
- Weeks start on Monday.