You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because we talk a lot about this on Slack, but it's not documented here:
Is there enough concern about the seasonal trends to:
(a) take off the triangles? (small task)
(b) overlay last year/month/week (large task)
(c) do something else?
I think the question boils down to...are the triangles more helpful than hurtful? We have many applications with seasonal trends where the triangles aren't useful and possibly misleading...unless it's to see that we're hitting a new season. We also have applications that we do want to know if the traffic is going up/down right now (so in those cases, the triangles are useful).
The reason I think (b) is a "large" task is because we have not currently explored GA further than 1 year out. That would require us using the data that we've been collecting via Jenkins. I won't call it an XL task, because I do think it'll be pretty straightforward, but just to be safe, calling it "large".
The text was updated successfully, but these errors were encountered:
Because we talk a lot about this on Slack, but it's not documented here:
Is there enough concern about the seasonal trends to:
(a) take off the triangles? (small task)
(b) overlay last year/month/week (large task)
(c) do something else?
I think the question boils down to...are the triangles more helpful than hurtful? We have many applications with seasonal trends where the triangles aren't useful and possibly misleading...unless it's to see that we're hitting a new season. We also have applications that we do want to know if the traffic is going up/down right now (so in those cases, the triangles are useful).
The reason I think (b) is a "large" task is because we have not currently explored GA further than 1 year out. That would require us using the data that we've been collecting via Jenkins. I won't call it an XL task, because I do think it'll be pretty straightforward, but just to be safe, calling it "large".
The text was updated successfully, but these errors were encountered: