Hi Maggie, were you able to get this resolved?

This is almost always due to multiple image requests going out on page load.This could be due to a number of things - anywhere from link tracking calls to other components of your site sending hit data. The first thing I'd do is open your site with the Experience Cloud debugger and double check all ...

There are two recommendations I'd have:Disable 'override last touch channel' for Direct - this should be the case by default for newer report suites, but you can double check this in the Marketing Channel Manager in the Admin Console.Segment out Direct - create a segment with the following definitio...

So I did some testing on my end, and at a minimum, users have access to calculated metrics to any report suites they have access to.Another thing you can try is to Approve Calculated Metrics​, which should make them accessible to other users in the organization.

In your specific instance, the difference might be due to tracking code changing values mid-visit. If someone manages to stumble across two tracking codes, then make an order, they would be caught in the visit-based segment while being excluded in the hit-based segment.

Hi Natalia, were you able to get the issue resolved?

It depends on what metrics you're using. If you're using anything that is not hit-based, like visits or unique visitors, they would not add up. If you're using hit-based metrics like custom events, they'll likely end up pretty close.

Since it's just a custom report, you can save the custom report as a new one, then name it correctly there. Once it's correctly named, you can delete the old one.

I'm afraid there isn't an automatic way to accomplish this. If you're looking at a 12-month period, you can create a segment where visits are greater than or equal to 60 (since 12x5=60).You'd want to adjust the 60 threshold based on your date range, though. There currently isn't a way to dynamically...

This wholly depends on the report complexity. If it's a complex API request using multiple breakdowns, metrics, and segments for an extended date range, it is very possible for the request to take longer than 10 minutes.Your best bet is going to be to either wait a bit longer, or simplify the reques...