Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: High High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: eZ Recommendation
    • Labels:
      None

      Description

      Example : /api/723/clickrecommended/ru20j9shoce2vd0sp0tsltbkd6/1/0219737?scenario=also_clicked

      If a user clicks on a recommended item the following event should be sent to gather statistics over the acceptance of recommended items. Click-recommended events are also known as follow-events. The URL has the following format:
      http://event.yoochoose.net/api/[customerid]/clickrecommended/[userid]/[itemtypeid]/[itemid]?scenario=<scenarioid>
      All embedded parameters are the same like for a click event.
      The scenario parameter identifies the originating scenario to gain detailed statistics about which scenario motivated the user to click a recommendation. This information comes with the recommendation from the recommendation controller. See chapter 2a. Fetching Recommendations (deprecated) for more information.
      This event is used for providing statistics about how often recommendations of the configured recommendation scenario wer accepted or considered as useful by the users. Besides that this information is used for providing and evaluating A/B Tests.

        Activity

        Kamil Musiał (Inactive) created issue -
        Artur Bujnicki (Inactive) made changes -
        Field Original Value New Value
        Description Example : /api/723/clickrecommended/ru20j9shoce2vd0sp0tsltbkd6/1/0219737?scenario=also_clicked

        If a user clicks on a recommended item the following event should be sent to gather statistics over the acceptance of recommended items. Click-recommended events are also known as follow-events. The URL has the following format:
        http://event.yoochoose.net/api/[customerid]/clickrecommended/[userid]/[itemtypeid]/[itemid]?scenario=<scenarioid>
        All embedded parameters are the same like for a click event. The request parameters are:
        Name
        Description
        Values
        scenario (required)
        Name of the scenario, where recommendations originated from.
        URL-encoded alphanumeric
        The scenario parameter identifies the originating scenario to gain detailed statistics about which scenario motivated the user to click a recommendation. This information comes with the recommendation from the recommendation controller. See chapter 2a. Fetching Recommendations (deprecated) for more information.
        This event is used for providing statistics about how often recommendations of the configured recommendation scenario wer accepted or considered as useful by the users. Besides that this information is used for providing and evaluating A/B Tests.
        Artur Bujnicki (Inactive) made changes -
        Description Example : /api/723/clickrecommended/ru20j9shoce2vd0sp0tsltbkd6/1/0219737?scenario=also_clicked

        If a user clicks on a recommended item the following event should be sent to gather statistics over the acceptance of recommended items. Click-recommended events are also known as follow-events. The URL has the following format:
        http://event.yoochoose.net/api/[customerid]/clickrecommended/[userid]/[itemtypeid]/[itemid]?scenario=<scenarioid>
        All embedded parameters are the same like for a click event. The request parameters are:
        Name
        Description
        Values
        scenario (required)
        Name of the scenario, where recommendations originated from.
        URL-encoded alphanumeric
        The scenario parameter identifies the originating scenario to gain detailed statistics about which scenario motivated the user to click a recommendation. This information comes with the recommendation from the recommendation controller. See chapter 2a. Fetching Recommendations (deprecated) for more information.
        This event is used for providing statistics about how often recommendations of the configured recommendation scenario wer accepted or considered as useful by the users. Besides that this information is used for providing and evaluating A/B Tests.
        Example : /api/723/clickrecommended/ru20j9shoce2vd0sp0tsltbkd6/1/0219737?scenario=also_clicked

        If a user clicks on a recommended item the following event should be sent to gather statistics over the acceptance of recommended items. Click-recommended events are also known as follow-events. The URL has the following format:
        http://event.yoochoose.net/api/[customerid]/clickrecommended/[userid]/[itemtypeid]/[itemid]?scenario=<scenarioid>
        All embedded parameters are the same like for a click event.
        The scenario parameter identifies the originating scenario to gain detailed statistics about which scenario motivated the user to click a recommendation. This information comes with the recommendation from the recommendation controller. See chapter 2a. Fetching Recommendations (deprecated) for more information.
        This event is used for providing statistics about how often recommendations of the configured recommendation scenario wer accepted or considered as useful by the users. Besides that this information is used for providing and evaluating A/B Tests.
        Kamil Musiał (Inactive) made changes -
        Status InputQ [ 10001 ] Development [ 3 ]
        Assignee Kamil Musiał [ kamil.musial@ez.no ]
        Kamil Musiał (Inactive) made changes -
        Status Development [ 3 ] Development Review [ 10006 ]
        Hide
        Artur Bujnicki (Inactive) added a comment -

        I just tested it and now event clickrecommended works correctly!

        Show
        Artur Bujnicki (Inactive) added a comment - I just tested it and now event clickrecommended works correctly!
        Kamil Musiał (Inactive) made changes -
        Assignee Kamil Musiał [ kamil.musial@ez.no ]
        Status Development Review [ 10006 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Alex Schuster made changes -
        Workflow EZ* Kanban SubTasks Workflow [ 104419 ] EZEE and EZP Story Workflow [ 129609 ]
        Alex Schuster made changes -
        Workflow EZEE and EZP Story Workflow [ 129609 ] EZ* Kanban SubTasks Workflow [ 130887 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        InputQ InputQ Development Development
        7d 4h 38m 1 kamil.musial@ez.no 06/Jul/17 2:31 PM
        Development Development Development Review Development Review
        4d 20h 44m 1 kamil.musial@ez.no 11/Jul/17 11:16 AM
        Development Review Development Review Closed Closed
        22h 14m 1 kamil.musial@ez.no 12/Jul/17 9:31 AM

          People

          • Assignee:
            Unassigned
            Reporter:
            Kamil Musiał (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: