Debugging custom attribute returned value into experience | Community
Skip to main content
S
sam_at_conversion
New Participant
March 17, 2021
Solved

Debugging custom attribute returned value into experience

  • March 17, 2021
  • 3 replies
  • 1369 views

Hi, 

 

I'm looking to get the value of a custom attribute dynamically logged into one experience. We have a custom attribute set up as 'Customer Attributes.lifestage'. I know that this is server side data by is there a way I can return this value straight into the custom code area of an A/B experience. 

 

I do not want to set this up as an audience as we want to dynamically change the copy based on the customer attribute value. For example, something like:

if (CustomerAttr.lifestage === "Retired") { console.log('User is retired'); } else { console.log('User is not retired'); }

Any help is appreciated! 

Thanks

Sam

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Pawan-Gupta

Audiences are better options as it has wide range for similar implementation via ContentHub or mbox parameter etc...

but if you dont want to go that route then

 

There are other approaches i can suggest (going on more level deeper not handling at audience rather through offer)

1. via passing setting and getting through contexthub and using that attribute in your HTML offer

2. or create client side object and use those in HTML offer

 

or 

even you can handle it through globalmbox if this scenario spreaded across site.

 

hope it helps!!

3 replies

Rajneesh_Gautam_
Rajneesh_Gautam_
New Participant
March 26, 2021

Did you try ResponseTokens? Customer Attributes are available under Response Tokens so you can view value under Preview of Adobe Target response under Developer Tools.

 

Regards,

Rajneesh

Gaureshk_Kodag
Gaureshk_Kodag
Employee
March 25, 2021

I guess

if(${crs.aliasid.columnname} == 'somevalue')

{ //Do something }

Else{do nothing}

would work.

Pawan-Gupta
Pawan-GuptaAccepted solution
New Participant
March 23, 2021

Audiences are better options as it has wide range for similar implementation via ContentHub or mbox parameter etc...

but if you dont want to go that route then

 

There are other approaches i can suggest (going on more level deeper not handling at audience rather through offer)

1. via passing setting and getting through contexthub and using that attribute in your HTML offer

2. or create client side object and use those in HTML offer

 

or 

even you can handle it through globalmbox if this scenario spreaded across site.

 

hope it helps!!

    Terms & ConditionsAccessibility statement

    Loading footer...