Skip to content
  • There are no suggestions because the search field is empty.

How Companies Work in HubSpot

Review Companies Work in HubSpot

What a Company represents

In HubSpot, a Company represents a retailer or agency we work with.

In most cases:

  • There is one company

  • The company may have one, multiple or no Omnivore URLs

  • Tickets, deals, contacts, and activity all relate to that company

Having multiple Omnivore URLs does not automatically mean multiple companies.

Leads, prospects, and pre-install Companies may exist in HubSpot without any Omnivore URL


When parent and child companies are used

Parent and child companies are used only when structure requires it, such as:

  • Enterprise retailers with separate brands like CRG

  • Groups with multiple trading businesses like MobileCiti

  • Agencies managing multiple independent retailers like Phase 3

  • Partners, eCommerce Platforms and Marketplaces

In these cases:

  • The parent company represents the overall group or agency

  • Child companies represent the individual brands or agency-managed retailers

Each child company maintains its own tickets, deals, contacts, and history, while rolling up to the parent for visibility.


How this relates to Omnivore URLs

Companies represent who we are working with.
Omnivore URLs represent which Omnivore account is involved.

A company (standalone or child) can have one or more Omnivore URLs.
Omnivore URLs sit alongside company structure.


Ticket rule

For tickets:

  • The Company and Omnivore URL must belong to the same child company

  • Parent companies are used for roll-up visibility only and should not be linked to tickets


Why this matters

Using companies and parent/child relationships correctly:

  • Keeps data clean and understandable

  • Avoids duplicate or misleading company records

  • Ensures tickets and reporting sit in the right place


Summary

  • Most retailers only need one company, even with multiple Omnivore URLs

  • Parent/child companies are used only when needed

  • Omnivore URLs represent Omnivore accounts, not company hierarchy

  • Tickets must link to the correct child company and Omnivore URL