# Analytics

Based on our experience, there are occasional gaps in the Freshdesk API that can result in the `<Birdie>` tag not being applied when it should (eg. tickets from Freshdesk portal).&#x20;

To ensure consistent tagging, we recommend using Freshdesk automations to add the `<Birdie>` tag:

1. Go to Freshdek settings and select <mark style="color:purple;">`Automations`</mark>

   <div><img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/c0bb67d2-7911-4a72-8f32-1828243589b8/Capture_dcran_2023-05-11__12.02.29_(1).png" alt=""> <figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FBH6cj9XDOETiRokQP3LZ%2FCapture%20d%E2%80%99e%CC%81cran%202023-11-09%20a%CC%80%2005.40.27.png?alt=media&#x26;token=43ae323f-8d44-4298-a3b3-a70f850a46a9" alt=""><figcaption></figcaption></figure></div>
2. Select Ticket Creation and create a <mark style="color:purple;">`New rule`</mark>:

   <div><img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/6491165e-b176-48bf-bb65-9b66b5de3494/Capture_dcran_2023-05-11__12.03.41_(1).png" alt=""> <figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FDuaLz3cduIQqKmccrYNY%2FCapture%20d%E2%80%99e%CC%81cran%202023-11-09%20a%CC%80%2005.41.09.png?alt=media&#x26;token=9f465055-b907-4be7-a286-99ba7b6f6b71" alt=""><figcaption></figcaption></figure></div>
3. Then, for the tickets whose description contains <mark style="color:purple;">`share.birdie.so`</mark>, add a tag called <mark style="color:purple;">`birdie`</mark>.

   <div><img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/63360da1-13a0-4712-98be-a41810f0a521/Capture_dcran_2023-05-11__12.13.06_(1).png" alt=""> <figure><img src="https://3843507234-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FECPgvsGwy5oMz4WIZw3a%2Fuploads%2FeUGDAkg0FZN8VWWas7Ry%2FCapture%20d%E2%80%99e%CC%81cran%202023-11-09%20a%CC%80%2005.42.37.png?alt=media&#x26;token=4fd6c636-a695-4942-aeda-bfe0930c33df" alt=""><figcaption></figcaption></figure></div>
4. Your tags will now be automatically created. ✅

<details>

<summary>How to Differentiate Incoming vs. Outgoing Recordings</summary>

Birdie uses specific URL patterns that let you identify whether a recording is **incoming** (from customers) or **outgoing** (to customers):

* **Incoming recordings** (from customers): URLs include `share.birdie.so/i/`
* **Outgoing recordings** (to customers): URLs include `share.birdie.so/o/`\ <br>

You can use this in your triggers to tag tickets accordingly.

**Example triggers:**

| Trigger name                | Condition                                           | Tag added         |
| --------------------------- | --------------------------------------------------- | ----------------- |
| Birdie – Incoming Recording | Ticket > Comment text contains `share.birdie.so/i/` | `birdie_incoming` |
| Birdie – Outgoing Recording | Ticket > Comment text contains `share.birdie.so/o/` | `birdie_outgoing` |

</details>

<details>

<summary>How to track when a Birdie Recording Is Requested?</summary>

Add a tag <mark style="color:purple;">`birdie_request`</mark> tag by creating a new rule:&#x20;

> **Category:** in `Ticket`  if `Description`   \
> **Operator:** `Contains`\
> **Value:** <mark style="color:purple;">`birdie.so/rec`</mark> <mark style="color:purple;"></mark><mark style="color:purple;">AND</mark> <mark style="color:purple;"></mark><mark style="color:purple;">`birdie.so/urec`</mark>

</details>