08-03-2017 01:54 PM
Where did the Icon go to insert an image??
We want to avoid a Visitor Attribute being set when the value is invalid or empty or undefined (according to the documentation on Visitor Stitching, that is dangerous because it may lead to stitching millions of profiles that are actually different people).
Right now we create all these seemingly stupid rules just to be "sure".
Is there an easy way to say "set only if not empty string or not undefined"?
@loldenburg This is a good question and a concept that needs to be clarified in that article. It does appear that the screenshots and examples are inaccurate with regard to the attribute rules and enrichments. We will add this article to our review queue.
The good news is that you do not have to create these rules for every Visitor ID attribute. The Visitor ID attribute protects itself according to the requirements mentioned in the article:
The Visitor ID attribute will automatically filter out values that do not satisfy that requirement.
That being said, the Visitor ID attribute cannot protect against unexpected values that satisfy that requirement. If, for example, you are passing in a value that is not intended to be a real Visitor ID, such as the string "unknown", it will result in unwanted visitor stitching. So it is important to understand how data is coming into UDH. In a case like that you could create an enrichment on the event attribute that unsets any unwanted values.
Hope that helps.
Just another quick follow-up to this...the Visitor ID Attribute article has been updated with details about the requirements for these values.