Hi @srikoll Our method of doing this (we use at.js 2.3.0) is using the
targetPageParamsAll function which looks a bit like
this:window.targetPageParamsAll = function() { function
_userIsLoggedIn() { // Some logic that returns true or false } return {
"logged_in": _userIsLoggedIn() }; } That way we have the custom mbox
attribute 'logged_in' available on all offer requests. Within Target we
then use this in an Audience. Kr, Thomas
Hi Karen, Indeed the parameters validate these requirements. They get
saved within the target database. It just seems that the Target UI does
not want to fetch them.
That's right. That parameter is not set through profile script but
through a custom profile parameter within the mbox call. This should,
according to the documentation, also appear within the Visitor Profile
attributes within the Audience Builder
(https://docs.adobe.com/content/help/en/target/using/audiences/create-audiences/categories-audiences/visitor-profile.html
point 4, the last sentences).
Timing should not be an issue since more than a day passed by. I did the
api calls to check what they said, just to be sure that the parameters
were indeed saved to the Target Database, and they also show that the
parameters are set correctly on the profile.
Hi, I am building a small POC to try out some ways to capture data using
at.js (version 2.3.0) directly on the page instead of Launch. I attached
some profile specific attributes when sending the pageload request, they
get stored within the profile in Target, but I am unable to use these
parameters when I try to build an Audience in Target using the 'Visitor
Profile' selector. The requestThe response with tracing What step am I
missing? Thanks, Thomas
AdChoices