Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser based segmentation using "Contains" does not work as expected. #17375

Open
Starker3 opened this issue Mar 22, 2021 · 1 comment
Open
Labels
Bug For errors / faults / flaws / inconsistencies etc.

Comments

@Starker3
Copy link
Contributor

Expected Behavior

When using a segment for example: Browser Contains Chrome we would expect that the segment would contain all browsers that contain Chrome, likewise for Browser Contains Safari etc.

Current Behavior

Unfortunately at present it appears as though using Browser Contains Chrome the reports only show data for Chrome and Google Search App (see screenshots)
image
image

Screenshot of "All Visits" segment:
image

In order to see reports for all the Chrome/Safari based browsers at present we would need to specify the browser names, eg. Chrome, Chrome Mobile, Chrome Mobile iOS, Safari etc.

Possible Solution

Steps to Reproduce (for Bugs)

  1. View the Software report, noting all the Browsers using Chrome in the name.
  2. Then view the Software report using the following Segment: &segment=browserName%3D@Chrome (Browser Contains Chrome)

Your Environment

  • Matomo Version: 4.2.1
  • PHP Version: 7.3.22
  • Server Operating System: Debian 10
  • Additionally installed plugins:
    Plugins Activated: API, AbTesting 4.1.0, Actions, ActivityLog 4.0.2, Annotations, BulkTracking, Cohorts 4.0.3, Contents, CoreAdminHome, CoreConsole, CoreHome, CorePluginsAdmin, CoreUpdater, CoreVisualizations, CustomAlerts 4.0.1, CustomDimensions, CustomJsTracker, CustomReports 4.0.5, Dashboard, DevicePlugins, DevicesDetection, Diagnostics, Ecommerce, Events, Feedback, FormAnalytics 4.0.4, Funnels 4.0.4, GeoIp2, Goals, GoogleAnalyticsImporter 4.1.1, Heartbeat, HeatmapSessionRecording 4.0.10, ImageGraph, Insights, Installation, Intl, IntranetMeasurable, LanguagesManager, Live, LoginLdap 4.3.0, LoginSaml 4.0.3, MarketingCampaignsReporting 4.0.4, Marketplace, MediaAnalytics 4.0.5, MobileMessaging, Monolog, Morpheus, MultiChannelConversionAttribution 4.0.5, MultiSites, Overlay, PagePerformance, PrivacyManager, Proxy, Referrers, Resolution, RollUpReporting 4.0.2, RssWidget, SEO, ScheduledReports, SearchEngineKeywordsPerformance 4.2.0, SegmentEditor, SitesManager, TagManager, Tour, Transitions, TwoFactorAuth, UserCountry, UserCountryMap, UserId, UserLanguage, UsersFlow 4.0.3, UsersManager, VisitFrequency, VisitTime, VisitorGenerator 4.0.3, VisitorInterest, VisitsSummary, WebsiteMeasurable, WhiteLabel 4.0.2, Widgetize, WooCommerceAnalytics 4.0.5
@Starker3 Starker3 added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label Mar 22, 2021
@diosmosis diosmosis added Bug For errors / faults / flaws / inconsistencies etc. and removed Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. labels Mar 22, 2021
@sgiehl
Copy link
Member

sgiehl commented Mar 23, 2021

This actually can't work currently due to the structure we are storing browser information in the database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

4 participants