Skip to content

[Content]: mtus-and-throughput page misleading Journey Step to Compute Credit ratio #6253

Open
@seanhan-segment

Description

@seanhan-segment

What article on segment.com/docs is affected?

https://segment.com/docs/guides/usage-and-billing/mtus-and-throughput/

What part(s) of the article would you like to see updated?

The following statement is misleading:

With Engage, this user falls into one audience, has one computed trait, and falls into one Journeys step, accounting for three compute credits total. Compute credits are not tied to an individual user, so multiple people could fall into these buckets, still accounting for a single compute credit for each trait/audience/journey step.

Each Journey step counts for only 0.5 compute credits. As written, the above paragraph implies one step is 1 compute credit. I'm not sure what "Viewed Page x Computed" is meant to convey - is that actually two Journey steps (which would be 1 CC)? Or is it just one step, in which case it's 0.5. Either way, it should be clarified.

In general, the breakdown of what specifically constitutes a Journey "step" is not well represented in docs. Outside of the above scenario, there's no further mention of steps vs compute credits in the entire "usage-and-billing" page. The most clear mention is in the "Engage Limits" page where it says

Half a credit for each step (up to 250 compute credits)

But

  • That detail feels more appropriate for the usage and billing page
  • Nowhere is it mentioned that certain steps (e.g. splits) can consume multiple billable steps/CCs. Since a split "step" with 4 branches is actually counted as 4 billable steps / 2 compute credits. Nuances like this should be conveyed somewhere (again the billing page seems like the right spot).

Additional information

No response

Metadata

Metadata

Assignees

Labels

contentWhen the bug is about content that needs to get fixedstaletriage

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions