Consent ID Workflow Scenarios

🆕 New User

Step	Action	JENTIS Action	Consent Status
1	User visits your website for the first time (no existing consent)	NEW Consent ID created Default Status: FALSE	❌ FALSE
2	User interacts with CMP banner (explicit consent)	Consent ID updated ✅ Accepted → Status: TRUE ❌ Denied → Status: FALSE	✅ TRUE / ❌ FALSE
✅ Sync	JENTIS and CMP consent information are in sync

👤 Existing User

Step	Action	JENTIS Action	Consent Status
1	User visited your website before JENTIS was installed	ℹ No information stored (JENTIS not yet implemented)	–
2	User visits again after JENTIS installation	NEW Consent ID created Status applied from CMP	✅ TRUE / ❌ FALSE
✅ Sync	JENTIS and CMP consent information are in sync (Note: Consent ID timestamp will reflect first visit after JENTIS installation, which may differ from CMP)

⚠ Edge Case

Step	Action	JENTIS Action	Consent Status
1	User visits your website for the first time (no existing consent)	NEW Consent ID created Default Status: FALSE	❌ FALSE
2	User provides consent via CMP banner	Consent ID updated	✅ TRUE / ❌ FALSE
3	User deletes CMP cookies/storage	–	–
4	User visits another page and CMP shows banner again	Consent ID remains unchanged	Status unchanged
5	User interacts again with CMP banner	Consent updated accordingly	✅ TRUE / ❌ FALSE
⚠ Warning	In this case, JENTIS and CMP can become out of sync because JENTIS storage is not cleared when CMP storage is deleted (e.g., due to browser tracking prevention, a do-not-track add-on, or technical issues).

💡 Tip: Using this Consent ID workflow ensures that consent is traceable, even in scenarios where CMP storage might be lost, helping maintain legal compliance and data accuracy.