Thanks for the feedback - we will certainly consider this in the future.
In the meantime, you can create segments for each of the continents (ie,
North America would contain a "Country = Canada" OR "Country = United
States of America", etc). Clearly that's manual, but you could do it
once and it should work forever.
Great idea - we have this on our backlog (really multiple ideas) and are
considering in the future. BTW, this doesn't do exactly what you're
asking, but it may help in the meantime - if you use a donut viz, it
will use the top 5 slices and then put everything else into "All
This seems reasonable - is there a reason why you don't turn off Limit
Max Items in this scenario? And if you don't want to show everything,
only select the top 24 cells/rows in the table so you only get 24?
Thanks for your comment here - I want to make sure I'm understanding
correctly. Currently you have two options for the map visualization -
you can either use lat/long values from the mobile SDK, or you can
choose geographic dimension, which will use Countries/Regions/Cities
under the hood (we start with Countries at the world level). Depending
on where you are looking at in the world and your zoom level, we break
countries down by regions, and then eventually by cities.When you say
"you never ge...
Great suggestion - we're actively considering various options for
improving the workspace landing page, and this functionality is
definitely one of them. So some form of this will probably be
implemented in the near future.
If I'm understanding your question correctly, you can have multiple
segments on a panel that consists of a cohort table. If you want
different segments per cohort table, you can wrap each one in a panel
and then add the desired segments to each panel. In the future, we are
considering adding segmentation capabilities to both the inclusion and
return metrics as well (in each cohort table).
Good news everyone - we implemented this last year. It is called
"Breakdown by Position". You can enable it by clicking on the dimension
settings cog and select "Breakdown by Position", and it will work
exactly how you have outlined
Got it, thanks for your added clarification. We would appreciate your
continued feedback as you work with the report consumers, because we may
need to change things in order to accommodate their needs (as you're
suggesting). We'll also consider the "select report suite first" idea.
I apologize, but I'm not understanding why templates don't fulfill what
you're trying to do. I can understand that you would want to choose a
report suite first (your other idea that you mentioned), but you could
create one template that would work for any number of report suites -
you just need to pick the report suite once you load the project and it
should work. But I'm sure I'm missing something from your description.
Trevor is right - we are working toward this - great suggestion.
Although this is a slight paradigm shift, we do have the ability to
create metrics with segments embedded in them (and we recently added the
ability to easily create a segment from a dimension rule when building a
metric). I know it's not the same thing, but you can achieve a similar
result by using the base dimension in a table, but then applying a
metric that has the segment baked into it (with the dimension filtering
Great news! We just recently released the ability to create custom
Workspace templates, which work very similarly to how you've suggested.
You can create a project and save it as a template. Then, when anyone
loads this template, it will not use the template it was saved with, but
whichever report suite they are using (they can also change the report
suite at any time). Now you shouldn't have to make a bunch of copies.
Good news! We actually released this last year - there is a function in
the Calculated Metric Builder called "Approximate Count Distinct", and
it works exactly like you've diagramed - it takes a dimension, and gives
you a count of the unique number of items for that dimension.
Understood. Yeah, the design is that at metric creation time (whether
that's a custom event or a calc metric), you can set the up = good/bad,
and then it should just "work" everywhere. There are a few other places
we leverage this setting.