Brandon, this looks like an amazing solution to your problem. Eventually you may want to make sure all the data is coming correctly, but this solution beautifully incorporates a great safety factor.Hyder
Yes, that is correct. It will not affect. I did not say that as Saneesh had already covered it.My question/argument to you was regarding, is it necessary to use Transaction ID if it is not being used for binding? Why not use an evar so that the transaction ID value is available in the reports as wel...
If you want to do this level of customization, the preferred tool would be Adobe Report Builder.It will allow you to do larger breakdowns and get data from multiple report suites. -Hyder
If you are looking at requests in the browser, check for pe and pev2 parameters. If the parameters are not present - it is a page viewIf the parameters are present - it is a non-page view (custom link, download link, exit link)-Hyder
So here are the things to note:Are you referring to the TransactionID column? If so, do you have transaction ID variable enabled for the report suite?The Transaction ID is used to bind the same transaction happening over two or more different hits. If each transaction id is only ever present in one ...
Another advantage of capturing pageURL on each page apart from them not being present in the standard reports as Suneesh mentioned, is that evars allow for 255 characters, while props allow 100 characters only.
Check if your event configuration is set to numeric.I may be wrong about this, but even if the event is a counter, it would accept numeric values to increase the counter by that number.
You can approach this in two ways:1. Create a HIT based segment and apply it to the report. Then in the report run for the instances as a whole. 2. DO a classification of pages report to group the pages together. Segmentation would be the quick method. Classifications would take some time, but would...