Forum Discussion

fleonyleon's avatar
fleonyleon
Guide
6 years ago

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 LS...
  • DougS's avatar
    DougS
    6 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

  • DougS's avatar
    DougS
    6 years ago

    That looks correct. I would advise you file a support case at this point if you are not seeing the search terms showing up in LSI.

DougS's avatar
DougS
Khoros Oracle

That looks correct. I would advise you file a support case at this point if you are not seeing the search terms showing up in LSI.

fleonyleon's avatar
fleonyleon
Guide
6 years ago

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