From 0e5f6bf68f7fe577470305f82185259a59dff715 Mon Sep 17 00:00:00 2001 From: Phil DelGobbo Date: Thu, 4 Jun 2026 14:43:03 -0400 Subject: [PATCH 1/2] Update first touchpoint explanation in funnels documentation Clarified the description of the first touchpoint attribution mode based on this ticket: https://posthog.slack.com/archives/C04G7E5K5U3/p1778527993829529?thread_ts=1778505884.017919&cid=C04G7E5K5U3 Originally indicated this setting looks for the first instance of a property within the confines of the funnel. In truth the first occurrence of any funnel event, even outside the date range of the funnel, is included. --- contents/docs/product-analytics/funnels.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents/docs/product-analytics/funnels.mdx b/contents/docs/product-analytics/funnels.mdx index f799cfbedc0a..e32c41f157ad 100644 --- a/contents/docs/product-analytics/funnels.mdx +++ b/contents/docs/product-analytics/funnels.mdx @@ -209,7 +209,7 @@ In this case, you can choose from which step the properties should be selected f ##### 1. First touchpoint -In this case, the first property value seen in any of the steps is chosen. +In this case, the first property value seen in any occurrences of the funnel events. Consider this example sequence of events: From 9d17787e40062fe64099d1d5557dce5c698fe3fe Mon Sep 17 00:00:00 2001 From: Phil DelGobbo Date: Thu, 4 Jun 2026 14:49:48 -0400 Subject: [PATCH 2/2] Clarify evaluation contexts impact on local evaluation Clarify that evaluation contexts do not impact local evaluation behavior. --- contents/docs/feature-flags/creating-feature-flags.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/contents/docs/feature-flags/creating-feature-flags.mdx b/contents/docs/feature-flags/creating-feature-flags.mdx index 49569745b248..17618b1facbd 100644 --- a/contents/docs/feature-flags/creating-feature-flags.mdx +++ b/contents/docs/feature-flags/creating-feature-flags.mdx @@ -281,6 +281,7 @@ Flags without evaluation contexts continue to evaluate for all requests (default - SDKs must send the `evaluation_contexts` parameter with matching contexts for the flag to evaluate (the legacy `evaluation_environments` parameter is also supported) - Flags with no evaluation contexts will evaluate for all requests (default behavior) - At least one evaluation context must match for the flag to be included in the evaluation +- Evaluation contexts and (and evaluation runtime) do not affect local evaluation behavior