Just a thought about it, would the following set up work/:Every time someone applies for a job, set s.products and set the product ID to "JobApplication" and then pass all the other eVars I need, including JobID, company ID, discipline etc in the s.products string.This would mean I have one generic product ID for an application (so it won't confuse the product report too much) and I can still capture all the info in need in the eVars.Thanks.Frank

So, in the s.products string, I would have something likes.products=;jobID123;eVar34=companyID_123;eVar28=CompanyName_ABC etc Is that correct? And I would need to set them as merchandising eVars?I still don't fully understand how classifications come into this? I understand what classifications are (we use the Rule builder for our marketing tracking codes) but I don't see how/why they need to be used for this?Thanks.

Thanks.Our current eCommerce implementation is very simple, we only set a product ID, no other info, so if I set the product ID as the Job ID, would it show up in the same report?Also, what exactly do you mean by "Then all the metadata like Company, Location, Discipline, etc. gets uploaded as a Classification."? As mentioned, our eCommerce tagging is very basic so the only part of the s.product variable we use is the Product ID. Could I add all these variables (job Id, company name, company ID, ...

Hi Andrey,Thanks for your reply.The issue I have with using product ID is that we are already using product ID for our B2B eCommerce offering which is in the same report suite, so it might cause issues with that reporting.Thanks,Frank