slug: hotjar
provider: Hotjar
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Survey Responses
  spec_file: hotjar-survey-responses-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.8
  evidence: GET /sites/{site_id}/surveys/{survey_id}/responses listSurveyResponses List survey responses;
    schemas SurveyAnswer, SurveyResponse; vendor 'behavior analytics and user feedback platform'
  reason: Retrieves end-user survey answers collected from website visitors — voice-of-customer/feedback
    data, matching Customer Feedback Management (surveys, NPS, VoC). Some ambiguity with product usage
    analytics, but the artefacts are explicitly survey responses.
- tag: Surveys
  spec_file: hotjar-surveys-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.8
  evidence: GET /sites/{site_id}/surveys listSurveys List surveys for a site; schemas SurveyQuestion,
    Survey
  reason: Manages/reads website feedback survey definitions and questions for a site, which realises survey-based
    customer feedback capture rather than any technical capability. Could alternatively be read as product
    insight, but survey instrument management maps best to Customer Feedback Management.
- tag: User Lookup
  spec_file: hotjar-user-lookup-api-openapi.yml
  capability_id: BC-130.50
  capability_id_l1: BC-130
  capability_name: Privacy & Data Protection Management
  confidence: 0.7
  evidence: 'POST /organizations/{organization_id}/user-lookup — "Look up or delete user data"; description:
    "automate user lookup and deletion requests"'
  reason: The single operation looks up and deletes an identified end-user's data, i.e. programmatic fulfilment
    of data-subject access/erasure requests, which is privacy & data protection management rather than
    any analytics capability. Moderate confidence because the alternative reading (vendor-side service-privacy
    commitment stewardship) is also defensible.