Session

For example, someone from Bergquell Mineralbrunnen reaches your website through a link on LinkedIn in the morning and reads the pricing page, a product page, and the contact page. That makes one session with three page views.

If the same person reads on in the afternoon, a second session starts. On the product pages of these docs, a session is called a visit.

When a session startsCopy Anchor Link

Webmetic starts a new session in these cases:

• A visitor views a page for the first time that day.
• More than 30 minutes have passed since their last page view.
• A new day begins, counted in UTC. In Germany that is at 1 a.m. in winter and 2 a.m. in summer.
• The page address carries campaign parameters such as utm_source or a click ID such as gclid, and the source or medium differs from the previous page view.

For the campaign rule, a direct visit and a link from your own website don't count as a change. After 30 minutes or on a new day, a direct visit does start a new session.

Signals sent when someone leaves a page, for example about scroll depth, don't count as page views.

A session belongs to exactly one visitor, one website, and one Webmetic account. Subdomains such as shop.your-website.com count as the same website as your-website.com. No session runs past midnight UTC.

The API only returns sessions that Webmetic has assigned to a company. Visits after an opt-out are also missing, and so are new visits from companies you exclude with the domain blacklist or the organization types. Earlier visits of these companies stay in the API.

A session keeps its session_id when more page views are added later, so store sessions with the session_id as the key and overwrite existing entries.

FieldsCopy Anchor Link

Source, medium, campaign, and click ID apply to the whole session and come from its first page view. For details, see Campaigns and channels.

Page viewsCopy Anchor Link

The page views of a session are in user_data, a list of objects. Each object describes one page view with its address, title, time, and events. All fields are listed under Page View.

A session has no field for the number of its page views, so count the entries in user_data instead.

/session returns no page views. For those, use /session_user_data, which has one row per page view. Each row carries the session_id that links it to its session.

Fields per endpointCopy Anchor Link

In webhook deliveries, timestamps carry a Z; in API responses they don't. What sets the three visit types apart is described under Visit types.

ExampleCopy Anchor Link

The visit started on https://your-website.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=messe-2026 and had three page views.

{
  "company_id": "41ea486a9c95",
  "company_name": "Bergquell Mineralbrunnen GmbH",
  "session_id": "01M4WQFX6YM2X5V8T4N6R1C0DZ",
  "client_id": "14e382cf709a614559666137b3d1dfcefa99b1e7ecf93400cc9e2cc4822619d3",
  "timestamp": "2026-10-14T08:12:05.214000",
  "weburl": "https://your-website.com",
  "utm_source": "linkedin",
  "utm_medium": "social",
  "utm_campaign": "messe-2026",
  "session_duration": 309.0,
  "session_time": 103.0,
  "session_engagement": 284.0,
  "user_agent_browser": { "family": "Chrome", "version": "130.0.0" },
  "user_agent_os": { "family": "Windows", "version": "11" },
  "user_agent_device": { "family": "Other" },
  "user_agent_category": "desktop",
  "visitor_city": "Freising",
  "visitor_zip": "85354",
  "visitor_country": "Deutschland",
  "visitor_country_code": "DE"
}

There were 245 seconds between the first and the last page view, and the browser measured 64 seconds on the last page. That makes a length of 309 seconds and 103 seconds per page view.

Edge casesCopy Anchor Link

• Missing values: In /session and /company-sessions, a field without a value is left out, but it can also be null. In the feeds and in webhooks, every field is present, as null without a value.
• Time not measured: If there was no interaction on the last page and the browser sent no active time, Webmetic can't measure the time there. Webmetic then uses an estimate of a few seconds, in time_spent and in session_duration.
• Order: /session and /company-sessions return sessions in no fixed order, so sort them yourself by timestamp or session_id. Within a row of the feeds, sessions run from oldest to newest. For details, see Pagination.
• Time range: from_date and to_date filter by the start of the session, in /session_user_data too. For details, see Date ranges and time zones.
• Several days: Because the client_id changes daily, you can't follow a visitor across several days. Link sessions through the company_id instead.
• Free plan: For companies you can't see on the Free plan, a session in /session only has session_id, company_id, timestamp, a placeholder as company_name, and blurred: true. For details, see Plans.

Used byCopy Anchor Link

• Endpoints: GET /session, GET /session_user_data, GET /company-sessions, GET /intensive-visits, GET /returning-visits, and GET /new-visits.
• Webhooks: company.identified, company.returned, company.intensive_visit, and segment.entered carry the session in data.visit. For details, see Webhooks.
• AI assistant: The AI assistant also retrieves a company's visits, with the tool get_company_activity.