> ## 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.

# Company tracking

> Set up Cometly company tracking: choose how contacts are grouped into companies and whose identity your ad-platform conversions carry.

The **Company tracking** page holds the Cometly company tracking settings for the space you are in (a space is a workspace inside your account, with its own settings, integrations and data). It has two settings: how contacts are grouped into companies, and whose identity a conversion carries when Cometly sends it to an ad platform.

You need it when you sell to businesses, where the person who pays is often not the person who clicked the ad. Grouping teammates into one company lets you see the whole account's path to a sale, and lets the ad platform connect that sale to the click that started it.

## Where to find it

Click **Settings** at the bottom of the left sidebar, then **Company tracking** under **Workspace**. The page is titled **Company Tracking**.

## Who can use it

The account **Owner** and members with the **Administrator** space role see **Company tracking** in the settings menu and can change both settings. Advertisers and Viewers do not see the menu item and cannot open the page.

## Company identity

This card sets how Cometly decides which company a contact belongs to. A space uses exactly one source, never both.

| Option | What it does |
| - | - |
| **Group by email domain** | A business email address creates the company automatically (`jane@acme.com` joins Acme). Any `company_external_id` you send is ignored. This is the default. |
| **Group by your account ID** | Only the `company_external_id` you send on events creates and assigns companies. A business email creates nothing, and contacts that never send the ID stay ungrouped. |

> [!WARNING]
>
> Pick one and stick to it. Switching does not move existing contacts: companies grouped by email domain keep their current members and stop growing, and companies grouped by your account ID stay as they are.

To use **Group by your account ID**, your events have to carry a `company_external_id`. The developer guide [Account-level attribution for B2B](https://docs.cometly.com/guides/b2b-account-attribution.md) explains how to send it from the API, your website and webhooks.

### The "External IDs are arriving but being ignored" banner

A red banner with this title appears at the top of the card when both of these are true:

* The space is set to **Group by email domain**.
* Events for the space carried a `company_external_id` in the last 7 days.

It means the IDs you send do nothing in this space. If you meant to group by them, switch to **Group by your account ID** and save. If not, you can leave the setting as it is.

## Ad-platform conversion identity

This card sets whose identity is attached to a conversion when Cometly sends it to Meta, Google and the other ad platforms through the [Conversion API](https://docs.cometly.com/guides/conversion-api/overview.md) (the feature that sends the events Cometly tracks back to your ad platforms).

| Option | What it does |
| - | - |
| **Send as the person who converted** | Conversions reach the ad platforms with the identity of the contact who performed the event. This is the default. |
| **Send as the teammate who clicked the ad** | When someone else in the same company clicked an ad more recently than the person who converted, the conversion is sent with that teammate's email, name, phone and click IDs. It is always one person's identity, never a blend. When no teammate clicked an ad, it falls back to the person who converted. |

Use the second option when the buyer rarely clicks the ad. For example, a developer at a company clicks your ad and starts a trial, and weeks later a finance manager at the same company completes the purchase. Sent as the finance manager, the ad platform cannot connect the conversion to any click. Sent as the developer, it can.

Keep in mind:

* It relies on company grouping, in either **Company identity** mode. A contact with no company, or whose company has no ad clicks, is always sent as themselves.
* Conversion facts such as the amount, order ID and time are never changed.

## Save your changes

**1. Pick the options**

Select an option in one or both cards. The **Save Changes** button at the bottom of the page becomes available once something differs from what is saved.

**2. Save**

Click **Save Changes**. One click saves both cards, and you see **Company tracking settings saved**. There is no confirmation dialog.

If you see **Settings saved, but the tracker could not be notified. The new modes take effect within 12 hours.** instead, your choice is saved and takes effect within 12 hours rather than right away.

## Frequently asked questions

### Does a Gmail or other personal email address create a company in Cometly?

No. With **Group by email domain**, only a business email address creates a company, so a contact who signs up with a personal address stays ungrouped. To group those contacts, switch to **Group by your account ID** and send a `company_external_id` on their events.

### Do company tracking settings apply to all of my spaces?

No. Both settings belong to the space you are in when you save. If you have several spaces, open **Company tracking** in each one and set it there.

### What happens to a company\_external\_id I send while my space groups by email domain?

Cometly still accepts and stores it on the event, but does not use it to group contacts. The **External IDs are arriving but being ignored** banner tells you when this is happening.

## Next steps

* [Account-level attribution for B2B (company external ID)](https://docs.cometly.com/guides/b2b-account-attribution.md)
* [Conversion API](https://docs.cometly.com/guides/conversion-api/overview.md)
* [Space roles and permissions](https://docs.cometly.com/guides/account/space-roles.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.