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-...

Can you share what your profile script looks like and the corresponding audience definition?For "not in other test" it is an out-of-the-box profile which just enables you to create an audience for anyone who isn't already in any other test you have live on your site. So if you ONLY have the 2 tests ...

I think I may have missed part of your question above. The adobe.target.applyOffer({offer: response}); will simply apply the content change Target returns in that getOffer. If there is no test that a visitor qualifies for then nothing will happen. If they qualify for a test with content changes then...

Hi,Sorry if I was confusing. I mean that you could do your DOM element check on the page and then if it returns true you could then send that as a parameter to Target via a getOffer function. Target can also use this "secondary" call to qualify a visitor for a test and return a content change to the...

Entity and profile should be at the same level. Also, I don't see the targetPageParams function. It should probably be after your if condition.Also, the quick way to debug is to monitor the mbox requests from the page this is running. Can you see the expected url parameters on that mbox request? Is ...

Your return can contain a list of parameters that get added.function targetPageParams() {  return "param1=value1&param2=value2&p3=hello%20world";}There are more ways to format your return. You can see examples in help: targetPageParams()​

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...

Looks like you are trying to add a delay in the targetPageParams function. I'd suspect this is why you don't see the DOMElement attribute showing. The targePageParams function cannot way for DOM elements to exist before returning a value. Target's call to the server will have already happened.If you...