feat: PoC - V3 space-scoped Experience API paths for CF-Entities#383
Draft
khaalid subaan (Khaalidsub) wants to merge 1 commit into
Draft
feat: PoC - V3 space-scoped Experience API paths for CF-Entities#383khaalid subaan (Khaalidsub) wants to merge 1 commit into
khaalid subaan (Khaalidsub) wants to merge 1 commit into
Conversation
Patches the ExperienceApiClient to use V3 space-scoped paths:
v3/spaces/{spaceId}/environments/{environment}/profiles
Adds a minimal React PoC app (implementations/cf-entities-poc/) that:
- Initializes the Optimization SDK with spaceId as clientId
- Points to the dev Experience API (experience.ninetailed.engineering)
- Sends identify/page events to trigger audience evaluation
- Displays the raw API response showing experience resolution
The V3 path reads config from SPACE_ENV_CONFIGS_KV[spaceId:envId]
which is populated by the config pusher in ninetailed-new.
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
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.
Summary
Proof of concept demonstrating the Optimization SDK calling the Experience API via V3 space-scoped paths instead of V2 organization-scoped paths. This enables the SDK to consume audiences and experiences stored as CF-Entities rather than legacy content type entries.
Changes
SDK Patch (
packages/universal/api-client/)Replaces V2 URL construction with V3:
For the PoC,
clientIdis repurposed asspaceIdfor V3 routing.New Implementation (
implementations/cf-entities-poc/)Minimal React app that:
clientId = spaceId(iyqlttzomqet)https://experience.ninetailed.engineering/)identifyandpageeventsHow to test
Click "Identify (Segment User traits)" to send an identify event with traits that match the "Segment User" audience. The Experience API will:
iyqlttzomqet:main) - populated by the config pusher in ninetailed-new PR #7111Companion PRs
contentful/cf-entities#feat/p13n-audiences-experiencesninetailed-new#7111Architecture