Skip to content
This repository has been archived by the owner on Aug 13, 2020. It is now read-only.

Grouping of properties for a site #812

Open
JasonBarnabe opened this issue Nov 15, 2019 · 5 comments
Open

Grouping of properties for a site #812

JasonBarnabe opened this issue Nov 15, 2019 · 5 comments
Labels
architecture Requires architure feature request Request for a feature that does not currently exist public-facing Visible to users
Milestone

Comments

@JasonBarnabe
Copy link
Contributor

I have set up multiple properties for a single site I run. Each time I am asked the same questions about the site. Each time I need to ask for the property to be set to active. I think it would be useful to have a "site" model so that this stuff could be set up once for all placements on a site, and possibly for reporting purposes for people who have multiple sites.

I also get the impression that advertisers see things on a per-property basis, and they may be ignoring my other properties that from their perspective should be equivalent.

@JasonBarnabe JasonBarnabe added the feature request Request for a feature that does not currently exist label Nov 15, 2019
@andrewmcodes
Copy link
Contributor

Great feedback @JasonBarnabe. I believe this is already on our list but I’ll bump it up in terms of importance. Hoping the redesign will solve some of these issues as well.

It seems to me that these should really be one property that we then break up into sub-sections. Is the reason you need multiple properties due to the url? If not could you drop a sentence or two as to why you need multiple properties for the same root domain just so I can get a better idea of the underlying problem that we need to solve?

Thank you!!

@andrewmcodes andrewmcodes added the architecture Requires architure label Nov 15, 2019
@JasonBarnabe
Copy link
Contributor Author

I use multiple properties because:

  1. Some properties have different display settings in CodeFund.
  2. I want the stats reported separately for different kinds of pages, because they display in different spots and may individually be in competition with other ad networks.

@andrewmcodes
Copy link
Contributor

Perfect. Thank you @JasonBarnabe. I’ll talk to the team and update you with our plan!

@andrewmcodes andrewmcodes added the public-facing Visible to users label Dec 3, 2019
@andrewmcodes andrewmcodes added this to the Multiple Ad Placement milestone Dec 3, 2019
@coderberry
Copy link
Contributor

Hi @JasonBarnabe, we are careful to how many placements we have per site. I believe you are the only using separate properties for the same website. The real issue we have here I believe is that we are not automatically notified of when a new property is added.

Each time we get a new property request, we have to ensure that the placement is correct and that it doesn't look bad. Unfortunately this is a human-driven process. That being said, I imagine there are ways we can automate it to a point with vetted out publishers such as yourself.

@coderberry
Copy link
Contributor

Scheduled for Q2 (marketplace)

@andrewmcodes andrewmcodes removed their assignment Feb 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
architecture Requires architure feature request Request for a feature that does not currently exist public-facing Visible to users
Projects
None yet
Development

No branches or pull requests

3 participants