Data consolidation & token priority

Data consolidation merges data from multiple sources into a single, up-to-date record instead of piling up duplicates. Two mechanisms work together: the key field decides which record incoming data belongs to, and source priority decides which value wins when two sources set the same field.

How the key field matches records

Every incoming write — from an import, a Make scenario, or the API — is matched against the space's key field. A match updates the existing record; no match creates a new one. Set the key to whatever uniquely identifies your data (email, SKU, order number).

Source priority

Each source that writes data — every API token, plus manual entry — has a priority. When two sources set the same field on the same record, the higher-priority source wins. There are seven levels:

Highest › Higher › High › Medium › Low › Lower › Lowest

  • Medium is the default for everything — every new token and data entered or imported manually. So by default all sources sit at the same level, and the most recent write wins.
  • Raise a trusted source above Medium so it always wins; drop a noisy one below so it can never overwrite better data.
  • Priority governs writes into Boost.space (the Connect and Enrich directions). Exports (Share) don't consolidate.

Manual entry isn't special — it's simply at Medium. A source above Medium can overwrite a value you typed; a source below Medium can't.

Set priorities

Setting priorities requires the Scale licence. Open a module and switch to the Flow view.

  • Per source — set a token's base priority, applied to every field it writes.
  • Per field — open a field's Data aggregation settings (the gear on the column) to override priority for that field only. Restore default clears the override.

In short

The key field keeps one record per real-world entity; priority keeps the right value on it when sources disagree — giving you one clean, trusted dataset no matter how many tools feed it. See also Remote IDs, which record each source's external identifier for the matched record.