I guess I'm not following? If I were to create some custom_dateTime field with them updating it with the current time, I get that it would change, and I could do a trigger for Data Value Changes on this custom_dateTime field, but what I don't get is how to distinguish this for all 5 vendors (which could grow), and additionally, these vendors could be involved in more than one Content Syndication marketing initiative for which I'd like to track individually, and trying to isolate out these leads for each of the vendors for each of the Marketing initiatives. Obviously, I wouldn't create a separate custom field for each CS Vendor and their respective initiative combination, so I guess I'm still confused.
I provided the vendor with 2 custom fields with a specific custom value, in order to filter on that. I gave them 2 fields, CS Vendor and LatestCampaignActivity, filled out with the Vendor Name and the specific name for this marketing initiative. So, in order to grab the non-New Persons, I basically should have a trigger for Data Value Changes of LatestCampaignActivity = CS 2018-02-29 abc Vendor x asset. (which is the field I have had the CS vendor populate for me with this value specific to this campaign). So the question is, when this field goes from nothing to being filled with a value, is that considered a Data Value Changes when done with an API integration?
Am I on the right track here? Please let me know your thoughts here.
Yes, you can use a String field that incorporates a string representation of the datetime + other info, if you believe that will help avoid a proliferation of individual Datetime type fields.
(Though note that Datetimes are strikingly more efficient than Strings at the database level: a String takes up to 50x the storage space of a Datetime, and at least 2x. And Datetimes allow date arithmetic while date-like strings do not.)
So the question is, when this field goes from nothing to being filled with a value, is that considered a Data Value Changes when done with an API integration?
A change from empty to filled is registered as a change.
The creation of a new lead, with an empty or filled value, is not a change.