User Profile

fleonyleon

Guide

Joined 10 years ago

22 Posts

View All Badges

User Widgets

Contributions

Re: Custom Search Component not being captured by Analytics
Doug hi, Hope you are doing fine. Khoros updated our community's software so that the API calls for search start working again. They have tested with a direct API call and the search results do show now on LSI, but the search results from our component, as described and validated by you above, are still not being captured by LSI. We changed the component on stage so that the command shows up as a COMMENT and this is what we got: Can you please help us validating that the command is being sent correctly, including the search=true part for data capture by LSI? Thanks! Federico
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Re: Custom Search Component not being captured by Analytics
Thanks! I will do so.
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Re: Custom Search Component not being captured by Analytics
Hello, We tried today again and we still can't see the search results in Analytics. This is how we changed the code according to your last recommendation, I hope our development team did them correctly. Please validate we understood correctly the changes that needed to be made and any other suggestions you may have. Thanks! Federico
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Re: Custom Search Component not being captured by Analytics
Thanks for your recommendation! We made the changes yesterday and we are not getting the error anymore... we pushed the changes into production. Problem is that we still don’t see the search count results in Analytics. Should it show today or do we need to wait until Monday? Regards, Federico
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Re: Custom Search Component not being captured by Analytics
We validated we are using LiQL query with matches but from your link we realized we were not including the search=true parameter correctly. We changed it following the example from the link but we are now getting an error message, so we are still not doing it correctly. Can you guide as to documentation where we can review how we should use the search=true parameter in our code? Thanks, Federico
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Re: Custom Search Component not being captured by Analytics
Thanks for your comments! We will validate with our development team.
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
Custom Search Component not being captured by Analytics
We have created a custom search component for similar reasons: better design, and it is working perfectly. The problem we now have is that the searches are not being captured by Analytics, so the LSI report on number of searches shows zero. One of the objectives of the custom component was to make it more user friendly and increase searches and now we don't have a way to measure it. We were told by Support to include the following query parameter to API call for them to be captured by Analytics: api.for_ui_search=true Problem is the change was done yesterday and we still don't see the results of quantity of searches in Analytics. Any advise you can give us? There is no documentation on this parameter that we can use as a reference so we might be using it incorrectly...or maybe we just need to wait for Analytics a while longer?
Solved
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments
DougS
Khoros Alumni (Retired)
7 years ago
Are you using a LiQL query with a MATCHES clause or REST V1 search calls to do your custom search? I believe the api.for_ui_search=true parameter only works for LiQL queries (not for the REST V1 search endpoints). If you are using a LiQL query with a MATCHES clause and you don't start seeing search terms start to show up (from the date you added it forward), I would recommend filing a support case b/c it should start working.

-Doug
Sign in to react to this post
Re: Custom Search Component, do I need one?
Hello Varun, We have created a custom search component for similar reasons: better design, and it is working perfectly. The problem we now have is that the searches are not being captured by Analytics, so the LSI report on number of searches shows zero. One of the objectives of the custom component was to make it more user friendly and increase searches and now we don't have a way to measure it. We were told by Support to include the following query parameter to API call for them to be captured by Analytics: api.for_ui_search=true Problem is the change was done yesterday and we still don't see the results of quantity of searches in Analytics. Any advise you can give us? There is no documentation on this parameter that we can use as a reference so we might be using it incorrectly...or maybe we just need to wait for Analytics a while longer? Regards, Fico
7 years ago Place Developer Discussion
Views
Sign in to react to this post
Comments

You’ve seen all recent content