Hi @NingLaoShi ,
Adobe Target processes profile parameters on the first call — so if:
The parameter (e.g. industry
, companyName
) is not yet set in localStorage (e.g. before Demandbase script has loaded),
If you don't prevent this, the null will overwrite any previous value in the visitor’s profile
Recommendations:
- Ensure Demandbase Data Is Ready Before Sending Target Call: Use a synchronous approach or callback to delay the Adobe Target call until Demandbase has populated localStorage.
-
Avoid Sending Null Values:
Before assigning parameters, check they’re not null or undefined.
-
Revisit __save=false Usage
__save=false prevents profile data from being saved on that Target call, but:
If your call includes null profile values, __save=false won't prevent overwriting if you're explicitly passing them.
Ensure you're either: Omitting params when they are null or, better, conditionally building your params object to exclude nulls
-
Delay Target Initialization (if using at.js)
If you're using at.js, delay initialization until Demandbase data is guaranteed to be in place