Null values of profile parameters

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),

• Target may receive and store a null (or empty) value into the visitor profile.

If you don't prevent this, the null will overwrite any previous value in the visitor’s profile

Recommendations:

1. 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.

2. Avoid Sending Null Values:

   Before assigning parameters, check they’re not null or undefined.

3. 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

4. Delay Target Initialization (if using at.js)

   If you're using at.js, delay initialization until Demandbase data is guaranteed to be in place

Hi @ninglaoshi ,

1. First, send your Target request with __save=false to delay saving — this prevents partial or null data from being saved.
2. Once your Demandbase data is loaded and content is displayed, send another Target request without __save=false to actually save the profile parameters.