Looking at Request > execute > pageLoad > parameters at the documentation on this page: https://experienceleague.adobe.com/docs/target-dev/developer/client-side/at-js-implementation/functions-overview/adobe-target-getoffers-atjs-2.html?lang=en I see the maximum param count is set to 50.  However, I'...

Is there a way to programmatically clear data tied to a Visitor Profile?  I'm using it for Customer Attributes but I don't want the segmentation to persist offline, only during session when user is authenticated.

Does anyone know what the maximum amount of values I can add to the custom audience in Target?     For instance I have some parameter == some value in the audience definition.  What is the max number of "some value" I can add?

When uploading a CSV to the Customer Attributes source the first column in the CSV files is being trimmed off of the schema.  Is this expected behaviour?

so for client side the Adobe CDN maps an experience delivered to VisitorID and TntID (taken from AMVC_*** cookie and mbox cookie).  I'm wondering what the mapping mechanism in app is.  In other word, how does Target for app know when a user previously entered into an A, B, C, etc.    

Can anyone here explain how bucketing works for A/B testing with native app (SDK)?

So it seems the reality is that there is no existing pattern (provided by Adobe) for sessionID instantiation/maintenance for a purely server side solution.     This feels like a bit of a disappointment.  There's a requirement for a sessionID, but that sessionID is only provided by the VisitorID serv...

Is there anyone who can explain how pattern for sessionID is supposed to work with the delivery API?   https://developers.adobetarget.com/api/delivery-api/   The documentation states that a sessionID is required, but where is this sessionID supposed to come from and how is it generated?  

Hello all! According to the documentation located here: https://adobetarget-sdks.gitbook.io/docs/core-principles/bucketing I should be able to bucket users into an A/B test experience by passing an arbitrary thirdPartyId parameter with the outbound mbox request.  However, I'm seeing that this is not...

It is set up exactly how it is documented in the Node SDK documentation