A synced trait is reachable in smart trait formulas under several names — its full path, its connection prefix, its label, and its last segment. When two traits want the same name, one has to win.
Trait name precedence is where you decide which. Find it under Settings → Organization → Settings.
When this matters
Most orgs never need it. It becomes relevant when a second connection starts syncing traits with the same names as one you already have — connecting Stripe to an org that already has Vitally, for example, where both sync around forty stripe.* trait names.
The default: your first connection keeps the name
With nothing configured, the connection you had first wins. That is deliberate: connecting a new platform never silently changes what an existing formula reads.
The losing trait is not lost. It stays reachable at its connection-qualified full path, so a formula can always address it unambiguously:
Two kinds of conflict
The settings panel separates them, because only one kind can be fixed by reordering.
Names claimed by more than one connection. Reordering the list changes which one wins. The panel lists them and the order control is right above.
Names claimed twice within a single connection. Two traits from the same connection want the same short name — a trait called country and another called stripe.country, say. Connection order cannot settle this; the winner is stable but fixed. If a formula needs the shadowed one, write it against that trait’s full path instead.
Changing the order
Move a connection up to hand it the contested names. The change applies to every formula, segment and report that reads those names.
Reordering changes which trait existing formulas read, which can change the values they produce. Check the conflict
list below the control to see exactly which names are affected before you save.
