如何从会话中获取分析和生成可视化报告？

Question

我正在寻找一种从用户会话日志中获取数据的技术或方法，并将其转换为某种可视样式(条形图/图表/其他)。

我们特别希望用户会话"arcs“(login->news->something->logout)能够更容易地分析人们使用站点的方式。

这意味着我们的服务是一个可用性分析器，我们可以从统计数据中看出并看到用户体验到的UX/UI问题。

Google和Piwik很酷，有一些相同的功能，但我们希望更进一步……

对如何开始有什么想法吗？另外，如果我错过了一种显而易见的方法，请随时指出！

Answer 1

福雷纳模块可用于此类类型的报告。它附带了各种样本报告和解决方案，例如站点管理报告，其中包含有关实际Drupal站点的数据。

以下是关于这些报告的一些细节：

• 活动用户- D7's管理员/人员的变体，包括用户报告日志的超链接。
• Active Users -向drupal站点的所有活动用户发送电子邮件的演示。
• 用户日志-最近的用户监视日志条目(指定为报表参数)。
• 角色详细信息-一个表，显示Drupal角色的所有用户(指定为报表参数)，以及授予他们的Drupal权限，并为每个用户提供查看或编辑用户配置文件的超链接。

将这些样本报告克隆到自定义变体中是直接的。例如，用一些报表参数调优活动用户报告，使其仅报告本周注册的用户。或者就像我不久前在这份报告中所做的那样(还有向下钻链接，也就是其中红色的数字)：

有关上述屏幕截图的详细信息，请参阅我在forena发布队列中的评论。

甚至还有AbitMORE:该模块还支持绘制这些数据的图表(典型的相关需求.)。

披露:我是这个模块的共同维护者，

我希望这不会违反网站的自我推销政策。

Answer 2

模块google分析报告激活图表做的工作

编辑：

我不知道我是否确切地回答了你的需求，但谷歌分析报告模块创建了一个默认视图来显示来自GA数据的摘要图表和数据选项卡。可以通过添加GA:session变量来修改和扩展这些drupal附加视图，例如

Adsense metrics: AdSense Exits
The number of sessions that ended due to a user clicking on an AdSense ad.
API name: ga:adsenseExits.
Ecommerce calculated metrics: Ecommerce Conversion Rate
The average number of transactions for a session on your property.
Calculation: ga:transactions / ga:sessions.
API name: ga:transactionsPerSession.
Ecommerce dimensions: Sessions to Transaction
The number of sessions between users' purchases and the related campaigns that lead to the purchases.
API name: ga:sessionsToTransaction.
Event tracking calculated metrics: Events / Session with Event
The average number of events per session with event.
Calculation: ga:totalEvents / ga:sessionsWithEvent.
API name: ga:eventsPerSessionWithEvent.
Event tracking metrics: Sessions with Event
The total number of sessions with events.
API name: ga:sessionsWithEvent.
Goal conversions calculated metrics: Goal Conversion Rate
The percentage of sessions which resulted in a conversion to at least one of your goals.
Calculation: ga:goalCompletionsAll / ga:sessions.
API name: ga:goalConversionRateAll.
Goal conversions calculated metrics: Goal XX Conversion Rate
The percentage of sessions which resulted in a conversion to the requested goal number.
Calculation: ga:goalXXCompletions / ga:sessions.
API name: ga:goalXXConversionRate.
Goal conversions calculated metrics: Per Session Goal Value
The average goal value of a session on your property.
Calculation: ga:goalValueAll / ga:sessions.
API name: ga:goalValuePerSession.
Internal search calculated metrics: % Sessions with Search
The percentage of sessions with search.
Calculation: ga:searchSessions / ga:sessions.
API name: ga:percentSessionsWithSearch.
Internal search calculated metrics: Site Search Goal Conversion Rate
The percentage of search sessions (i.e., sessions that included at least one search) which resulted in a conversion to at least one of your goals.
Calculation: ga:goalCompletionsAll / ga:searchUniques.
API name: ga:searchGoalConversionRateAll.
Internal search calculated metrics: Site Search Goal XX Conversion Rate
The percentage of search sessions (i.e., sessions that included at least one search) which resulted in a conversion to the requested goal number.
Calculation: ga:goalXXCompletions / ga:searchUniques.
API name: ga:searchGoalXXConversionRate.
Internal search metrics: Sessions with Search
The total number of sessions that included an internal search
API name: ga:searchSessions.
Page tracking calculated metrics: Pages / Session
The average number of pages viewed during a session on your property. Repeated views of a single page are counted.
Calculation: ga:pageviews / ga:sessions.
API name: ga:pageviewsPerSession.
Page tracking dimensions: Page Depth
The number of pages visited by users during a session. The value is a histogram that counts pageviews across a range of possible values. In this calculation, all sessions will have at least one pageview, and some percentage of sessions will have more.
API name: ga:pageDepth.
Session calculated metrics: Avg. Session Duration
The average duration of user sessions represented in total seconds.
Calculation: ga:sessionDuration / ga:sessions.
API name: ga:avgSessionDuration.
Session calculated metrics: Bounce Rate
The percentage of single-page session (i.e., session in which the person left your property from the first page).
Calculation: ga:bounces / ga:sessions.
API name: ga:bounceRate.
Session metrics: Bounces
The total number of single page (or single engagement hit) sessions for your property.
API name: ga:bounces.
Session metrics: Session Duration
The total duration of user sessions represented in total seconds.
API name: ga:sessionDuration.
Session metrics: Sessions
Counts the total number of sessions.
API name: ga:sessions.
Social interactions metrics: Unique Social Actions
The number of sessions during which the specified social action(s) occurred at least once. This is based on the the unique combination of socialInteractionNetwork, socialInteractionAction, and socialInteractionTarget.
API name: ga:uniqueSocialInteractions.
Time dimensions: Hour
A two-digit hour of the day ranging from 00-23 in the timezone configured for the account. This value is also corrected for daylight savings time, adhering to all local rules for daylight savings time. If your timezone follows daylight savings time, there will be an apparent bump in the number of sessions during the change-over hour (e.g. between 1:00 and 2:00) for the day per year when that hour repeats. A corresponding hour with zero sessions will occur at the opposite changeover. (Google Analytics does not track user time more precisely than hours.)
API name: ga:hour.
Traffic sources dimensions: Social Source Referral
Indicates sessions that arrived to the property from a social source. The possible values are Yes or No where the first letter is capitalized.
API name: ga:hasSocialSourceReferral.
User calculated metrics: % New Sessions
The percentage of sessions by people who had never visited your property before.
Calculation: ga:newUsers / ga:sessions.
API name: ga:percentNewSessions.
User dimensions: Count of Sessions
The session index for a user to your property. Each session from a unique user will get its own incremental index starting from 1 for the first session. Subsequent sessions do not change previous session indicies. For example, if a certain user has 4 sessions to your website, sessionCount for that user will have 4 distinct values of 1 through 4.
API name: ga:sessionCount.