First, the impetus of this Idea was born out of the frustration of seeing changes to all of the (multiple) Giving-Analytics-related Person Attributes completely cluttering up Person History.

This happens because the Giving Analytics process is just storing its data in regular old Person Attributes (perfectly fine), and today, any changes to a Person Attribute get recorded as  "Demographic Changes"  in Person History. These entries can overwhelm the other Demographic Changes that we are ACTUALLY looking for.

Here's an example of these attribute changes:

And here's a short screen cap that shows how distracting and cluttered these attribute changes are, because there are typically so many of them for a regular giver.
https://soapbox.wistia.com/videos/x0nTA4Bdrm

All that said, per discussion about this in Rock chat, we came to the conclusion that the best Idea was to enhance ATTRIBUTES themselves rather than make these particular (Giving-Analytics-related) attributes be presented in a different way, different category, etc.

So... the idea is quite simple:

Add a setting to attributes that determines whether changes to a specific attribute will be recorded in Person History (or not.)

In this way, organizations that want to reduce this clutter going forward can configure those attributes to NOT record in Person History, while organizations that DO want this info can just let them continue to record there. And because this would be a change to the way attributes work, any OTHER attributes an organization may want to suppress from Person History could also be configured that way. It's a general solution vs. one that only addresses the Giving Analytics "noise" problem.

I think a "Suppress Recording to Person History" setting (or whatever it ends up being called) should default to "off" (so that it represents current behavior and DOES record to History), and when checked/enabled, suppresses the recording of that attribute to history.