Implementation
- Tags Sync Workflow Guide — workflow context and sequencing
- How to Sync Tags with Dimension Values — API usage and step-by-step instructions
Conceptual Model
Tag synchronisation keeps the Tags within each Tag Group aligned with the Dimension Values of the corresponding Dimension.| AS Entity | Pleo Entity |
|---|---|
| Dimension Value | Tag |
| Dimension Value code | Tag code |
| Dimension Value name | Tag name |
Sync Process
1. Pull Dimension Values
For each synced Dimension-Tag Group pair, retrieve active (non-blocked, non-expired) Dimension Values from the AS.2. Pull Tags from Pleo
Retrieve active and archived Tags for the corresponding Tag Group from Pleo.3. Match Dimension Values to Tags
For every Dimension Value, match against Tags using the Dimension Value’s code (case-insensitive).Code found — Tag is active
The AS Dimension Value is active and the matching Pleo Tag is also active. Preserve it. If the Tag’s name differs from the Dimension Value name, update the Tag’s name to match.Code found — Tag is archived
The AS Dimension Value is active but the matching Pleo Tag is archived. Unarchive it. If the Tag’s name differs from the Dimension Value name, update the Tag’s name to match.Code not found
The AS Dimension Value is active but no matching Pleo Tag exists. Create a new Tag with the Dimension Value’s code and name.Duplicate codes found
Two or more Tags in Pleo share the same code. Apply the following resolution logic:- Check whether any of the duplicates also match the Dimension Value by name.
- If a name match exists: retain that Tag, archive all other duplicates.
- If no name match exists, or multiple name matches exist: retain one Tag (chosen randomly), update its name to match the Dimension Value, and archive all other duplicates.
4. Archive unmatched Tags
Pleo Tags that are active but have no matching active AS Dimension Value must be archived. This covers Tags corresponding to Dimension Values that have been deleted, blocked, expired, or deactivated in the AS.Matching Rules
- Matching is performed using the code field on both ends.
- Matching is case-insensitive: a Dimension Value with code
ENGmatches a Tag with codeeng. - Name differences do not affect matching; only code is used for matching. Names are updated separately if they differ.