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

Brave Ads: display 7-day ads history and feedback options for viewed ads #4047

Closed
mandar-brave opened this issue Apr 8, 2019 · 6 comments · Fixed by brave/brave-core#2792

Comments

@mandar-brave
Copy link

Specification details -- images and UX coming shortly.

V1.1 User feedback changes

The Brave Ads panels will be expanded to have a Browser history; this browser history table will also be allowing multi-functional actions back from the user.

In V1.0, the actions are;
Don’t send me this again - Block ad from notifying me again
Dismiss action on Ad will perform the same action
Save - Want to ensure Ad is saved for future viewing
Adds to Bookmark
Flag - Ad is very inappropriate
This will also trigger Action#1
Personalize Ads - add/remove categories i am interested in
Includes LDA check upfront
These categories will be flagged the highest in the taxonomy
Categories opted out will be tagged opted out forever

Mock for Ads Rewards feedback panel
Note: Mock is not complete and needs to be re-rendered

User flow
The user can reach the User feedback setting as part of Brave rewards. The user can see which ads were delivered for the last 30 days with the following detail;
Advertiser detail (main + ad-text)
Category why ad was delivered and allow quick click to opt out for that specific category
Viewed or Clicked or Dismissed
Earned reward per line level item

The above details provide a bookmark view of Ads viewed in the past. The user can decide to choose the dismissed Ads to personalize ad viewing. The user can opt out of Ad categories, including 18 and over.

In the same flow, the user can decide to personalize further and decide not opt out of categories. When the user opts out, they are opted out of those categories permanently. The user can search through categories via drop down or by searching for them. Similarly, a user can decide to opt in to certain categories in the same flow.

Spec: https://docs.google.com/document/d/1XusXB1li8I7Q-3PAk3-2BcdujwZ0Y6oD0yNvhsahZgc/edit#heading=h.l7wtf1v849do

@jsecretan V1.1 prioritization
@NejcZdovc user feedback loop in Brave Rewards
@jenn-rhim to prioritize the visualization of the user feedback loop

@mandar-brave mandar-brave added feature/rewards priority/P2 A bad problem. We might uplift this to the next planned release. feature/ads labels Apr 8, 2019
@mandar-brave
Copy link
Author

@jenn-rhim would love to ship the current design for user feedback loop. If you can post it, i can get the details from the spec to map to the UI. cc @alexwykoff

jasonrsadler pushed a commit to brave/brave-core that referenced this issue May 6, 2019
jasonrsadler pushed a commit to brave/brave-core that referenced this issue May 14, 2019
update brave-ui version
jasonrsadler pushed a commit to brave/brave-core that referenced this issue May 17, 2019
jasonrsadler pushed a commit to brave/brave-core that referenced this issue May 31, 2019
@jsecretan
Copy link

Some things to clarify for @emerick is that

  1. When the upvote/downvote on the ad is selected, it will send an "upvote" or "downvote" type of confirmation associated with the creativeInstanceId of that ad.
  2. The ad delivery logic should then avoid delivering anything with the same creativeSetId (note that this is broader than just creativeInstanceId) as anything that was downvoted.
  3. When and ad is downvoted, it is probably wise to store creativeInstanceId, creativeId, creativeSetId, campaignId and advertiserId just in case the blocking rules change in the future

@jsecretan
Copy link

And after discussion with @tmancey and @emerick, we should also filter out creativesets that are associated with downvoted categories.

@jsecretan
Copy link

jsecretan commented Jun 21, 2019

Flag as inappropriate should send "flag" confirmation type. And when flagged, should follow the same creativesetid blocking as downvote.

emerick pushed a commit to brave/brave-core that referenced this issue Jul 16, 2019
emerick pushed a commit to brave/brave-core that referenced this issue Jul 22, 2019
@jasonrsadler jasonrsadler removed their assignment Jul 29, 2019
emerick pushed a commit to brave/brave-core that referenced this issue Jul 30, 2019
emerick pushed a commit to brave/brave-core that referenced this issue Aug 2, 2019
emerick pushed a commit to brave/brave-core that referenced this issue Aug 5, 2019
emerick pushed a commit to brave/brave-core that referenced this issue Aug 7, 2019
@tmancey tmancey added this to the 0.70.x - Dev milestone Aug 14, 2019
@LaurenWags
Copy link
Member

LaurenWags commented Sep 27, 2019

Verified passed with

Brave 0.69.129 Chromium: 77.0.3865.90 (Official Build) (64-bit)
Revision 58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830}
OS macOS Version 10.13.6 (Build 17G5019)

Screen Shot 2019-09-27 at 6 51 16 PM

Screen Shot 2019-09-27 at 6 51 27 PM

Screen Shot 2019-09-27 at 6 51 57 PM

Verification passed on

Brave 0.69.130 Chromium: 77.0.3865.90 (Official Build) (64-bit)
Revision 58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830}
OS Windows 10 OS Version 1803 (Build 17134.1006)

image

image

image

Verification passed on

Brave 0.69.131 Chromium: 77.0.3865.90 (Official Build) (64-bit)
Revision 58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830}
OS Ubuntu 18.04 LTS

image
image
image

@rebron rebron changed the title Implement user feedback loop Brave Ads: display 7-day ads history and feedback options for viewed ads Oct 2, 2019
@tmancey
Copy link
Contributor

tmancey commented Jan 28, 2020

@jsecretan @emerick Adding the following comment, which we previously discussed to help QA with #7833

Ads viewed count will be reset to zero due to legacy ads history having to be cleared out as we only stored a timestamp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants