Composr offers three main systems for providing online support:
1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support.
2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities.
3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content.
How can I access the raw data behind the statistics graphs?
Answer
Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools.
All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.
What are the limitations of pre-computed statistics in Composr?
Answer
Pre-computed statistics introduce certain limitations:
Filtering constraints: Limits filtering options to those incorporated in the data structure.
Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.
KPIs (Key Performance Indicators) are specific measurements selected for marketing analysis. In Composr, time-series graphs can be added as KPIs. They offer several benefits:
Quick reference: Available on the Admin Zone dashboard staff checklist.
Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries.
Notifications: Staff members receive regular notifications regarding target achievement status.
Tracking codes help you identify the sources driving user sessions to your website or associate specific split testing variations with users. Composr offers integrated referral tracking through various means:
URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon.
Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page.
Member joining: When a referred member joins, the referring member receives points and a friend request.
Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system.
Stats addon: Generates graphs of tracking codes, including conversion rate measurements.
User lookup tool: Allows checking if a user accessed the site via a tracking code.
Tempcode integration: Inject tracking codes into Tempcode using symbols like {$SET_TRACKING_CODE,some code} or {$SPLIT_TEST,some code,some other code}.
What are the different ways to track events in Composr?
Answer
Composr offers various methods for tracking events:
Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc.
Tempcode symbol: Use the {$LOG_STATS_EVENT,event} symbol within your templates to track events when the template is displayed.
JavaScript function: Employ the $cms.statsEventTrack JavaScript function to track events from within your JavaScript code.
HTML data attribute: Add data-click-stats-event-track="{ category: 'some event', nativeTracking: true }" to HTML elements. This method acts as a wrapper for the JavaScript function.
URL wrapping: Wrap URLs in links using the {$STATS_TRACK_URL,URL,event} symbol. This approach records events via a redirection script and doesn't rely on JavaScript.
The JavaScript and HTML data attribute methods can also be integrated with Google Analytics events.
Why are my searches slow, and how can I improve search speed?
Answer
Slow searches can occur when dealing with large amounts of content. Here are some workarounds and solutions:
MySQL timeout setting: For MySQL 5.7+, set a query timeout to prevent searches from locking up your database. Composr automatically sets this, but you can configure it manually if needed.
Use InnoDB tables: Switching to InnoDB tables in MySQL can prevent slow queries from affecting other users on your website. Note that InnoDB is not officially supported by Composr yet.
Enable the fast custom index: As mentioned earlier, the fast custom index is optimized for handling large datasets and filtered searches, potentially leading to significant speed improvements.
