Not sure what is your arrangement with your marketing channel processing rule, But for processing rule, the most important aspect is the arrangement of the processing rule, I think in your case you had the Paid search at position 3rd, But it should be at position 1 instead of 3rd.   

Potential Cause How to Check FixMissing eVar values (i.e., no value captured at hit-level)  Use Hit Depth breakdown to see when eVars are assigned.Ensure eVars are set before the tracking call (s.t() or s.tl()).Empty strings ("") being sent instead of a value Look at Network request (b/ss call) and ...

Agree to Disagree, there are many connection which is out of the box, and some are easliy consumable too. But yes you will always have some soruces which you will have to consume without API or connector. But that doesn't mean that it's manual, It will be just one time effort only. So understand you...

Agree with all previous comments, but also keep that in mind Persistent will also play a big role, So keep this also in mind when you do the reporting for Person, Session or events.  

Try this once and see what its showing Break down Products by Hit Timestamp and check if the junk values appear only in older timestamps.

@jonathancastillo  can you try to run this and check if the button click is actually working or not document.querySelector("button").addEventListener("click", () => console.log("Button Clicked!"));And if this is working then go with the solution mention by @Jennifer_Dungan 

@RajatAr  I don't think so there is any out of the box solution, Because keep that in mind if we are doing this for many elements in the freeform table you will not able to read the data, and your report is going to become very slow, so keep all that in mind. My suggestion is that don't use this way

Create a calculated metric with below functionDATEDIFF("minute", purchaseTimestamp, timestamp)This function calculates the difference between timestamp and purchaseTimestamp in minutes.

You can achieve this using Adobe Experience Platform Query Service (SQL) by categorizing records based on the time difference between timestamp and purchaseTimestamp

@U19977  are you blocking the tag firing for Adobe tags if the performance cookies are by default is turned off, in that case you will loose loads of traffic, and every less people will go and accept the performance cookie. the only way i can see is that you have to make sure customer makes a choice...