Skip to content
Extraits de code Groupes Projets
  1. août 21, 2013
  2. juil. 02, 2013
  3. juin 17, 2013
  4. mai 30, 2013
  5. avr. 23, 2013
    • mattab's avatar
      Refs #2135 · 7933de11
      mattab a rédigé
       * BETA release of Segment editor.
       * API to add/update/delete/get recorded segments
       * cron script will pre-process segments marked as such
       * UI to create, update, apply segments
      
      TODOs @mattab
       - test with NON super user (anon/view/admin)
       - testing (and more testing)-- try to break it (it's not hard...)
       - UI: Saving the segment for reuse / pre-processing
       - Loading message: "This can take a while based on the amount of data that needs to be pre-archived"
       - i18n
       - Save & Apply this segment ==> "Test this segment" which would call VisitsSummary.get for early feedback ?
      
      + hoping for Piotr superJS Ninjas skills with some jquery/js that I can't figure out
      7933de11
  6. avr. 20, 2013
    • mattab's avatar
      Fixes #3904: · 35f975ac
      mattab a rédigé
       * new segment 'siteSearchKeyword'
      Fixes #3903, #3905:
       * adding few fields in the Live API output to accomodate getSuggestedValuesForSegment
       * renamed other fields for consistency with segment names
      Fixes #3906:
       * new API: getSuggestedValuesForSegment which returns top suggested values for a particular segment. It uses the Live.getLastVisitsDetails API to fetch the most recently used values, and will show the most used values first
      
       * Adding tests for everything. The test case actually generates data for all segments so that VisitsSummary.get returns some data for each of the 47 segments being tested returns some data.
        How it works:
        * generate extended data in fixture
        * Tests (1) call getSuggestedValuesForSegment for each segment, check there is some data returned for each segment
        * get the first suggested value from the list,
        * Tests (2) call VisitsSummary.get with this segment value, eg. countryCode==ru.
          * I worked this way for all 47 segments until all tests had some data ==> now we know that all segments have been tested and that the auto suggest works for all segments. TDD FTW!
      35f975ac
  7. nov. 01, 2012
  8. oct. 19, 2012
  9. oct. 15, 2012
    • mattpiwik's avatar
      Refs #2992 Site Search KABOOM, Refs #49 · 53649590
      mattpiwik a rédigé
      Implementing Site Search tracking & reporting in Piwik core!
      
       * New Admin UI to customize, for each site, wheter site search is enabled. Also options to set default values to use.
       * New Reports: Searches, Searches with no result, Search categories, Top Pages Following a Search
       * to track "No result keyword" users will have to tag their site with a JS call, or add a new parameter to the search result page &search_count=X (X being zero for no result searches)
       * Reports works with Row evolution, PDF/HTML reports, Piwik Mobile
       * idaction_url is now NULLable because, Site Search records a page with idaction_name == Keyword, and idaction_url == NULL. This ensures that the Site Searches don't create "Page URL Not defined" records. 
       * updates to Tracker JS API, new function trackSiteSearch, also added in PHP tracker
       * New fields in log_visit to track searches
       * new segment, "searches" which can be used to select visitors who did a search ie. searches>0 or those who searched a lot, ie searches>10
       
       TODO: 
        * commmit integration test, TESTING, DOCS, FAQ, release, and a nice Prayer to the universe and the stars, hoping that I can code a major new feature without any bug...
        * It would be awesome to have compatiblity with Transitions so we can see, for a given site search, what are the starting pages and Destination pages
        
       Thank you for your patience Timo, 
       and thank in advance everyone for your help Testing this new feature!
       
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@7190 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      53649590
  10. oct. 10, 2012
    • benakamoorthi's avatar
      Refs #1823, several changes & tweaks to GeoIP modifications: · 2bd2cea5
      benakamoorthi a rédigé
        * Renamed getVisitsByCity & getVisitsByRegion to getCity & getRegion.
        * Extra testing for anonymized IPs.
        * Show visitor city & region in visitor log & last visits widget.
        * Do specific check for apache module in checking for server based geoip implementation.
        * Fix for continent segment error.
        * Redesigned admin UI to be more compact & to show reason for broken implementations.
        * Don't show duplicate Unknowns in pretty location strings.
        * Don't use REMOTE_ADDR, instead get IP from Piwik_IP.
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@7140 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      2bd2cea5
  11. oct. 07, 2012
    • benakamoorthi's avatar
      Refs #1823, modified UserCountry plugin to allow use of GeoIP databases if... · b2e1f41d
      benakamoorthi a rédigé
      Refs #1823, modified UserCountry plugin to allow use of GeoIP databases if desired. Added two reports, getVisitsByRegion + getVisitsByCity.
      
      Notes:
      
        * Supports country, region, city, org & isp GeoIP databases.
        * Supports GeoIP PHP API, PECL module & server modules.
        * Added ability to regenerate 'general' tracker cache.
        * Removed location_continent column from log_visit & log_conversion tables, and removed visits by continent blob record. Report is now a view over country report.
      
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@7122 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      b2e1f41d
  12. déc. 18, 2011
  13. sept. 11, 2011
  14. sept. 09, 2011
  15. sept. 07, 2011
  16. mai 21, 2011
  17. mai 17, 2011
    • mattpiwik's avatar
      Fixes #2434 Now Actions.get* and Goals.get* (which were the two API not... · 4727edfe
      mattpiwik a rédigé
      Fixes #2434 Now Actions.get* and Goals.get* (which were the two API not supporting all segments) have full support of all segments + adding tests
      
      Refs #2432 
       * Processing Custom vars per page: they are merged in the existing Custom Variables output (rather than create a separate one)
       * So there is no need for a new Report in the UI, Custom variables of scope "page" are displayed in the "Visitors > Custom Variables" report
       * Displaying Custom vars per page in the Live API output
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@4717 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      4727edfe
  18. mai 16, 2011
    • mattpiwik's avatar
      Refs #898 · d8ed9a11
      mattpiwik a rédigé
       * New segment visitType=returningCustomer for visits that are returning, and bought something in a previous visit + integration tests
      Refs #2432 
       * Tracking Custom vars per page + PHP Tracking API + tests
       * TODO: JS API + js tests + Reporting
      Also trying to improve mysqli build..
      
      git-svn-id: http://dev.piwik.org/svn/trunk@4709 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      d8ed9a11
  19. mai 15, 2011
    • mattpiwik's avatar
      Refs #898 Work in progress (but should leave trunk stable and not break anything) · 371af63e
      mattpiwik a rédigé
       * Now tracking Ecommerce Items (sku,name,category,qty,price)
       * zero, 1 or many items can be in a Ecommerce Cart (total), or an Ecommerce order (orderid, grandtotal, subtotal, tax, shipping, discount)
       * A Cart left at the end of a visit becomes an Abandoned cart. New reports separate orders from abandoned carts.
       * JS API and PHP API have 3 new functions (add items, track cart update, track ecommerce order)
       * JS stores timestamp last ecommerce transaction in id cookie so we can count repeat buyers
       * Goals.get API now returns stats for the two goals: ecommerceOrder and ecommerceAbandonedCart
       * new API functions to request Items (product) reports: getItemsSku, getItemsName, getItemsCategory. See doc:
      
        If you are tracking Ecommerce orders and products on your site, the functions "getItemsSku", "getItemsName" and "getItemsCategory"
        will return the list of products purchased on your site, either grouped by Product SKU, Product Name or Product Category. For each name, SKU or category, the following
        metrics are returned: Total revenue, quantity, average price, average quantity, number of orders with this product.
        
        By default, these functions returns the 'Products purchased'. These functions also accept an optional parameter &abandonedCarts=1.
        If the parameter is set, it will instead return the metrics for products that were left in an abandoned cart therefore not purchased. 
        
        The API also lets you request overall Goal metrics via the method "get": Conversions, Visits with at least one conversion, Conversion rate and Revenue.
        If you wish to request specific metrics about Ecommerce goals, you can set the parameter &idGoal=ecommerceAbandonedCart to get metrics about abandoned carts (including Lost revenue, and number of items left in the cart) 
        or &idGoal=ecommerceOrder to get metrics about Ecommerce orders (number of orders, visits with an order, subtotal, tax, shipping, discount, revenue, items ordered)
       * showing ecommerce orders/abandoned carts in the Live! API output
       * new segments: visitEcommerceStatus and daysSinceLastEcommerceOrder
       * these new attributes also appears in Live! API output
       * Fixes #1975 as side effect of cleaning up all this code this bug should now be fixed (bug was to use nb of conversions as dividend, rather than number of converted visits)
       * adding full integration test testing all possible use cases regarding Ecommerce carts/orders/items etc.
       * also integration testing the changes to piwik.js 
      
      git-svn-id: http://dev.piwik.org/svn/trunk@4691 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      371af63e
  20. avr. 15, 2011
  21. avr. 14, 2011
  22. fév. 14, 2011
    • mattpiwik's avatar
      Refs #409 · 087471e0
      mattpiwik a rédigé
       * Adding new metrics: Visit count, Days since first visit, Days since last visit, these are new fields in the table
       * The new Reports will be done in 1.3
       * Reading the timestamps and visit count from the 1st party cookie 
       * Fixing tests that are using the 1st party cookies (added also tests for the 3rd party cookie use case) 
      
      git-svn-id: http://dev.piwik.org/svn/trunk@3892 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      087471e0
  23. fév. 13, 2011
  24. fév. 12, 2011
    • mattpiwik's avatar
      Refs #1736 Sorting segments list to prevent random order test fail · 8e95264a
      mattpiwik a rédigé
      Renaming one segment
      
      git-svn-id: http://dev.piwik.org/svn/trunk@3871 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      8e95264a
    • mattpiwik's avatar
      Refs #1736 · 0e325251
      mattpiwik a rédigé
       * API functions returning data now have a new optional 'segment' parameter. segment can define a Visitor segment dynamically that will be applied to the report. For example, &segment=country==FR;actions>=3 (AND, OR supported. Only == and != supported currently, but easy to add more)
       * For API requests with a segment parameter, the reports will now be processed on the fly, and only the requested plugin report will be archived.
       * All plugins now define the 'segments', with a name, category, SQL field, filter, etc.
       * Simplifying archiving code a bit
       * Fixes #2069 Exit rate computation
       * New widget: lists the Top Keywords for a page URL, Widgets for a website only. Maybe later we could create a widget category "For your site"?
        * This widget is pretty cool SEO wise, but maybe the PHP snippet should do caching (not so good hitting the API on each page view... but why not?)
       * still to do!
      
      git-svn-id: http://dev.piwik.org/svn/trunk@3870 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      0e325251
Chargement en cours