What happens when an attribute's value changes?

[loldenburg]

https://community.tealiumiq.com/t5/Universal-Data-Hub/What-happens-when-two-visitor-profiles-are-sti... says:

"So back to the question, whether the "Opt-In Status" flag will be set to “True” or “False”, the answer is that it depends on the outcome of all of the enrichments that will be reprocessed when AudienceStream replays all of these visitors' past events."

That's hard to understand for me: Say a person identifed as living in zip code 8000 (string attribute). Now he moves to another city and updates his profile on desktop. His new zip code 7000 is tracked into the same string attribute. What will Visitor Stitching/Data Layer enrichment show the next time for this user when he enters the site on Mobile?

[dan_george · Accepted solution]

@loldenburg

I'm going to attempt to provide 2 specific scenarios in the hopes that it clears any confusion.

Scenario 1

• In this scenario, the enrichment is setup to set the "Zip Code" string to UDO variable customer_zip_code as long as customer_zip_code is assigned and is not empty
• This is an overwrite scenario, meaning as long as a valid value is passed in to customer_zip_code, it will always overwrite and use the latest value even for a stitch event
• So if 8000 was first received and 7000 was later received, the String would equal 7000 in the end

Scenario 2

• In this scenario, the enrichment is setup to set the "Zip Code" string to UDO variable customer_zip_code as long as customer_zip_code is assigned and is not empty AND the the "Zip Code" string is not already assigned
• This is a persist original value scenario, meaning once the value is set it will never overwrite, it will always persist and use the first value even for a stitch event
• So if 8000 was first received and 7000 was later received, the String would equal 8000 in the end

Conclusion

Zip Code may not be the best scenario to use in this use case since you would always want the latest value to be saved. I would venture to say that in most use cases, scenario 1 is what is going to be used.

However, the system is built to be flexibile enough to allow users to determine what exactly they need to do with their data, hence the answers "it is fully dependant on how your enrichments are setup".

Please let me know if this helps, or this caused any further confusion!

Cheers,

-Dan

[loldenburg]

Ok that makes sense, thanks, Dan. This post of yours yearns to be added to that documentation page because it makes it a lot clearer than "it depends on the outcome of all of the enrichments that will be reprocessed when AudienceStream replays all of these visitors' past events" (sorry, I am lost here)! ;)

[kathleen_jo]

---

@loldenburg wrote:
Ok that makes sense, thanks, Dan. This post of yours yearns to be added to that documentation page because it makes it a lot clearer than "it depends on the outcome of all of the enrichments that will be reprocessed when AudienceStream replays all of these visitors' past events" (sorry, I am lost here)! ;)

---

Indeed @loldenburg. We've definitely heard your request.