AEM–Target: Location (hex) hash mismatch between cq:ActivitySettings and runtime page hash

[test1234567]

Hello Community,

We have an AEM–Adobe Target integration in place and are encountering an issue where the hexadecimal location hash stored in cq:ActivitySettings/locations does not match the runtime-generated Target location hash on the page. Because of this mismatch, the activity is not binding to (or activating on) the page.

Key observations:

          This hash is stored in the locations node after we save and sync the activities, before publishing the actual page.

• In the working environment, the full hash value is written correctly under cq:ActivitySettings/locations.
• In the non‑working environment, the hash stored under cq:ActivitySettings/locations is only partially captured (truncated) and does not match the hash generated at runtime.
• Result: Target activities do not bind to the page in the non-working environment.

Has anyone seen a scenario where a custom publish/workflow path interferes with the generation or persistence of the full location hash in cq:ActivitySettings? Any insight into which step (or service user / permission / event listener) could be skipped or blocked would be helpful.

Working Environment:

Non-Working Environment: 

Any guidance on root causes or what specifically triggers the full hash generation (that a custom workflow might be bypassing) would be greatly appreciated.

Thank you.

@davidjgonzalezzzz @EstebanBustamante @RiteshY18 @Gokul_Agiwal @Umesh_Thakur @pradnya_balvir @Amelia_Waliany @ParitMittal @pradnya_balvir
@Umesh_Thakur @AmitVishwakarma @HrishikeshKagne