Discussions
Eloqua Profiler Usage Reports
Hello. Hoping to see standard usage reports for Eloqua Profiler included in Insight Reporting. While reports like this exist for the Engage product, Profiler does not have such reports. After large scale deployments of Profiler, it would be beneficial to be able to run a report to see which users are/have been actively using this particular tool. Ideally metrics such as LastLoginDate, AvgDurationOfUse, NumLoginsInXMonths etc. by sales rep would be beneficial. Current process requires an SR be logged in MyOracleSupport.
Thank you.
Comments
-
This is a question some of our stakeholders have asked as well, however i believe the challenge is that if you have profiler embedded in the SFDC lead/contact layouts its loading whether its being used or not.
I would love to see some way of measuring if our users are engaging with the tool.
-
We have 400+ users of Eloqua Sales tools (Profiler + Engage). We just rolled out SSO so everyone is being automatically logged in whenever they load a contact or lead page. Profiler is displayed by default and if you can see it it means you're logged in. Whether or not someone actually interacts with it (clicks around) is a whole different story and would require a rework of every button that can be clicked inside to register as an "interaction". If in your case you have Profiler loading in an iFrame in SalesForce, this should be something you would need to consider when reviewing any such usage reports - unless the "interaction"-based reporting is something that will be considered.
-
Hello,
Wondering if anything new has changed since this previous posting. I just asked this of our product team. We have 800 users, and would like to use this type of usage data to understand who power users are, what features are clicked most, how long people spend using, and if there are certain accounts or type of contacts are being monitored more closely. This would be great if this can be pulled into Analyzer.
-
We have 400+ users of Eloqua Sales tools (Profiler + Engage). We just rolled out SSO so everyone is being automatically logged in whenever they load a contact or lead page. Profiler is displayed by default and if you can see it it means you're logged in. Whether or not someone actually interacts with it (clicks around) is a whole different story and would require a rework of every button that can be clicked inside to register as an "interaction". If in your case you have Profiler loading in an iFrame in SalesForce, this should be something you would need to consider when reviewing any such usage reports - unless the "interaction"-based reporting is something that will be considered.
Hi Alex,
Are users still automatically logged in when they load a contact/lead page? Support continues to tell me that after a security feature implemented earlier this year, that this is no longer the case. The user must hit the "authenticate now" button first before being authenticated (and this is using the saml approach).
Can you confirm if you're getting this experience also?
-
Hello everyone,
Could somebody please help me? I wonder why the "Wait" step is changing randomly the time by itself when I set a campaign. And what should I do to fix this problem?
Thanks,
Christian
-
Hello,
Wondering if anything new has changed since this previous posting. I just asked this of our product team. We have 800 users, and would like to use this type of usage data to understand who power users are, what features are clicked most, how long people spend using, and if there are certain accounts or type of contacts are being monitored more closely. This would be great if this can be pulled into Analyzer.
-
Hi Alex,
Are users still automatically logged in when they load a contact/lead page? Support continues to tell me that after a security feature implemented earlier this year, that this is no longer the case. The user must hit the "authenticate now" button first before being authenticated (and this is using the saml approach).
Can you confirm if you're getting this experience also?
@Devon Guerrero just saw this - we have no issues with the SSO. The security release forced authentication to occur in a pop-up window and cannot any longer be done in an i-Frame. Once a user logs in they stay logged in as that's part of the cookie. They can even close their browser and when they re-open it it'll auto log in based on cookie/session.
-
Hello,
Wondering if anything new has changed since this previous posting. I just asked this of our product team. We have 800 users, and would like to use this type of usage data to understand who power users are, what features are clicked most, how long people spend using, and if there are certain accounts or type of contacts are being monitored more closely. This would be great if this can be pulled into Analyzer.
I wish I had more visibility into who is actually engaging with Profiler. We have been live to all 6k sales users since November 2018. I would like to see how many users are actually using the tools. Tracking usage for us will be tricky as we have embedded profiler within the SFDC lead and contact layouts and it loads via SSO so every time a record is accessed profiler is logged in automatically even though the user may not actually be viewing the Profiler section.
We hope to increase adoption by embedding more widgets from the SFDC lead and contact layouts within the custom profiler panes which we are looking to develop. Things like linkedin sales navigator.
Would love to have a better set of tools for managing and monitoring usage for Sales Tools in general. would be nice to see who is doing what.
Dave
-
@Devon Guerrero just saw this - we have no issues with the SSO. The security release forced authentication to occur in a pop-up window and cannot any longer be done in an i-Frame. Once a user logs in they stay logged in as that's part of the cookie. They can even close their browser and when they re-open it it'll auto log in based on cookie/session.
That's the same experience I'm talking about . Good to confirm that is happening for others as well.
If I remember correctly, in the past you never had to go through that process, and I wanted to know if that was still possible.
-
That's the same experience I'm talking about . Good to confirm that is happening for others as well.
If I remember correctly, in the past you never had to go through that process, and I wanted to know if that was still possible.
I think it was sometime early in summer 2018 when this changed. It was announced with release notes and a side warning. Most people don't read release notes and found out about this the hard way the day after the release when their sales users started filing support tickets. We've had some of this on our side, but it was mostly due to the fact that Eloqua relies way too heavily on browser cache and when a new release comes out and you don't clear your cache a whole lot of issues can arise as documented by @Chris Seepe. We had 500-class errors, we had blank pages, all of which are resolved by clearing cache and sometimes cookies as well.
-
I think it was sometime early in summer 2018 when this changed. It was announced with release notes and a side warning. Most people don't read release notes and found out about this the hard way the day after the release when their sales users started filing support tickets. We've had some of this on our side, but it was mostly due to the fact that Eloqua relies way too heavily on browser cache and when a new release comes out and you don't clear your cache a whole lot of issues can arise as documented by @Chris Seepe. We had 500-class errors, we had blank pages, all of which are resolved by clearing cache and sometimes cookies as well.
I looked back through the release notes for 2018 and couldn't find a mention. Here's 18B which was in the summer, can you point it out?
-
I looked back through the release notes for 2018 and couldn't find a mention. Here's 18B which was in the summer, can you point it out?
Oracle Eloqua Release Resource Center -> Product Notices -> View archived product notices -> "Oracle Eloqua Login Enhancements (Jan 2018)" ->
I LOL at the "enhancement" portion as that's a very relative statement. To a non-technical user this is a roadblock, not an enhancement. From a security standpoint it may be an enhancement. We had so many cases where people either did not know how to work with their browser's pop-up blocker as the login window is a pop-up that's blocked by default in Chrome/Firefox. For others they simply did not click the "authenticate" button because the SSO used to automatically do it for them in the past simply by loading the page. We worked through this, educated some users and etc. Good now, but it was not a smooth transition.
-
Oracle Eloqua Release Resource Center -> Product Notices -> View archived product notices -> "Oracle Eloqua Login Enhancements (Jan 2018)" ->
I LOL at the "enhancement" portion as that's a very relative statement. To a non-technical user this is a roadblock, not an enhancement. From a security standpoint it may be an enhancement. We had so many cases where people either did not know how to work with their browser's pop-up blocker as the login window is a pop-up that's blocked by default in Chrome/Firefox. For others they simply did not click the "authenticate" button because the SSO used to automatically do it for them in the past simply by loading the page. We worked through this, educated some users and etc. Good now, but it was not a smooth transition.
Yeah they made a long post about it, but could not bother to add a line in the official release notes, nor mention in the title that it will primarily affect Engage user experience.
-
We would like to see the SAML login abiltiy be added to Eloqua Insights BI reports. Insight Agents are able to send the link to a report to our Eloqua users and the UX expected is they user clicks the link on their corporate computer and the SAML process runs and redirects them to see the report.
Today this doesn't happen and a error message is shown. The user has two workarounds
- access Profiler if they have a licence, then access the report
- login to Eloqua, access insights then acess the report
This is a poor experience and limits a key benefit of using the agent to send the email for our simple business workflow.
Has anybody any news on when this SAML authentication could be made possible?
Niall