<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=571997) </details> <!--IssueSummary end--> Based on this [comment](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/216275/diffs#note_2973021530), we want to add `have_excluded_experiment matcher` to the GLEX itself. <details> <summary>Original description</summary> The following discussion from gitlab-org/gitlab!205504 should be addressed: - [ ] @dstull started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/205504#note_2771853193): (+2 comments) > **question (non-blocking):** > > Did we try using the [exclude matchers](https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment/-/blob/master/README.md?ref_type=heads#exclusion-and-segmentation-matchers) and tracking matchers instead here? added context in https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment/-/issues/88#note_2867410924 </details>