Source
Experiment types & delivery — found from sitemap — Contentsquare
Checked for Contentsquare on 1 Oct 2026
- Page
- https://docs.contentsquare.com/en/csq-sdk-flutter/experience-analytics/experimental/
- Checked
- 1 Oct 2026, 10:28 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:2b2d4f33e397361709ed12bf2a3a800d1e3fc3a86314c3d10ac1295b1e4e0d48
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Experimental annotation purpose Report an error
“The @experimental annotation is an annotation we apply to certain features within the SDK. This annotation indicates that while the feature is accessible for use, it is not yet fully stable and may undergo changes.”
-
Experimental stability guarantee Report an error
“The experimental annotation is not a guarantee that the feature will be included in the SDK stable release.”
-
Experimental breaking changes Report an error
“Adopting an experimental feature means you are using a feature that could be modified or removed at any time, even without a change in the SDK major version number.”
-
Experimental logs Report an error
“Logs: When using an experimental feature, you will see a log message indicating that the feature is experimental.”
-
Experimental log no data submission Report an error
“Experimental warning log might be visible even when SDK is not started. This does not submit any data to remote. It is only information notifying you that an experimental feature is used.”
-
Experimental changelog updates Report an error
“Changelog Updates: Any introduction of or changes to an experimental feature will be documented in the changelog, ensuring transparency.”
-
Experimental lifecycle paths Report an error
“Experimental features follow one of three potential paths”
-
Experimental deprecation timeline Report an error
“This process involves marking the feature as @deprecated in the upcoming release, signaling to clients that the feature will no longer be supported. The feature will then be fully removed in the following minor version of the SDK.”
-
Experimental feedback channel Report an error
“The most direct way to provide feedback is by submitting a support ticket. When doing so, mention that you are using an experimental feature and provide any relevant details.”
Scores citing this record
- The Product Engineer Experiment types & delivery