We use channel specific opt in fields in our instance, such as:
For better compliance purposes I would like to implement timestamps for these fields and I would like to get your opinion on what the best way of doing it would be.
Is it better to create a separate timestamp field for Opt Ins and Opt Outs?
Is it sufficient enough to have one timestamp field that updates whenever the Opt In field updates to Opt In or Opt Out?
You may want to have at least one separated date field for each opt-out field.
One field should be enough, though, as anyway, all changes in all these fields are logged by Marketo as data value changes that are all time-stamped.
We have a global "process opt-in requests" program set up that not only timestamps the opt-in request, but also associates the program that was responsible for it. And since we're a global company, we have an extended process for Germany, where double-opt-in is required.