Hey Scott, this is definitely something we're aware of and we're currently working on a better method for more granular control over the lookback window. As a short term workaround for your use case set the reporting date range to start on Dec 31 (as you mentioned), but use a segment to filter the r...

Fantastic feedback - we're looking at improving flow, so your comments couldn't have come at a better time. I'll be sure to take this back to the team.

Hi, thanks for the suggestion! We actually did an internal POC for this, but it turns out that regex engines were too slow for us to return reports in a timely manner. We'll keep looking at it though, thanks for posting!

The histogram is based on the instances metric of your dimension rather than the metric itself. It's simply a view of how many touches users have to your dimension in general.

Thanks for the feedback. For what it's worth, you can reproduce any and every visualization in the Attribution Panel yourself in a blank panel. We made panels such that a user could reconstruct them manually if they wanted to. There's no reason you couldn't look at the same histogram or Venn, etc. t...

I like your idea! Certainly not an easy change by any stretch of the imagination, but I'll take this feedback back to the team. Last question for you - if we charged not only by hit count, but by size of hit (I guess that'd be similar to volume or GB pricing) would that help ease the strange impleme...

Great point. The reason for this is because we have no way of knowing how to apply an attribution model from outside of the calculated metric builder. For example, if you had revenue / orders and you applied "Linear" to it - does that mean (linear revenue) / (linear orders) or (linear revenue) / ord...

Very interesting idea/comment.If we did away with billing by server call volume, do you have a suggestion on how we could structure an alternative pricing model that wouldn't have bad incentives?

Ah gotcha - a segment would include both dogs and cats, a breakdown of "small" by product would only give you "dogs" though. Sub-hit segmentation is a common feature request - I'll pass this along to the team.

I should also mention that Attribution IQ will be available to customers on the new SKUs: Foundation, Select, Prime, and Ultimate. Also fwiw, participation has always been available in calculated metrics which surfaces in Workspace.