4U Platform

A description of the csv file format can be found in the <a href="https://help.4uplatform.com/en/articles/5442867-data-files-for-sftp" rel="nofollow noopener noreferrer" target="_blank">accompanying article</a>.

A territory describes a user location (eg branch or office).  At this time, only US-based locations are accepted.

<code>territory_id</code>: A unique identifier of the location (eg branch or office). Some clients use their branch number. The <code>territory_id</code> is not displayed within the 4U Platform. Two territories may not have the same id.

<code>name</code>: A unique name for the territory as you would like it to appear within the system. Some clients have made this a combination of the branch number and location. For example, "999 - Walnut Creek, CA". The territory name is what your Field users will see as their location for contact matching and IC and WM Home Office users see as locations in the analytics reporting. Two territories may not have the same name.

* Uniqueness: Although defining locations at the branch or office level is the most common and generally recommended approach, it is possible to define locations that span larger geographical regions comprising multiple postal codes. In these cases, we support specifying multiple postal codes by repeating the unique <code>territory_id</code> and <code>name</code> line multiple times (one per postal code). See Sample File below:

1. <code>territory_id</code>: A unique identifier of the location (eg branch or office). Some clients use their branch number. The <code>territory_id</code> is not displayed within the 4U Platform. Two territories may not have the same id.
2. <code>name</code>: A unique name for the territory as you would like it to appear within the system. Some clients have made this a combination of the branch number and location. For example, "999 - Walnut Creek, CA". The territory name is what your Field users will see as their location for contact matching and IC and WM Home Office users see as locations in the analytics reporting. Two territories may not have the same name.
3. * Uniqueness: Although defining locations at the branch or office level is the most common and generally recommended approach, it is possible to define locations that span larger geographical regions comprising multiple postal codes. In these cases, we support specifying multiple postal codes by repeating the unique <code>territory_id</code> and <code>name</code> line multiple times (one per postal code). See Sample File below:

territory_id,name,postal_code 3,"3 - Yeadon, PA",19050-3343 7,"7 - Walnut Creek, CA",94598

One line per postal code with all records for a given <code>territory_id</code> appearing consecutively in the file. All records for a given <code>territory_id</code> appearing consecutively in the file is a requirement for correct processing.

Whenever possible, using more granular branch-level locations is recommended.

territory_id,name,postal_code 3,"Portland Metro, SE",97202 3,"Portland Metro, SE",97206 7,"7 - Walnut Creek, CA",94598

Please contact us at <a href="mailto:Support@4uplatform.com" rel="nofollow noopener noreferrer" target="_blank">Support@4uplatform.com</a> for additional assistance.

Describes the format of territory data files for the provisioning and maintenance of user locations.

Column Name	Required?	Type (max length)	Unique?
territory_id	Yes	string (255 characters)	yes*
name	Yes	string (255 characters)	yes*
postal_code	Yes	string (10 characters) USPS postal code in either 5 digit or Zip+4 format.	no

General Format

Column Descriptions

Notes

Sample File

Locations with one postal code

Locations spanning multiple postal codes