I'm seeing issues with the pageLoad parameters not working in Adobe Target Delivery API calls
I'm under the impression that these properties should be available for audience segmentation for use with the associated mbox. However, I am not seeing the properties available in the audience definition custom audience associated with the mbox. Does anyone know how/why this is?
Hi @rjbu
Are you referring to Page Parameters? which generally called “mbox parameters”. These are name/value pairs passed in directly through page code that are not stored in the visitor’s profile.
For this, 2 methods are used - targetPageParams() and targetPageParamsAll.
The parameters passed through above methods can be seen in Audience section under Adobe Target
And the other's way to get the data in Target and used for Audience, In- Page Profile attributes, These are name/value pairs passed directly through page code that are stored in the visitor’s profile for future use.
Here is the guide or help documentation
In case, if you're looking any specific use case, please reply
Hi @rjbu
Are you referring to Page Parameters? which generally called “mbox parameters”. These are name/value pairs passed in directly through page code that are not stored in the visitor’s profile.
For this, 2 methods are used - targetPageParams() and targetPageParamsAll.
The parameters passed through above methods can be seen in Audience section under Adobe Target
And the other's way to get the data in Target and used for Audience, In- Page Profile attributes, These are name/value pairs passed directly through page code that are stored in the visitor’s profile for future use.
Here is the guide or help documentation
In case, if you're looking any specific use case, please reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
