Yeah, the only other thing I can think of would be to adjust the date range and granularity so the column sum gives you the duplicated data you're looking for. This might take multiple freeform tables, though.

This idea is duplicated by Date Range relative to project's date range​, adding 2 votes here.

Marking as duplicate of: Dynamic date ranges

The date range builder can use any date relative to today, and can roll daily, weekly, or monthly. You can absolutely say the start date to be "current day minus 7 days", then the end date be "current day".The one thing it can't do is be relative to the selected date range. If this is something you'...

For standard page view calls, creating a workspace project with page as the dimension and custom event as a metric would be the way to go.For custom link calls, you'd want to populate an eVar with page name, then send that eVar in all link tracking calls.

Do you have any additional information on pulse extensions and .pv filetypes? My initial searches didn't bring up anything of value.What is your goal of this configuration and file?

It also could be a custom variable - if it's a prop or eVar, you'll want to strip the query string yourself.Were you able to get everything figured out?

I think that's the report Brian was referring to - return visits is a segment that can be used, but daily return visits is not.

The issue is almost guaranteed going to be in 1 of 3 places: Implementation, processing rules, or VISTA rules, the most likely being Processing Rules (as Andrey mentioned).Let us know if you're able to find it, and we can explore some further edge-case scenarios.

Not yet, but there's this idea thread currently open: Workspace to FTP