You can access the setup custom events with the following menu path: Site Metrics>Custom Events Metrics > Custom Events. An alternative is you can do a quick search if you do a Quick Search in the bar at the top of the main menu OR you can type / and that will bring up the search bar to query for yo...

Hi Mike,You can still rely on Report Builder to build your fallout reports. The metric is listed as page views, but is in fact instances of visits that made it past each fallout checkpoint (exactly the same criteria as within R&A). You can compare for the same period & fallout logic the 'Visits' ver...

No there is not a way to pull the full paths reports via DW. You might need to leverage a data source such as the full raw clickstream.Best,Brian

Hi Tyler,I am not aware of why there would be missing orders from your full paths report if your logic criteria is consistent. I would verify the date ranges and then try to compare against exact sessions or order IDs perhaps to QA.Best,Brian

While you cannot swap out the visits total count for an orders metric in the full paths report (since the purpose of the report is to illustrate aggregate distinct path counts); you could show full paths only containing your order confirmation page and that would restrict per your requirements.Best,...

Hi Scott,I agree this is a very bad idea and would recommend they work within a tag management system such as DTM or put in place additional code control within each environment if the development team is having trouble keeping track of DEV and Prod. Segmentation across DEV + PROD is not the answer ...

I would bet the Custom Conversion eVar has a longer expiration window which therefore attributes more page views post internal search interaction that the Custom Traffic prop (intrinsically only persists for the hit). So the difference is expected and in line with the configuration settings of the v...

See attached logic- make sure to end with an exclude condition container to 'cap' your page view hits conditions to only 3 times within a visit.[img]PageHome3X.png[/img]

You are on the right track- keep on adding separate containers with equals condition per how many times you need the page to be viewed and you should be set.Compare with the finalized segment filtered against the full paths report to verify your results.Best,Brian

The segment builder does not support RegEx at this time, but you should be able to set a visit container with the criteria within where the given page value was viewed X amount of times. If you have more complicated parameters than that potentially nested containers or sequential segmentation can ac...