Hey team.
A note about the visitor profile parameters.
The Target audience builder UI does not list a profile parameter unless it has been already sent to Target with an at.js getOffers or with an alloy("sendEvent") request. I just discovered that with the Journey Optimizer Decisions API of the mobile SDK this is not working.
That is: sending a profile parameter as part of an updateProposition request does not enable that profile parameter in the Target Audience UI (see the snapshot below).
If this is the meant behavior, why not to include in the documentation the fact that a new profile parameter should be sent to Target before the audience creation? And why not to include the expected delay time to have the parameter available in the UI?
Thanks,
Alberto
Issue in ./help/main/c-target/c-audiences/c-target-rules/visitor-profile.md
Hey team.
A note about the visitor profile parameters.
The Target audience builder UI does not list a profile parameter unless it has been already sent to Target with an at.js getOffers or with an alloy("sendEvent") request. I just discovered that with the Journey Optimizer Decisions API of the mobile SDK this is not working.
That is: sending a profile parameter as part of an updateProposition request does not enable that profile parameter in the Target Audience UI (see the snapshot below).
If this is the meant behavior, why not to include in the documentation the fact that a new profile parameter should be sent to Target before the audience creation? And why not to include the expected delay time to have the parameter available in the UI?
Thanks,
Alberto
Issue in ./help/main/c-target/c-audiences/c-target-rules/visitor-profile.md