> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/other/gong.md).

# Gong

Connect Gong to HockeyStack to bring your sales calls into reporting, next to the rest of your GTM data.

#### What data does HockeyStack pull from Gong?

Each Gong call becomes **actions** in HockeyStack, and the call details come in as **Action Properties**. Gong doesn’t add any User, Deal, or Company properties.

**Actions**

| Action             | When it’s created                         | Tied to                       |
| ------------------ | ----------------------------------------- | ----------------------------- |
| Gong Call Started  | Once per call                             | The prospect’s company domain |
| Gong Call Attended | Once per external participant who joined  | That participant’s email      |
| Gong Call Skipped  | Once per external invitee who didn’t join | That invitee’s email          |

**Action Properties** (in **Atlas > Properties > Action**, search “Gong”)

| Category           | Properties                                                                                                                                                                    |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Call details       | Gong Call Id, Gong Call Title, Gong Call Brief, Gong Call Direction, Gong Call Duration Minutes, Gong Call Client Unique Id                                                   |
| Timing             | Gong Call Scheduled Date Time, Gong Call Started Date Time                                                                                                                    |
| Host               | Gong Call Host Id                                                                                                                                                             |
| Attendees\*        | Gong Call Attendee Name, Gong Call Attendee Email, Gong Call Attendee Affiliation, Gong Call Attendee Methods, Gong Call Attendee Id, Gong Call Speaker Id, Gong Call User Id |
| Linked CRM records | Gong Company Id, Gong Opportunity Id, plus any other CRM objects Gong links to the call (e.g. Gong Contact Id)                                                                |

\*Attendee properties only appear on the Gong Call Attended and Gong Call Skipped actions.

**What’s not included**

* Calls marked **private** in Gong
* Calls Gong classifies as **internal**
* Internal participants (your own team), and participants without an email address

**Sync frequency:** Every 8 hours.

#### What can I do with Gong data?

* **Report on call activity.** Count calls by account, opportunity, host, or time period in any report or dashboard.
* **Track attendance.** Use Gong Call Attended and Gong Call Skipped to see who from the buying committee shows up, and who doesn’t.
* **Filter and segment.** Filter by direction, duration, title, or attendee. For example, only calls over 30 minutes, or only calls tied to a specific opportunity.
* **See calls in the journey.** Gong calls show up on account and contact timelines next to marketing and sales touchpoints.

#### How to connect Gong

1. Go to **Atlas > Ingest > Sales Enablement > Gong**.
2. Click **Connect**. You’ll be redirected to Gong.
3. Log in to Gong and approve the requested permissions.
4. Once you’re authorized, calls sync automatically every 8 hours.


---

# 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.hockeystack.com/integrations/other/gong.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.