Gravatar for mahesh_patil2@cable.comcast.com

Question by helpme, Jul 28, 2016 9:58 AM

Coveo Analytics

Hi,

We are planning to enable Coveo Analytics We took below approach.

We are using Coveo for Sitecore.

On our search page Search Layout we "Enable Analytics" & Set the API token we received from Coveo.

Everything works fine. Our Concern is with this approach API Token is visible in Plain Text in Browser.

I was trying to figure out more secure approach looked at below documentation

https://onlinehelp.coveo.com/en/cloud/settingupcloudusageanalyticsloggingbythejavascriptsearchwithanon-premises_index.htm

but with this approach i configure everything correctly still dont see any data in Cloud Analytics?

ON CES server in API log i do get some kind of a log for 405

Can someone help out with this?

Thanks, Mahesh

1 Reply
Gravatar for sbelzile@coveo.com

Answer by Sébastien Belzile, Jul 28, 2016 10:27 AM

First: which version of C4SC are you using?

If you use C4SC 4.0 or one of the latest version of C4SC 3.0 (since June (maybe you should not trust my memory)), analytics tokens are handled by the Coveo search proxy (it is optional in 3.0): https://developers.coveo.com/display/public/SitecoreV3/Configuring+Coveo+Usage+Analytics

Before going further: Are you using one of these versions? Is it possible for you to upgrade?

Gravatar for mahesh_patil2@cable.comcast.com

Comment by helpme, Jul 28, 2016 11:16 AM

Thanks for your prompt reply.

We are on C4SC - 3.0.1026.0 . This is precisely how i configure it & having concerns on token being placed as a plain text?

Any thoughts or suggestions?

Thanks, Mahesh

Gravatar for sbelzile@coveo.com

Comment by Sébastien Belzile, Jul 28, 2016 11:43 AM

"This is precisely how i configure it & having concerns on token being placed as a plain text?": I meant: have a look at the bottom of the page, section "Using a Different Data Token per Site" -> There is a way to place your token in the Sitecore configuration so that the token is added by the C4SC proxy and not rendered as plain text on the page.

Unfortunately you are using an old version that does not allow doing this. That is why I asked if it is possible for you to upgrade to June 2016.

I will help you with the 405 error then. Could you share your config.yml? (you can censure sensible informations of course).

Ask a question