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?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @rrrrrraul
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
Could you give an example of which parameters you're referring to? And also ideally a screenshot showing where in the request to Target the parameters are being passed?
@alexbishop I'm referring to the delivery API documentation located here:
https://developer.adobe.com/target/implement/delivery-api/
from here it seems that the same pattern for sending mbox page params that exists for web (JavaScript) API. however when sending data in the pageLoad object here it is not associating it with the mbox.
Hi @rrrrrraul
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
@Gokul_Agiwal I think this is documentation for web (JavaScript), is that correct?
what I'm interested in is how to do this using the Delivery API located @ https://developer.adobe.com/target/implement/delivery-api/
any ideas?
okay I think it's just a request data structure on my end. I changed it up and the internets is working now.
Thanks!
Hello @Gokul_Agiwal,
What would cause pagedata parameters to be removed? Are these configured in AT.js? In recent weeks I've seen several pageLoad parameters disappear, causing test activities to not be delivered because I was using them in an audience.
I see some parameters, however, the ones I'm used to seeing have been removed.
Thanks in advance for your help!
-Brion
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies