Hi Cooper -
If you've got access to the Funnelback Admin UI, you could examine the click and query log files directly for a given collection:
Administer > Browse Log Files > Archived Log Files
clicks-SERVER-SHORTNAME.DATESTAMP_TIMESTAMP.log.gz
query-SERVER-SHORTNAME.DATESTAMP_TIMESTAMP.log.gz
Try accessing the Funnelback Public UI directly for the funnelback_documentation collection (without Matrix involved), perform some queries and clicks, and examine the corresponding output in these log files.
It's also possible that:
- you're using a template that doesn't refer to the click tracking URLs in the response data model (transaction.response.resultPacket.results.clickTrackingUrl), or
- the click tracking URL prefix has been incorrectly configured, or
- there has been some additional reporting blacklisting configured.
If you're wrapping the Funnelback response in a Matrix page requested on a user's behalf, you will also want to ensure you're passing through the remote user's IP address for accurate logging.
See also:
https://docs.funnelback.com/14.2/ui_modern_click_link_collection_cfg.html
https://docs.funnelback.com/14.2/reporting_blacklist_cfg.html
https://docs.funnelback.com/14.2/logging_ignored_x_forwarded_for_ranges_collection_cfg.html
Once you're logging queries and clicks correctly, you could try triggering analytics regeneration from the Admin UI (Analyse > Update Analytics Now).