gaureshk30144236​ - thanks. PratheepArunRaj​ - any guidance will help.tanvia28417128​ - have you experienced where the -clicked fires but it isn't logged? That is what we are experiencing after going in and setting usecase query parameters and logging what we should see in terms of impressions and clicks. The mbox-clicked fires as expected and we see a clickid in the headers as well, but it doesn't track through except on an experience where the page is the exact same as the VEC experience. exam...

Hi gaureshk30144236​ - I have a similar ask - but with one element. I am seeing the click track, but only seeing the reports populate in A4T for an experience similar to the element in the VEC. We are using the click on the container since we just want to see how much engagement increases or decreases on the container regardless of how many links it might have.The click is id'd and tracking per the tools as you stated above for all of the pages - but the reporting only logs the VEC experience or...

Hi Løjmann - Thanks for the reply - Apologies for my delay - I will respond in a bit. Just got back from vacation.

Hi Parit,Thank you for the response. Option 1 is what we are segmenting with, and is what we want. We are looking to segment based on the OOTB functionality for customer domains based on IP. So if they come in from a particular company's IP/Domain, we can target them.This current test is a POC and we are using our own IP to test. It does work. If I am outside of the domain/IP, I get experience A as expected. If I am inside the domain/IP, I get experience B as expected. That is good. However, if ...