Add attribution FAQ entry on breakdown ordering - #201
Draft
claude[bot] wants to merge 1 commit into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Confidence Score: 5/5The documentation-only change appears safe to merge. The new FAQ matches the documented user-facing ordering limitation, and no concrete incorrect or broken behavior was established.
|
| Filename | Overview |
|---|---|
| docs/features/computed-properties.mdx | Adds a concise FAQ entry documenting attributed-by breakdown ordering with a country and UTM-source example. |
Reviews (1): Last reviewed commit: "Add attribution FAQ entry on breakdown o..." | Re-trigger Greptile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Ross Gonsolvis · Slack thread
Before: The Attribution FAQ on the Computed Properties page didn't explain why the "Attributed by" breakdown can't be reordered above other breakdowns. Users had no documented answer for why the breakdown always stays at the bottom of the breakdown stack.
After: A new FAQ entry (5) explains that the "Attributed by" breakdown is always applied last, so any breakdown added afterward is placed above it, and that attribution is computed within the boundaries of the breakdowns that precede it. It includes a worked example: breaking down by Country and then by "Attributed by UTM Source" computes the attribution model separately within each country.
How: Added as entry 5 in the "Attribution FAQ" section of
docs/features/computed-properties.mdx.