> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/hubspot/analytics.md).

# Analytics

The Screendesk activity property on HubSpot tickets, and how to compare tickets with and without recordings in views, reports and workflows.

Screendesk marks the HubSpot tickets it works in. It adds a **Screendesk activity** ticket property to your HubSpot account and ticks a value on a ticket each time something happens on it, so you can filter tickets, report on them and run workflows.

Marking is on by default. To turn it off, open **Settings → Integrations** in Screendesk, click **Configure** on the HubSpot card and switch off **Mark the tickets**. Screendesk adds the property when you connect HubSpot, when you turn **Mark the tickets** on, or the next time you open **Configure**. In HubSpot, it's in the **Screendesk** property group, with the internal name `screendesk_activity`.

| Value                    | Ticked when                                                                                             | Ticked by           |
| ------------------------ | ------------------------------------------------------------------------------------------------------- | ------------------- |
| **Recording requested**  | An agent clicks **Request a recording** in the card.                                                    | The Screendesk card |
| **Recording received**   | A customer's recording arrives on the ticket as a note.                                                 | Screendesk          |
| **Video call started**   | A video call started from the card begins: at least two people have joined it.                          | Screendesk          |
| **Call recording added** | A recorded video call started from the ticket is added to it as a note.                                 | Screendesk          |
| **Booking link sent**    | An agent copies a booking link from the card.                                                           | The Screendesk card |
| **Video shared**         | An agent copies a library video from the card, or submits a recording made with **Record a response**.  | The Screendesk card |
| **AI note added**        | [AI resolution](https://docs.screendesk.io/debug-with-ai/ai-resolution.md) adds its note to the ticket. | Screendesk          |

The three values ticked by the Screendesk card in the ticket's sidebar need the card's current version: an older card doesn't tick them. The others are ticked by Screendesk itself, whatever the card's version.

A ticket keeps every value it gets: Screendesk never unticks one. Tickets from before you connected HubSpot or turned marking on have no value.

## Find tickets with recordings

1. In HubSpot, open **CRM → Tickets** and click **Advanced filters**.
2. Under **Advanced filters**, click **Add filter**, search for **Screendesk activity** and select it.
3. Choose **is any of** and tick **Recording received**.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FrCRqngll8N7drAuAeAii%2Fhubspot-analytics-view.png?alt=media" alt="HubSpot tickets filtered by Screendesk activity is any of Recording received"><figcaption></figcaption></figure>

For the tickets without one, choose **is none of** instead and tick the option to include tickets with no value, so the tickets Screendesk never marked count too. Save the filter as a view to come back to it.

## Compare them in a report

Custom reports need a HubSpot Professional or Enterprise subscription (any hub). Views and their filters work on every HubSpot plan.

1. In HubSpot, open **Reports**, click **Create** and choose **Create report**.
2. Choose **Custom report** and click **Next**. Keep **Create report on your own**, pick **Tickets** as the **Primary data source** and click **Next**.
3. Click **+** next to **Screendesk activity** and **(Count) tickets**.

   <figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FlF6GiywZTqaBqA8dHco8%2Fhubspot-analytics-report.png?alt=media" alt="A HubSpot ticket report broken down by Screendesk activity"><figcaption></figcaption></figure>
4. Click **+** next to **Time to close**, click it under **Columns** and set **Aggregation** to **Average**.

The table has a row for each value. **Recording received** shows the tickets that got a recording, and **(No value)** the ones Screendesk never marked. A ticket with several values counts in each of their rows. Add other ticket properties the same way, such as your CSAT or first-response properties.

## Use it in a workflow

Ticket-based workflows, and workflows that edit tickets, need a HubSpot Service Hub Professional or Enterprise subscription. They can use the property as a trigger or a branch. For example, notify a ticket's owner when a recording arrives: set the enrollment trigger to **Screendesk activity** is any of **Recording received**, then add a notification action.

{% hint style="info" %}
**Links from snippets, marketing emails and forms**

These links name no ticket, so Screendesk can't mark the ticket when the customer pastes their recording back. See [Snippets](https://docs.screendesk.io/helpdesk-integrations/hubspot/snippets.md), [Marketing emails](https://docs.screendesk.io/helpdesk-integrations/hubspot/marketing-emails.md) and [Forms](https://docs.screendesk.io/helpdesk-integrations/hubspot/forms.md).

* **Forms**: if your form's message fills the ticket description, a workflow can tick it for you (Service Hub Professional or Enterprise). Create a ticket-based workflow with the trigger **Ticket description** contains any of `screendesk.io/r/` and `screendesk.io/recordings/`. Add an **Edit record** action: **Screendesk activity**, change type **Append**, value **Recording received**.
* **Replies**: a link the customer pastes in a later reply isn't a ticket property, so no workflow can see it. Tick **Recording received** on the ticket's **Screendesk activity** property yourself.
  {% endhint %}

A [chatbot or Breeze](https://docs.screendesk.io/helpdesk-integrations/hubspot/chatbots-and-agents.md) recording is marked only when the request names the ticket (`ticket_id`). Otherwise it goes on the customer's contact.

{% hint style="info" %}
**The old Screendesk Yes/No property**

A Yes/No ticket property named `screendesk`, made from an earlier version of this page, is a separate property. Screendesk still sets it to **Yes** when a recording arrives on a ticket, or when a video call recording is added to it as a note.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/helpdesk-integrations/hubspot/analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
