Given the nature of MVT, I think it actually underscores specificity of the KPIs used in reporting. Also, there is an article stating for MVT "Requires mbox-based goal metric goal to get the Element Contribution report. The Element Contribution report does not currently support Analytics metrics." Here is the link: https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4t.html

Product Finding Methods are a great way to say, "how did my visitors find this product, and convert." Examples are: top navigation, search, left navigation, browse, etc. These are captured as an eVar with binding to the product, so persistence and allocation are usually set to last on the conversion (best practice), but you can set it to match your use case, and also override it with Attribution IQ if you want to look at multi-touch. The net: it's a powerful little tool when looking for opportun...

@sarachar wrote: from the CJA session- 305; the example of showing SQL query which is why Adobe CJA is hoping to minimize the time between query-validation-analysis. Is is possible to see the SQL in the background that a request/table CJA is built from? There's a debugger, currently in beta, that will allow you to see the background SQL. It works similar to enabling the debugger in Adobe Analytics, Analysis Workspace, under the Help menu.