Hi Neetu,This is probably because you are checking a profile that was just created. The profile fetch API has ~30 minute latency before you'll see it showing up. If you try that same ID again you'll probably get the JSON response you are expecting.

Hi Saila,It's possible that your server doesn't allow unknown query parameters to be added into the URL. Our VEC adds a couple of query parameters to the page when loading to help prevent Target from loading any test content that could be live in another activity. You can verify this by trying to lo...

Most definitely! You need to start by choosing single page to setup/compose your test with the visual experience composer (VEC). But then you can layer on a "template" rule to allow a set of urls to qualify for entry in the test.Configure (gear icon) > page delivery > add template rule with "OR" con...

Hey Prarthana,I'd use the mboxTrace debugging tool to see what is returned for your IPs for domainName and then adjust your audience accordingly. Here's the help doc on using the mboxTrace tool: Troubleshooting Content Delivery​. You'll also need to get the auth token (described in the doc). You can...

Okay, if you need both new and return visitors under the same activity for some reason you can use an XT activity to achieve this. Here's how I'd set it up:1. Create a profile script to randomly assign visitors a number between 1-100 (this will be reusable for future tests too). In my example name i...

Hi YogitaBist,If I'm following you correctly, you may not need a profile script for this. It looks like you want to test Experience B against Experince C for return visitors. And if they are a new visitor show only Experience A . I'd maybe treat this as 2 activities.For new visitors (we have an out-...

When you go to Audiences you will find many prebuilt browser selection options. If you need something not already built out (i.e., Safari 11) you can use a Profile Script to evaluate anything in the useragent string. Something like this for your profile script will return a 'true' or 'false':I don't...

You should create a profile script to do this. You can evalauate the URL of the page a visitor is hitting and then store some profile in Target against that visitor. Here is a basic on that will work:You could also layer on some session logic that only set it if it's a new session. This might prove ...

Hi Suchindra,Target's default implementation, for as long as I can remember, has always used first party cookies. Unless you are using a third party ONLY implemenation you shouldn't be affect by change to default settings of third party cookies.

Hi Rama,If you have Target implemented on pages that are created with AEM, and you load those pages in the Target UI to compose a test experience then in response:Target only "loads" those pages temporarily for you to compose the experiences.Target actually saves the content modifications you make a...