A mapping rule didn't recognise a value
One of your automatic mapping rules matched new tracking profiles, but could not tell what one part of their names means. It left that detail empty on those profiles.
What it means
Mapping rules read a value out of each profile's name, for example BTM out of FB_BTM_DE, and translate it into a brand, traffic source, commission plan, country or region. Here the rule read a value it has no translation for. The message names the rule, the account, the detail (for example brand), the value it could not read, and how many profiles are affected.
Nothing is broken. Those profiles just still have that detail empty, so reports grouped by it show them as unassigned.
Why it happens
- The value is shorthand that the rule's What the values mean list does not cover yet. Matching ignores capitals and punctuation, but it never guesses abbreviations:
BTMonly means BetMGM once you add a row saying so. - A new campaign or brand started using a code nobody has added to the rule.
- The rule is reading the wrong part of the name for these profiles, so the value it reads was never meant to be a brand or country.
What you can do
- Go to Settings → Mapping rules and open the rule named in the message.
- In What the values mean, add a row for the value from the message and pick what it stands for. If the rule is reading the wrong part of these names, fix the rule instead.
- Save, then Preview and Apply the rule so the profiles that were left empty get filled in.
See Mapping rules.
When it clears
Automatically, when a run of that rule writes that value on that account, which is what step 3 does. Deleting the rule also closes it. If you fill the profiles in by hand instead, it is not closed straight away: it closes by itself 7 days after the value was last seen. It opens again if new profiles arrive with the same unknown value.