> ## Documentation Index > Fetch the complete documentation index at: https://www.usenotra.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get website sessions by UTM parameter > Sessions and visitors per value of one UTM parameter (source, medium, campaign, term or content), counted on each session's first page, against the previous window of the same length. Returns the top 25 values. Includes completed history imports when no path is set. Term and content from visits Notra tracked itself cover at most the last 90 days. Campaign, term and content values that look like an email address, a UUID or a token are reported as `:id`. ## OpenAPI ````yaml https://api.usenotra.com/openapi.json get /v1/projects/{projectId}/geo/traffic/web/utm openapi: 3.1.1 info: title: Notra API version: 1.0.0 description: >- OpenAPI schema for Notra content endpoints. Use GET /v1/status for public reachability. Error responses include recovery guidance. Breaking changes ship under a new major path; deprecated operations send Deprecation and Sunset headers at least 90 days before removal. servers: - url: https://api.usenotra.com description: Production - url: https://demo-api.usenotra.com description: >- Sandbox with sample data. Get a free sandbox key at demo.usenotra.com, no signup needed security: - BearerAuth: [] tags: - name: Webhooks description: Manage outbound webhook subscriptions and delivery history. - name: Discovery description: Public API status and authenticated workspace discovery. - name: Content description: >- Manage posts, brand identities, and GitHub or Linear integrations, and queue content generation. Organization is inferred from the API key (identity.externalId). - name: Schedules description: >- Manage scheduled content generation. Organization is inferred from the API key (identity.externalId). - name: Event Triggers description: >- Manage event-based content generation triggered by GitHub webhooks. Organization is inferred from the API key (identity.externalId). - name: Chats description: >- Manage chat sessions. Organization is inferred from the API key (identity.externalId). - name: Skills description: >- Manage reusable writing skills. Organization is inferred from the API key (identity.externalId). - name: Feedback description: >- Collect and triage feedback submitted by AI agents. Agents post to the organization's feedback URL without credentials; reading and triage require an API key with feedback.read or feedback.write. - name: GEO description: >- Manage generative engine optimization: projects, tracking settings, prompts, prompt sequences, competitors, scans, visibility reads, content gaps and briefs, agent readiness and AI traffic. Project-scoped endpoints require the GEO plan entitlement in addition to their scope; organization-level ingest endpoints require only the traffic scope. - name: Sites description: >- Notra Sites are hosted blogs and changelogs built from a GitHub repository. Read Sites and their deployments, start builds, preview posts on a Site, open pull requests that publish posts to it, and manage blog.json authors and the author page through staged Design changes. Domains, settings, rollbacks and deletion stay in the dashboard. externalDocs: description: Notra API versioning and deprecation policy url: https://www.usenotra.com/docs/api/versioning paths: /v1/projects/{projectId}/geo/traffic/web/utm: get: tags: - GEO summary: Get website sessions by UTM parameter description: >- Sessions and visitors per value of one UTM parameter (source, medium, campaign, term or content), counted on each session's first page, against the previous window of the same length. Returns the top 25 values. Includes completed history imports when no path is set. Term and content from visits Notra tracked itself cover at most the last 90 days. Campaign, term and content values that look like an email address, a UUID or a token are reported as `:id`. operationId: getGeoWebAnalyticsUtm parameters: - schema: type: string minLength: 1 pattern: ^[A-Za-z0-9_-]{1,100}$ example: b1f2c3d4-0000-4000-8000-000000000000 required: true name: projectId in: path - schema: type: integer minimum: 1 maximum: 365 description: Rolling window size in days. Ignored when from/to are set. required: false description: Rolling window size in days. Ignored when from/to are set. name: days in: query - schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-01-31' required: false name: from in: query - schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-01-31' required: false name: to in: query - schema: type: string maxLength: 128 description: >- Hostname to filter on, such as www.example.com. Subdomains are included. Omit for every host. required: false description: >- Hostname to filter on, such as www.example.com. Subdomains are included. Omit for every host. name: host in: query - schema: type: string maxLength: 2048 description: Only count this exact page path, such as /pricing. required: false description: Only count this exact page path, such as /pricing. name: path in: query - schema: type: string enum: - exclude description: '`exclude` leaves out traffic to sites hosted on Notra Sites.' required: false description: '`exclude` leaves out traffic to sites hosted on Notra Sites.' name: sites in: query - schema: type: string enum: - source - medium - campaign - term - content description: UTM parameter to group sessions by. required: true description: UTM parameter to group sessions by. name: dimension in: query responses: '200': description: UTM report fetched successfully content: application/json: schema: $ref: '#/components/schemas/GeoWebAnalyticsUtmResponse' '400': description: Invalid request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '402': description: GEO plan or available AI credits required content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Organization, project or resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Conflict content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Authentication or billing service unavailable content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: GeoWebAnalyticsUtmResponse: type: object properties: dimension: type: string enum: - source - medium - campaign - term - content rows: type: array items: type: object properties: value: type: string description: >- Source and medium are lowercased. Campaign, term and content values that look like an email address, a UUID or a token are reported as `:id`. sessions: type: integer previousSessions: type: integer visitors: type: integer required: - value - sessions - previousSessions - visitors organization: type: object properties: id: type: string slug: type: string name: type: string logo: type: - string - 'null' required: - id - slug - name - logo required: - dimension - rows - organization ErrorResponse: type: object properties: error: type: string code: type: string recovery: type: string required: - error securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Send your API key in the Authorization header as Bearer API_KEY. Account API keys work in every workspace you belong to: send X-Notra-Organization-Id with the workspace id or slug to choose one. Workspace endpoints require it when you belong to more than one workspace; GET /v1/me/workspaces works without it. Organization keys only accept their own workspace there. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.