> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# get_company_journey

> Full chronological timeline for a single company — touchpoints + conversions across all contacts.

Same shape as `get_contact_journey` but rolled up to the company. Includes a `contact_roster` of every profile that touched ads on the company's behalf.

## When to use

* "Show me the journey for Acme Corp."
* "Which contacts at this company touched our ads?"

For per-contact journeys, use [`get_contact_journey`](/mcp/tools/get-contact-journey). For the basic company record, use [`get_company`](/mcp/tools/get-company).

## Parameters

| Parameter    | Type    | Required | Description                         |
| ------------ | ------- | -------- | ----------------------------------- |
| `company_id` | integer | Yes      | Numeric company id.                 |
| `format`     | string  | No       | `json` (default), `csv`, or `yaml`. |

## Output

```json theme={null}
{
  "company_id":     901,
  "domain":         "acme.com",
  "ltv":            12849.20,
  "contact_roster": [8231, 8240, 8312],
  "event_count":    34,
  "events": [
    { "type": "touchpoint", "event_time_utc": "2026-03-02T...", "source": "linkedin_ads", "profile_id": 8231 },
    { "type": "conversion", "event_time_utc": "2026-03-15T...", "event_name": "purchase", "amount": 4200, "profile_id": 8240 }
  ]
}
```

`companies` in this codebase are domain-based only — there's no human "company name" column. Surface the domain to the user.

## Caveats

Capped at 250 touchpoints + 250 conversions per company (500 events total).