There is another variable, 'Days Since Last Visit' that provides the granular days.Regardless, to solve this you would likely need to use Data Feeds or Data Warehouse in lieu of Analysis Workspace or Report & Analytics.The primary reason being that both 'return frequency' and 'days since last visit'...

As Curtis mentioned it is a result of the exit rate metric.  One option is to wrap in a checker to only evaluate rows in which visits is greater than or equal to one.  Then you could choose to not display a value when the result is zero.  The rows will be there, but with empty values.You are going t...

One method within the Adobe ecosystem would be to leverage the s.hitgovernor plugin.https://docs.adobe.com/content/help/en/analytics/implementation/javascript-implementation/plugins/hitgovernor.html

If your current data layer works for you - then keep using it.  Many people use the array approach because it aligned with the WC3 recommendations.  

Have you contacted Client Care?  Alternatively you might try to set up a new request for a single day of data and see if it comes through.

Client care should still be accessible by either chat or telephone.

I would recommend contacting client care.  Imports can take up to 72 hours to sync, but that seems like a long time for an import that could be completed via browser.

Updating a new value to a specific key will overwrite the existing relationship.  All instances of 123 would relate to new value once the sync occurs.

If you stack or add multiple segments it will essentially behave like the cross section of a Venn Diagram.So if you stacked the two segments below, it would only return hits to the winter boots page, that occurred in visits in which users also viewed the home page.Only the first visit would be inclu...

Have you considered using Data Sources?  This is typically the tool used for this scenario.https://docs.adobe.com/content/help/en/analytics/import/data-sources/datasrc-home.html