With the new consent tile, when consent is imported - regardless of the start date of that consent - the date that RE uses to decide what order to show on the consent tile overview is the date that the consent was added.
While this makes sense most of the time as the consent tile is a historical record, it comes undone in situations like the one my organisation faces where another charity's database was merged into ours.
Every single consent from that database is dated 4th April 2025 (when the merge was being processed by BB) - even the ones from when it seems like that charity did an exercise where they added opt-in consent with a legitimate interest reason on a big group of records all with the start date 1st January 1900. As there is a substantial overlap in donor-base between the two charities, we are merging a lot of records and these Victorian-era consents now appear more recently than consents recorded in our original database from anytime in the last 100 years once the records are merged.
It looks like this:
Date added |
Channel |
Category |
Consent |
Start Date |
04/04/2025 |
Opt-in |
01/01/1900 |
||
04/04/2025 |
Phone |
Opt-in |
01/01/1900 |
|
04/04/2025 |
Opt-in |
01/01/1900 |
||
04/04/2025 |
SMS |
Opt-in |
01/01/1900 |
|
18/04/2024 |
Opt-out |
18/04/2024 |
While our case is a bit unusual, I can see that this could also cause problems if consent is collected by third parties (fun run sponsor forms, JustGiving, big crowdfunding campaigns and others) and that supporter directly updates their consent with us. The third party collected consent could get entered into RE after the consent directly from the supporter but should be dated on the day of collection.
Basically, it would be great if there was something that could import historical consents so that they could be recorded in the right order chronologically.