Update Profile Action reverting same schema's consent field | Community
Skip to main content
A
ap95
Level 3
July 1, 2026
Question

Update Profile Action reverting same schema's consent field

  • July 1, 2026
  • 1 reply
  • 0 views

We observed that after a subscriber clicks the one-click unsubscribe link in an AJO email, and a streaming audience (consent = N) triggers a journey whose Update Profile action sets a custom attribute (optin = false), the consents.marketing.email.val field reverts from N back to Y simultaneously with the Update Profile action's execution — even though the action is configured to update only the custom optin field and never references the consents field at all

according to this post: https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26352

“Specific field values do not seem to update properly after running through an Update Profile node in a journey.” -- this is not the case for us, as the optin field gets updated with update action, however the consent field got reverted back to origin state although we haven’t had interacted or manually changed it from somewhere else.

 

1 reply

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe Employee
Adobe Employee
July 1, 2026

​@ap95 My assumption of what’s happening is that One-click unsubscribe correctly sets: consents.marketing.email.val = "n" (or idSpecific consent) and your update profile node updates optin=false. Now that update triggers UPS profile recomputation while another dataset/profile fragment still containing consent="y" wins merge precedence

Result: consent flips back to "y" even though the journey never touched the consent field.

Can you check whether idSpecific consent exists. Also check merge policy precedence and the dataset used in update profile. Adobe recommends prioritizing the AJO Consent Service Dataset in merge policy.

Terms & ConditionsAccessibility statement

Loading footer...