Hi,Why don't you just use the first part of the URL (mysite.com/search/posts) in your condition?/Løjmann

Classification would make you a report where historical data are merged, and that may seems like the least bad option. However, I would consider to fix the data collection (either on-site/TMS or via processing rule) so you do not store the protocol (http/https) as part of your dimension.../Løjmann

Hi,Such segment won't give you anything, as Facebook isn't considered a search engine by Adobe Analytics.I guess you are adding a tracking code to all your paid activities, and should they use that (Tracking Code/s.campaign) in your segmentation instead... It is good practice to create a tracking co...

Hi Pallavi,It sounds like you need to look at your implementation. Either does your implementation not set the scAdd event (named Cart Additions in the interface) or you are not using the same product name/SKU when adding and ordering./Løjmann

Hi John,As far as I know, the answer is yes. Visitors in other experiments (control group or not) will be excluded./Løjmann

Hi Dwayne,Looking at what data is sent to Adobe, the URL isn't one of them. It may be stored in a prop or eVar server side (via processing rules for examples), but I can't see that. You will have to ask your implementation team about that.Looking at the URL: https://www.ers.usda.gov/publications/pub...

Hi Judy,You will have to request that via Client Care./Løjmann

Hi Frank,Do debug what Jantzen says, in your page load rule, write the datalayer value to the console to validate if that is the case. Youw can do that via the custom code Input/tab./Løjmann

Hi Dwayne,Data Warehouse is a interface to extract data, you do not want to ude that as your everyday reporting interface.Can you post a few URLs here where Adobe does not get the query strings, then I can quickly check your implementation as I suspecthat one for removing the query strings.../Løjman...

Perfect, glad to help :)/Løjmann