Hi sabahatu1546489,You shouldn't modify the throttle rates in this use case. Your groupA/groupB audiences already control that. Set both activities to 100% of traffic (i.e., eligible traffic). If you get into the home page activity your visitor should not be able to see the about us activity. Keep t...

Yes, you have to create a new audience with the definition I supplied.The same is true for the DOMelement audience too. NOTE that requestType will only show up in the drop down if Target has seen that parameter on a request for the target-global-mbox. So you'll need to add the code and load a page ...

Assuming you are using the VEC instead of form based - You can use a Target activity to add the DOM element checker and getOffer function to the PDP. Create an activity on the PDP and use insert element (HTML) to an element that will exist below the element you are looking for (for timing purposes)....

That profile looks fine. You then need to create two audiences one for the GroupA response and one for the GroupB response. Your rule should be something like: visitor profile > twoGroups > contains: GroupA.Is that how your audiences are defined? Then I'd replace the "all visitors" audience with one...

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()​

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