Who can use this: Tech admin
Available on: Any Gong plan
Ideal for: Salesforce admin
Gong Territories brings your Salesforce Enterprise Territory Management (ETM) hierarchy into Gong, so deal boards, forecast boards and dashboards can roll up by territory instead of by manager. Gong reads your territory setup and never changes it. Set up your territory model, user assignments and opportunity territories in Salesforce before you turn on the import in Gong.
Before you begin
Gong Territories works with Salesforce ETM only. Other CRMs aren't supported.
A Salesforce admin completes steps 1 to 5 in Salesforce.
In step 6, a Tech admin turns on the import in Gong. Once it's on, it can't be turned off.
In Gong, territories apply to opportunities only. Accounts aren't organized by territory, so you don't need to change how accounts are assigned to territories in Salesforce.
Step 1: Activate your territory model
Gong imports only the territory model that's active in Salesforce. If you build a new model, it appears in Gong only after you activate it in Salesforce.
To activate your territory model:
In Salesforce, build or finalize your territory hierarchy in the territory model.
Set the model's state to Active.
Step 2: Assign Salesforce users to territories
User assignments control which territories, deals and forecasts each team member can see in Gong. An assignment covers the territory and everything beneath it.
To assign Salesforce users to territories:
In Salesforce, assign each user to the territories they cover.
Note: Assign each user the highest territory they own. They don't need a separate assignment for each territory beneath it.
For each territory with no one assigned to it, check that someone is assigned to its parent territory.
Note: A territory with no one assigned still appears in the forecast and rolls up to its parent territory like any other territory. Anyone assigned to the parent territory can submit the forecast for it.
Step 3: (Optional) Assign a role in each territory
Everyone assigned to a territory can see its data, but only the forecast owner can submit its forecast. When an admin sets up a territory-based forecast board in Gong, they choose whether forecast owners follow territory assignments or Role in Territory. Complete this step only if you plan to set forecast owners by role.
In Salesforce, set Role in Territory on each user's territory assignments, at every level of the hierarchy, from the lowest territories to the top. Role in Territory is a field on the territory assignment, not a role from the Salesforce role hierarchy.
Step 4: Assign opportunities to territories
Gong places each opportunity in a territory based on the standard territory field on the Opportunity object. Custom territory reference fields on opportunities aren't supported.
In Salesforce, use your ETM assignment rules to assign opportunities to territories. Every opportunity you want in territory-based boards needs the standard territory field filled in.
Step 5: Give the integration user access to territory data
Gong connects to Salesforce through an integration user and imports only the territory records that this user can read.
Learn more about the objects and fields Gong needs access to.
To give the integration user access:
In Salesforce, give the integration user read access to these objects:
Territory2
UserTerritory2Association
Give the integration user read access to the territory field on the Opportunity object.
Step 6: Turn on the territory import in Gong
Turning on the import starts the territory sync. Complete steps 1 to 5 in Salesforce before you start.
To turn on the territory import:
From the left sidebar, click Admin center.
In the Settings tab, click CRM settings under the CRM card.
Click the Import settings tab.
Under Territory hierarchy, select the Import territory hierarchy and the role assignment checkbox. This imports your territory hierarchy and the user assignments for each territory, including Role in Territory.
Warning: Once enabled, this setting can't be disabled.
Click Update.
The first import can take a few hours. After that, Gong picks up territory changes from Salesforce within an hour. Learn more about Gong-CRM data sync times.
Step 7: (Optional) Tag territories for Territory Views
A Territory View limits a territory-based forecast board, deal board or dashboard to part of your hierarchy, such as only your Sales territories or only your Partners territories. You define each view by tagging territories in a custom field in Salesforce, and Gong Support then generates the views. A view changes only which territories a board shows. It doesn't change your territory model or what each team member can see and submit.
To set up Territory Views:
In Salesforce, create a custom text field on the Territory2 object, for example Forecast Business Segment.
Note: Each value in the field becomes its own Territory View, named after the value. Enter values exactly as you want them to appear in Gong, and use the field only for values you want as views.
On each territory that belongs in a view, enter that view's value. For a territory that belongs in more than one view, enter every value, separated by semicolons, for example Sales;Partners.
Open a ticket with Gong Support, and include:
The field's API name and label
The Gong workspace where the views should be available
The values you expect to become views
Gong Support confirms when the views are ready, usually within 3 to 5 working days. Then, in Gong, Forecast Admins can select a view for forecast boards, and board admins can select one for deal boards and dashboards.
How Gong builds a view from your tags
Gong builds each view from the tagged territories only, keeping them in the order they have in your hierarchy:
A tagged territory rolls up to its nearest tagged territory above it, however many levels up that is.
A tagged territory with no tagged territory above it becomes a top-level territory in the view. A view can have several top-level territories.
An untagged territory with tagged territories beneath it is skipped, and those tagged territories roll up to the next tagged territory above it.
An untagged territory with nothing tagged beneath it is left out, together with its whole branch.
These rules let you shape a view with tagging alone:
Goal | How to tag |
|---|---|
Start the view below your top level | Leave everything above the new top level untagged. |
Leave out a branch | Leave the branch, and everything under it, untagged. |
Skip a level | Tag the levels above and below it, and leave the level to skip untagged. |
Note:
When territories from two views roll up to the same territory, that territory and every shared territory above it need both values, for example Sales;Partners.
For example, Global is tagged Sales;Partners, AMER and EMEA are tagged Sales, and AMER Partners and EMEA Partners are tagged Partners. The Partners view skips AMER and EMEA, and both partner territories roll up directly to Global.
Step 8: (Optional) Bring in historical territory assignments
The territory sync brings in current territory assignments only. To show opportunities in the territories they belonged to at an earlier date:
In Salesforce, map historical Territory2 IDs against your Opportunity field history, and export the result as a CSV file.
Open a ticket with Gong Support and attach the CSV file.
Keep your territory setup current
After the first import, you maintain territories in Salesforce only. Gong picks up each change on its next sync. These changes need extra attention:
New territories: A new territory appears in the full hierarchy on the next sync, but in a Territory View only once it's tagged. Add the tagging field to your territory creation process.
New values: A new value in the tagging field creates a new Territory View automatically on the next sync.
Changed responsibilities: Update user assignments in Salesforce when people move. Assignments control what each team member can see in Gong.
Deleted territories: Gong removes a deleted territory from every view, and its tagged territories roll up to the next tagged territory above it.
The tagging field: Renaming the field's label has no effect, because Gong stores its API name. Deleting the field stops its views from working. Before you delete the field or one of its values, remove the matching Territory View from every board and dashboard that uses it.
A replaced territory model: When you activate a new model in Salesforce, Gong reads it on the next sync and rebuilds your Territory Views from its tagged territories.
Frequently asked questions
Are opportunity splits supported?
No. A split belongs to a user, not a territory. Territory rollups always use the opportunity's full amount.
Can we use team-based and territory-based boards at the same time?
Yes. Territories don't replace your team hierarchy. You choose team or territory when you create each deal board, forecast board or dashboard, and you can't change it afterward.