You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this feature related to a problem? Please describe.
As a billboard manager, I want to be able to target billboards to a specific device type (desktop or mobile) or both device classes so I can be more specific with my targeting.
Describe the solution you’d like
Each billboard should be able to be targetted to:
Desktop,
Mobile, or
Any (desktop or mobile).
Definition of Done
Add the ability to add device type targeting criteria to billboards - from the three options specified above
Update the billboard API to allow specific the device type option
Update the billboard display code/query to incorporate the user's device type in the subset of billboards that can be displayed
The text was updated successfully, but these errors were encountered:
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.
To our amazing contributors: issues labeled bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.
If this is a feature request from an external contributor (not core team at Forem), please close the issue and re-post via GitHub Discussions.
To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up.
For full info on how to contribute, please check out our contributors guide.
Is this feature related to a problem? Please describe.
As a billboard manager, I want to be able to target billboards to a specific device type (desktop or mobile) or both device classes so I can be more specific with my targeting.
Describe the solution you’d like
Definition of Done
The text was updated successfully, but these errors were encountered: