Data Map View

Location: /a/<team_slug>/data-sources/<uid>/update/map

The Data Map view is used for mapping origin data to the mandatory and recommended BoogieBoard fields. Any field from the origin source can be ingested and attached to the BoogieBoard account entity.

Mapping allows the user to control which fields are imported, the corresponding BoogieBoard property to which it matches, the field’s data type, and the user’s preferred display name for the field.

BoogieBoard Attributes

BoogieBoard relies on a defined set of account-level attributes to accurately model, analyze, and distribute accounts within territory structures. These attributes ensure data consistency across integrations and allow for precise territory balancing, hierarchy management, and reporting.

Below are the required and recommended attributes for every connected or imported dataset:

Required

  1. ID – A unique external identifier for each account. BoogieBoard uses this ID to maintain record integrity during synchronization and when exporting finalized territory assignments.
  2. Name – The human-readable account name, displayed throughout the application wherever users take action on accounts.

Recommended

  1. UltimateParentId – The unique identifier of the account’s ultimate parent record; the account’s top-most parent in the hierarchy tree. Used to establish hierarchical relationships and enable account family logic.
  2. ParentId - The unique identifier of the account’s immediate parent account. Used to establish hierarchical relationships and enable account family logic.
  3. City– The city in which the account is located. Required for geographically based territory models.
  4. State– The state or province in which the account is located. Required for geographically based territory models.
  5. PostalCode– The postal or ZIP code associated with the account. Required for geographically based territory models.
  6. Country– The country in which the account resides.
  7. OwnerId – The unique identifier or name of the current account owner. Useful for comparing current ownership with proposed model changes.