Hi @Luca_Lattarini,The help section has a special page on limits of various parameters and attributes for Target. Entity.ids are limited to 1000 characters. However, in practice it is more convenient to keep the entity.id's to around 50 characters or less because they are easier to view in the UI (n...

Hi @Sundhara,I presume you used the test-duration calculator to determine how long the test should be run, and you are wondering if statistically speaking if letting it run longer is going to compromise the statistical calculations. I think the "days" measure is the less important measure of duratio...

@garora8 Can you share a screen shot of the page? Or if you prefer DM me the URL and I can take a specific look?

Hi @KeithF53,Two+ users on a single device and therefore same Target profile can be a little tricky as your noticing. Profile parameters (the stuff under "visitor profile" when setting up audiences) are sticky to the profile and can't be "cleared" like your wondering about. They can be updated/overw...

Hey @ambikaTewari_ATCI,I'm sure you already know the top recommendation: Fix the customer attributes data file so it doesn't have the double quotes surrounding the ids.In help for ECID and Customer IDs the docs do say to NOT use encoded values in your ids (within the "important" section). Which I gu...

I'd think you could add a rule in Launch to fire the trigger view on page load if some condition exists (e.g., a hash value is in the url). I've done something similar with JS on the page. Here's my sample code if it is helpful:<script> //add triggerview function triggerView(viewName) { // Vali...

You need to pass the cookie value to Target as a custom parameter. Using the targetPageParams() function is a great way to do this for a client-side at.js implementation of Target. Then you can setup an audience rule that checks against the custom parameter you are passing into Target.

Hi @jasmib25972844,That's a good question. I know in general the design limit on recommendations results is 99. However, it could be true that "recently viewed" results could be lower then that. Since we have to keep a list of all the recently viewed in a visitor's profile it makes sense it might be...

If you are using the Visual Experience Composer (VEC) you shouldn't need "regional" mboxes. If using the form composer, and if you are running tests/activities on native mobile apps, server-side, or other IOT then you'll want to use custom locations (aka regional mboxes). That's at least one perspec...

I haven't seen it done exactly has you've described. However, it isn't super uncommon to use other API's for helping get the meta data needed to render the recommendations on pages. I know several clients that just return a list of the ids to recommend from Target and then use that list to call othe...