Skip to content
Extraits de code Groupes Projets
  1. nov. 27, 2014
  2. juin 17, 2014
  3. juin 10, 2014
  4. fév. 02, 2014
  5. nov. 11, 2013
  6. nov. 06, 2013
  7. oct. 20, 2013
  8. oct. 10, 2013
  9. oct. 09, 2013
  10. oct. 08, 2013
  11. sept. 03, 2013
  12. août 02, 2013
  13. juil. 31, 2013
  14. juil. 21, 2013
  15. juil. 20, 2013
  16. juil. 02, 2013
  17. juin 18, 2013
  18. juin 07, 2013
  19. juin 06, 2013
  20. juin 05, 2013
  21. mars 27, 2013
  22. fév. 05, 2013
  23. déc. 10, 2012
  24. 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
  25. fév. 08, 2012
  26. nov. 18, 2011
  27. sept. 27, 2011
    • mattpiwik's avatar
      Fixes #2667 · c91c513e
      mattpiwik a rédigé
       * Stop aggregating visits for Custom variables of scope "page"
        * still OK for scope "visit" since there is supposed to be one custom var value per custom variable name for a given visit
       * Now we always display the Actions columns so that these rows with no visit still show the number of Actions
       * cleaned up from custom var output report, removed some "price_viewed" column left out
      
      UI Change (future FAQ maybe...)
       * When there is a "Visits" column for the Custom Variable report with a value of "-" (hyphen) then it means this custom variable was used with scope=page. 
      
      Fixes #2662
       * Added integration tests testing getPageUrl with multiple periods and websites 
       * fixed a bug when idSite=all or 1,2,3
      
      git-svn-id: http://dev.piwik.org/svn/trunk@5235 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      c91c513e
  28. sept. 22, 2011
    • mattpiwik's avatar
      Fixes #2676 · 169f211c
      mattpiwik a rédigé
       * Now tracking custom variables with empty value in setEcommerceView
       * Now aggregating custom variables with empty value under a label "Value not defined" (in english always)
       * Updated tests and refactored code in API instead of archiving
      
      git-svn-id: http://dev.piwik.org/svn/trunk@5203 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      169f211c
  29. sept. 19, 2011
    • mattpiwik's avatar
      Fixes #2660 · 635f0569
      mattpiwik a rédigé
       * Adding price tracking on Ecommerce pages, via JS or PHP api. 
       * Displaying price in API field avg_price ONLY IF the product was NOT purchased. If a product was purchased, the "display price" tracked is not displayed and purchased price is used instead.
       * Price tracked with this feature will ONLY be displayed as "Avg_price" in Product Names, and Product SKUs ONLY WHEN the products havent been bought.
       * Hacking around tracking price for ecommerce items, using a custom variable and small custom hacks to the SQL to get the average price for each custom var.
       Similar to doing basic version of custom variables co variation
       * Allow custom variables values to be integer (previously would fail to record the custom variable)
      
      TODO: Update Doc
      
      git-svn-id: http://dev.piwik.org/svn/trunk@5191 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      635f0569
  30. mai 19, 2011
    • mattpiwik's avatar
      Refs #898 · 3aca2890
      mattpiwik a rédigé
       * Adding Product page/Category page view tracking via Tracking function: setEcommerceView: function(sku, name, category)
      This is using the Custom Variables per page, using slot 3/4/5 to track sku/name/category
       * UPdated PHP tracker + JS tracker + adding tests
       * Items reports (best SKU/Name/Category) will automatically call the Custom Vars API and enrich the items reports with "Visits", "Conversion rate"
       * Updating integration tests + fixing bug when item is deleted from Cart, then added again (or purchased)
      
      
      git-svn-id: http://dev.piwik.org/svn/trunk@4723 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      3aca2890
  31. avr. 14, 2011
  32. mars 23, 2011
  33. fév. 13, 2011
    • mattpiwik's avatar
      Refs #1984 · e20919c1
      mattpiwik a rédigé
       * removing setCustomData feature
       * updated JS doc piwik.org
       * deprecated setCustomData getCustomData and the customData parameter to few functions. Now plugin developers can use the Custom Variables array 
      
      git-svn-id: http://dev.piwik.org/svn/trunk@3882 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      e20919c1
  34. fév. 12, 2011
    • 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
  35. jan. 19, 2011
    • mattpiwik's avatar
      Refs #1984 - New plugins CustomVariables · 1afa1066
      mattpiwik a rédigé
       * Now possible to track up to 5 Custom variables per Visit. Also, Goal conversions will be reported 'By custom variable name & value' 
       * New report in Visitors > Custom Variables, new CustomVars API
       * Updated schema
       * Updated PiwikTracker PHP api to allow setting the name,value pairs
      
      Code style
       * Refatoring some API code, and Archiving queries 
       * Changing text from 'segment' to 'dimension' as this is better description + we want to build actual segmentation later
       * removing getJs calls in some plugins since they only included sparkline.js, moved to CoreHome
      
      git-svn-id: http://dev.piwik.org/svn/trunk@3780 59fd770c-687e-43c8-a1e3-f5a4ff64c105
      1afa1066
Chargement en cours