Profile Script Lifetime

[#1]

I recently created a profile script which captures whether or not the login page has been seen by a visitor:

if(page.url.indexOf("/login") > -1){

  return "hasSeenLogin"

}

Checking with mboxTrace, I have seen the user parameter working within the same session as the login page view. However when I go back and check again a day or so later, I can no longer see the parameter. 

Is there a reason that it is not remaining for 14 days as per this: https://marketing.adobe.com/resources/help/en_US/target/ov/c_visitor_profile_lifetime.html?

Thanks,

Chris

[#2 · Accepted solution]

Hi Chris ,

 I assume your query is resolved . If not, please do let us know so that we can further help you with the same.

Regards

Parit Mittal

[#3]

You might also want to write out the profile script into an offer so you can see the value easily as you test it out. Here is some info on it: https://marketing.adobe.com/resources/help/en_US/target/target/r_passing-profile-attributes-to-the-h... 

[#4]

Hi Chris,

The syntax profile.name are ONLY used if you send it in via a mbox call. If you make Profile scripts, the syntax (for the same end result) are user.name...

Via mbox call: https://marketing.adobe.com/resources/help/en_US/target/ov/c_pass_parameters_to_global_mbox.html
Via profile script: https://marketing.adobe.com/resources/help/en_US/target/target/c_script_profile_attributes.html (so i guess the code example in this link, using code like profile.get('model')  are incorrect...)

/Løjmann

[#5]

Hi Løjmann,

Thanks for replying. I have tried testing this and it doesn't appear to be working. The test only appears when I go to the login page in the same session.

Also, I tried adding the following to the test to see if anything was being passed:

var param = user.get('Has_Seen_Login_Page') alert(param);

So far this has not worked, even in the same session and with other user parameters, such as IP: 

[img]https://content.screencast.com/users/Mezzo_Chris/folders/Jing/media/ae57b524-0224-4c94-b82b-a5826537...

Is there a significant difference between user and profile params that would be causing this?

Many thanks,

Chris

[#6]

Hi,

I think you only see the profile parameters that are sent on the call, not those stored backend... have you tried to setup a test and see if you are included the day after? You can also setup a test, that print out your target profile parameters, that could also help you debug.

/Løjmann