We are working on defining how visitor stitching should work so that this problem is resolved.

We can handle documentation updates at any time. I will pass this info along to our KB team to hopefully get the documentation clarified. Thanks for submitting!

Is there any reason to have what we call the "traveling menu," the one that pops up when you click on the line item itself? Couldn't we have just the breakdown menu and it would be just as good?

I think @spectaprod's solution is very good; there are a lot of uses for Previous Page data in a variable, and there is a plug-in which makes it very easy. However, I will leave voting open in case others feel that this is a must-have out of the box.

Let me ask this: Which would be better? A.) Making the number of 2-item correlations unlimited (but you still have to set them up)B.) Keeping the number of 2-item correlations the same and allowing you to create/edit up to four 5-item and two 20-item correlations without contacting ClientCare I gues...

Dan, that is a slick use of Processing Rules. Do you have ClientCare serialize the events so they are counted only once per visit? Or do you leave them unserialized and treat them as "New Visitor Page Views" and "Repeat Visitor Page Views?"

Very cool suggestion. Thanks--I think I get now.

Ah, so to be able to say something like [menu clicks] / [menu impressions]? Something like that?

Can you expound on this a bit? The tool offers calculated metrics, so you could build a CTR metric which would be defined as [clicks] / [impressions], and then pull that into a report showing Ad ID, Campaign, etc. as the dimension. Can you describe how what you need is different?

I apologize that this status is vague, but hopefully it is understood as good news