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
Jeanne let me know a few producers are creating new drafts on dates when drafts already exist, causing issues with previously targeted faked-in flights. Jeanne highlighted the following use cases:
producer created a new draft on a date when a draft already existed with flights targeted to it.
So, to me, possible solutions lie in a few places, but we should probably look at adding something to alert producers that a draft for "today" already exists and creating a new draft, when one already exists, may cause issues with ads.
Something like that???
The text was updated successfully, but these errors were encountered:
just wanted to surface something that just happened…. Normal Gossip launched today, it was their first ep in Podcasts, so they created a new ep and then deleted the old episode draft, which is all well and fine from a publishing side, except that we had a faked-in campaign targeted towards the old draft, which was deleted/not used to publish. So we missed a bunch of imps, but I think we’ll be ok because Melissa caught it in time. Potential solution… I think that if there a way for whoever is in Podcasts to see that there is something targeted to that ep, that might give them pause before they delete drafts, even though I know that in this case it was a little more complicated
Jeanne let me know a few producers are creating new drafts on dates when drafts already exist, causing issues with previously targeted faked-in flights. Jeanne highlighted the following use cases:
So, to me, possible solutions lie in a few places, but we should probably look at adding something to alert producers that a draft for "today" already exists and creating a new draft, when one already exists, may cause issues with ads.
Something like that???
The text was updated successfully, but these errors were encountered: