[DOCS-13875] Add Unity Feature Flags documentation by typotter · Pull Request #35341 · DataDog/documentation

typotter · 2026-03-17T16:20:57Z

What does this PR do? What is the motivation?

Fixes DOCS-13875

Adds documentation for the Datadog Feature Flags SDK for Unity (dd-sdk-unity PR #206).

Documentation added:

content/en/feature_flags/client/unity.md — covers the full direct IFlagsClient API:
- Installation via EDM4U and UPM
- DdFlags.Enable() / DdFlags.Instance.CreateClient()
- SetEvaluationContext with targeting key and attributes
- Typed flag evaluation: boolean, string, integer, double, object
- FlagDetails<T> detail methods (value, variant, reason, error)
- Advanced configuration (FlagsConfiguration constructor options)
Unity card added to the feature flags client navigation partial

Structure follows the iOS and Android Feature Flags doc pattern.

Merge instructions

Merge readiness:

Ready for merge

Additional notes

This PR is ready for technical and editorial review. The SDK PRs (#206, #210) are still open — merge readiness is gated on the SDK landing first.

Preview: https://docs-staging.datadoghq.com/tyler.potter/unity-feature-flags-docs/feature_flags/client/unity/

Add comprehensive Unity Feature Flags documentation with two implementations: 1. unity.md - Direct FlagsClient API (current implementation) - Uses DdFlags.CreateClient() and direct FlagsClient methods - Synchronous flag evaluation (GetBooleanValue, GetStringValue, etc.) - Simpler API without async/await 2. unity-openfeature.md - OpenFeature integration (future/alternative) - Uses OpenFeature Api.Instance.GetClient() - Async flag evaluation methods - Standards-based approach Both pages: - Include cross-links to each other for easy navigation - Follow the structure of Android/iOS feature flags docs - Include installation, setup, evaluation, and advanced config sections - Add Unity card to feature flags client navigation The documentation is ready for preview and user feedback.

Replace full documentation with minimal placeholder pages to test CI: - Keep navigation links and cross-references - Add 'Documentation coming soon' message - Reduce from ~270 lines to ~28 lines each - Test if minimal changes pass all CI checks Full documentation will be added incrementally after CI validation.

github-actions · 2026-03-17T19:37:47Z

Preview links (active after the `build_preview` check completes)

New or renamed files

https://docs-staging.datadoghq.com/tyler.potter/unity-feature-flags-docs/feature_flags/client/unity

…e docs Incremental update to unity-openfeature.md: - Add detailed Overview explaining OpenFeature integration - Add complete Installation instructions (EDM4U, Unity package, Android setup) - Add Initialize SDK section with reference to Unity Monitoring Setup - Add reference links at bottom File size: 27 → 68 lines (+41 lines)

Add back all sections to unity-openfeature.md: - Enable flags - Create and retrieve a client - Set the evaluation context - Evaluate flags (boolean, string, integer, double, object) - Flag evaluation details - Advanced configuration Also fixes duplicate further_reading partial and adds OpenFeature external link to further_reading frontmatter.

Add back all sections to unity.md: - Overview - Installation - Initialize the SDK - Enable flags - Create and retrieve a client - Set the evaluation context - Evaluate flags (boolean, string, integer, double, object) - Flag evaluation details - Advanced configuration

Feature flags are no longer in preview. Removed the callout from both unity.md and unity-openfeature.md to match the other SDK pages (android, ios, javascript, react).

…section - FlagsConfiguration is now immutable (constructor-based, not object initializer) - Add Getting Started quickstart section to unity.md - Fix DdFlags.Instance.CreateClient() throughout unity.md - Update parameter names to match constructor signatures (camelCase) - Add EvaluationFlushIntervalSeconds clamp range [1, 60] to both pages

- Revert FlagsConfiguration to object initializer syntax (mutable properties, PascalCase) - Restore DdFlags.SetEvaluationContext() as static method (not on client) - DdFlags.CreateClient() returns void; OpenFeature client retrieved via Api.Instance.GetClient() - Add Getting Started quickstart section - Restore correct advanced config property names (PascalCase)

- DdFlags is an instance class with immutable FlagsConfiguration (constructor syntax) - DdFlags.Instance.CreateProvider() returns provider for registration with OpenFeature - Provider registered via Api.Instance.SetProviderAsync(provider) - Evaluation context set via OpenFeature standard EvaluationContext.Builder() - No Datadog-specific context types or direct provider method calls - Rename "Create and retrieve a client" section to "Register the provider"

- Evaluation context set via client.SetEvaluationContext(FlagsEvaluationContext) not OpenFeature context builder - DdFlags.Instance.CreateClient() returns FlagsClient (held for context setting); OpenFeature client retrieved separately via Api.Instance.GetClient() - Show Unity coroutine pattern (WaitUntil) for async flag evaluation — MonoBehaviour does not support await - Fix named provider registration: Api.Instance.SetProviderAsync("domain", provider) - Add Getting Started as full MonoBehaviour example - Remove unused openfeature.dev footnote

- Merge unity.md and unity-openfeature.md into one page, OpenFeature-first - Add aliases for old unity-openfeature URLs - Direct FlagsClient API moved to collapsed advanced section at the bottom - Drop FlagDetails documentation (FlagDetails<T> and FlagEvaluationError are now internal) - Flag evaluation details section uses OpenFeature FlagEvaluationDetails types only - Delete unity-openfeature.md and unity.md.bak

- new DatadogFeatureProvider(client) replaces DdFlags.Instance.CreateProvider() - DatadogFeatureProvider is in separate com.datadoghq.unity.flags.openfeature package - using Datadog.Unity.Flags.OpenFeature namespace required - DdFlags.Instance is always non-null (static readonly singleton) - CreateClient() returns IFlagsClient (public interface) - FlagDetails<T> and FlagEvaluationError are public — restore detail methods in direct API section - Installation section updated for two-package architecture and NuGetForUnity

… install step

- Remove all OpenFeature references and the openfeature package install steps - Follow iOS page structure: Enable → Create client → Set context → Evaluate → Advanced config - DdFlags.Enable() / DdFlags.Instance.CreateClient() / client.SetEvaluationContext() - Synchronous typed getters: GetBooleanValue, GetStringValue, GetIntegerValue, GetDoubleValue, GetObjectValue - FlagDetails<T> detail methods documented - FlagsConfiguration uses constructor syntax (immutable) - Backup of previous state at typo/unity-feature-flags-docs-openfeature-backup

drichards-87 · 2026-03-31T17:19:02Z

Created DOCS-13881 for the editorial review.

joepeeples · 2026-04-03T21:02:58Z

+aliases:
+  - /feature_flags/setup/unity/


I don't think we need a redirect because the page never existed at this location.

thanks, good catch!

joepeeples · 2026-04-03T21:07:48Z

+
+1. Install the [External Dependency Manager for Unity (EDM4U)][1]. This can be done using [Open UPM][2].
+
+2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.


Suggested change

2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.

2. Add the [Datadog SDK Unity package][3] using its Git URL `https://github.com/DataDog/unity-package.git`.

joepeeples · 2026-04-03T21:10:36Z

+);
+{{< /code-block >}}
+
+This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations once the background operation completes.


Suggested change

This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations once the background operation completes.

This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations after the background operation completes.

joepeeples · 2026-04-03T21:11:24Z

+
+## Set the evaluation context
+
+Define who or what the flag evaluation applies to using a `FlagsEvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to ensure proper targeting.


Suggested change

Define who or what the flag evaluation applies to using a `FlagsEvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to ensure proper targeting.

Define who or what the flag evaluation applies to using a `FlagsEvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to help ensure proper targeting.

- Remove /feature_flags/setup/unity/ alias (URL never existed) - Simplify Git URL installation step wording - ensure -> help ensure (Vale rule) - once the -> after the (Vale rule)

typotter · 2026-04-07T21:20:40Z

Thanks Joe for the fixes and nav-bar add. PTAL

joepeeples

LGTM!

* Add Unity Feature Flags documentation Add comprehensive Unity Feature Flags documentation with two implementations: 1. unity.md - Direct FlagsClient API (current implementation) - Uses DdFlags.CreateClient() and direct FlagsClient methods - Synchronous flag evaluation (GetBooleanValue, GetStringValue, etc.) - Simpler API without async/await 2. unity-openfeature.md - OpenFeature integration (future/alternative) - Uses OpenFeature Api.Instance.GetClient() - Async flag evaluation methods - Standards-based approach Both pages: - Include cross-links to each other for easy navigation - Follow the structure of Android/iOS feature flags docs - Include installation, setup, evaluation, and advanced config sections - Add Unity card to feature flags client navigation The documentation is ready for preview and user feedback. * Simplify Unity Feature Flags docs to placeholders Replace full documentation with minimal placeholder pages to test CI: - Keep navigation links and cross-references - Add 'Documentation coming soon' message - Reduce from ~270 lines to ~28 lines each - Test if minimal changes pass all CI checks Full documentation will be added incrementally after CI validation. * Add Overview, Installation, and Initialize SDK sections to OpenFeature docs Incremental update to unity-openfeature.md: - Add detailed Overview explaining OpenFeature integration - Add complete Installation instructions (EDM4U, Unity package, Android setup) - Add Initialize SDK section with reference to Unity Monitoring Setup - Add reference links at bottom File size: 27 → 68 lines (+41 lines) * Restore full OpenFeature docs for Unity Feature Flags Add back all sections to unity-openfeature.md: - Enable flags - Create and retrieve a client - Set the evaluation context - Evaluate flags (boolean, string, integer, double, object) - Flag evaluation details - Advanced configuration Also fixes duplicate further_reading partial and adds OpenFeature external link to further_reading frontmatter. * Restore full Unity Feature Flags direct API documentation Add back all sections to unity.md: - Overview - Installation - Initialize the SDK - Enable flags - Create and retrieve a client - Set the evaluation context - Evaluate flags (boolean, string, integer, double, object) - Flag evaluation details - Advanced configuration * Remove preview callout from Unity Feature Flags docs Feature flags are no longer in preview. Removed the callout from both unity.md and unity-openfeature.md to match the other SDK pages (android, ios, javascript, react). * Update Unity Feature Flags docs with correct API and Getting Started section - FlagsConfiguration is now immutable (constructor-based, not object initializer) - Add Getting Started quickstart section to unity.md - Fix DdFlags.Instance.CreateClient() throughout unity.md - Update parameter names to match constructor signatures (camelCase) - Add EvaluationFlushIntervalSeconds clamp range [1, 60] to both pages * Fix Unity OpenFeature docs to match openfeature SDK worktree - Revert FlagsConfiguration to object initializer syntax (mutable properties, PascalCase) - Restore DdFlags.SetEvaluationContext() as static method (not on client) - DdFlags.CreateClient() returns void; OpenFeature client retrieved via Api.Instance.GetClient() - Add Getting Started quickstart section - Restore correct advanced config property names (PascalCase) * Rewrite Unity OpenFeature docs to match intended API design - DdFlags is an instance class with immutable FlagsConfiguration (constructor syntax) - DdFlags.Instance.CreateProvider() returns provider for registration with OpenFeature - Provider registered via Api.Instance.SetProviderAsync(provider) - Evaluation context set via OpenFeature standard EvaluationContext.Builder() - No Datadog-specific context types or direct provider method calls - Rename "Create and retrieve a client" section to "Register the provider" * Fix Unity OpenFeature docs to match intended API design - Evaluation context set via client.SetEvaluationContext(FlagsEvaluationContext) not OpenFeature context builder - DdFlags.Instance.CreateClient() returns FlagsClient (held for context setting); OpenFeature client retrieved separately via Api.Instance.GetClient() - Show Unity coroutine pattern (WaitUntil) for async flag evaluation — MonoBehaviour does not support await - Fix named provider registration: Api.Instance.SetProviderAsync("domain", provider) - Add Getting Started as full MonoBehaviour example - Remove unused openfeature.dev footnote * Consolidate Unity Feature Flags into a single page - Merge unity.md and unity-openfeature.md into one page, OpenFeature-first - Add aliases for old unity-openfeature URLs - Direct FlagsClient API moved to collapsed advanced section at the bottom - Drop FlagDetails documentation (FlagDetails<T> and FlagEvaluationError are now internal) - Flag evaluation details section uses OpenFeature FlagEvaluationDetails types only - Delete unity-openfeature.md and unity.md.bak * Remove openfeature URL aliases from Unity docs * Update Unity Feature Flags docs for PR #210 API changes - new DatadogFeatureProvider(client) replaces DdFlags.Instance.CreateProvider() - DatadogFeatureProvider is in separate com.datadoghq.unity.flags.openfeature package - using Datadog.Unity.Flags.OpenFeature namespace required - DdFlags.Instance is always non-null (static readonly singleton) - CreateClient() returns IFlagsClient (public interface) - FlagDetails<T> and FlagEvaluationError are public — restore detail methods in direct API section - Installation section updated for two-package architecture and NuGetForUnity * Fix installation: NuGetForUnity is a transitive UPM dep, not a manual install step * Rewrite Unity Feature Flags docs: direct API only, no OpenFeature - Remove all OpenFeature references and the openfeature package install steps - Follow iOS page structure: Enable → Create client → Set context → Evaluate → Advanced config - DdFlags.Enable() / DdFlags.Instance.CreateClient() / client.SetEvaluationContext() - Synchronous typed getters: GetBooleanValue, GetStringValue, GetIntegerValue, GetDoubleValue, GetObjectValue - FlagDetails<T> detail methods documented - FlagsConfiguration uses constructor syntax (immutable) - Backup of previous state at typo/unity-feature-flags-docs-openfeature-backup * add new Unity page to side nav * Address joepeeples review comments on unity.md - Remove /feature_flags/setup/unity/ alias (URL never existed) - Simplify Git URL installation step wording - ensure -> help ensure (Vale rule) - once the -> after the (Vale rule) --------- Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>

github-actions Bot added the Architecture Everything related to the Doc backend label Mar 17, 2026

typotter force-pushed the tyler.potter/unity-feature-flags-docs branch from e593405 to bc89345 Compare March 17, 2026 18:48

typotter added 2 commits March 17, 2026 13:13

typotter force-pushed the tyler.potter/unity-feature-flags-docs branch from bc89345 to cac19fc Compare March 17, 2026 19:13

typotter added 13 commits March 17, 2026 13:44

Remove preview callout from Unity Feature Flags docs

5e10195

Feature flags are no longer in preview. Removed the callout from both unity.md and unity-openfeature.md to match the other SDK pages (android, ios, javascript, react).

Remove openfeature URL aliases from Unity docs

42525a5

Fix installation: NuGetForUnity is a transitive UPM dep, not a manual…

42d96ee

… install step

typotter changed the title ~~Add Unity Feature Flags Documentation~~ [DOCS-XXXXX] Add Unity Feature Flags documentation Mar 31, 2026

typotter marked this pull request as ready for review March 31, 2026 16:49

typotter requested review from a team as code owners March 31, 2026 16:49

drichards-87 added the editorial review Waiting on a more in-depth review label Mar 31, 2026

typotter changed the title ~~[DOCS-XXXXX] Add Unity Feature Flags documentation~~ [DOCS-13875] Add Unity Feature Flags documentation Mar 31, 2026

joepeeples added 2 commits April 3, 2026 16:39

Merge branch 'master' into tyler.potter/unity-feature-flags-docs

8176a12

add new Unity page to side nav

5854a21

joepeeples requested changes Apr 3, 2026

View reviewed changes

Address joepeeples review comments on unity.md

ded1f83

- Remove /feature_flags/setup/unity/ alias (URL never existed) - Simplify Git URL installation step wording - ensure -> help ensure (Vale rule) - once the -> after the (Vale rule)

typotter requested a review from joepeeples April 7, 2026 21:20

joepeeples approved these changes Apr 8, 2026

View reviewed changes

jhgilbert approved these changes Apr 8, 2026

View reviewed changes

typotter merged commit 53d8922 into master Apr 8, 2026
30 of 36 checks passed

typotter deleted the tyler.potter/unity-feature-flags-docs branch April 8, 2026 19:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[DOCS-13875] Add Unity Feature Flags documentation#35341

[DOCS-13875] Add Unity Feature Flags documentation#35341
typotter merged 18 commits intomasterfrom
tyler.potter/unity-feature-flags-docs

typotter commented Mar 17, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Mar 17, 2026 •

edited

Loading

Uh oh!

drichards-87 commented Mar 31, 2026

Uh oh!

joepeeples Apr 3, 2026

Uh oh!

typotter Apr 7, 2026

Uh oh!

joepeeples Apr 3, 2026

Uh oh!

typotter Apr 7, 2026

Uh oh!

joepeeples Apr 3, 2026

Uh oh!

typotter Apr 7, 2026

Uh oh!

joepeeples Apr 3, 2026

Uh oh!

typotter Apr 7, 2026

Uh oh!

typotter commented Apr 7, 2026

Uh oh!

joepeeples left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants


		1. Install the [External Dependency Manager for Unity (EDM4U)][1]. This can be done using [Open UPM][2].

		2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.

	2. Add the Datadog SDK Unity package from its Git URL at [https://github.com/DataDog/unity-package][3]. The package URL is `https://github.com/DataDog/unity-package.git`.
	2. Add the [Datadog SDK Unity package][3] using its Git URL `https://github.com/DataDog/unity-package.git`.

	This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations once the background operation completes.
	This method fetches flag assignments from the server asynchronously in the background. The operation is non-blocking and thread-safe. Flag updates are available for subsequent evaluations after the background operation completes.


		## Set the evaluation context

		Define who or what the flag evaluation applies to using a `FlagsEvaluationContext`. The evaluation context includes user or session information used to determine which flag variations should be returned. Call this method before evaluating flags to ensure proper targeting.

		aliases:
		- /feature_flags/setup/unity/

Conversation

typotter commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do? What is the motivation?

Merge instructions

Additional notes

Uh oh!

github-actions Bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Preview links (active after the build_preview check completes)

New or renamed files

Uh oh!

drichards-87 commented Mar 31, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

typotter commented Apr 7, 2026

Uh oh!

joepeeples left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

typotter commented Mar 17, 2026 •

edited

Loading

github-actions Bot commented Mar 17, 2026 •

edited

Loading

Preview links (active after the `build_preview` check completes)