feat(autocomplete): add searchId to state and TileList component for … #209
Conversation
…tracking search context
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
This pull request introduces support for tracking and passing a
searchIdthroughout the autocomplete product suggestion workflow. This enables the frontend to annotate rendered product lists and items with search-related metadata, which can be used for analytics or tracking user interactions with search results.Search ID propagation and analytics instrumentation:
searchIdproperty to the product suggestion output (IProductsOutputinreact/utils/biggy-client.ts) and to the autocomplete state (AutoCompleteStateinreact/components/Autocomplete/index.tsx). This ensures the search identifier is available wherever product suggestions are handled. [1] [2]searchIdfrom product suggestions into its state, and to pass it down to theTileListcomponent. [1] [2] [3] [4]TileListcomponent to accept asearchIdprop and render it as data attributes (data-af-search-id,data-af-onimpression,data-af-onclick, etc.) on product list and item elements. This provides detailed instrumentation for analytics purposes. [1] [2] [3]