Sophia Kianni @[Engineer #2] you can just swipe it to the right and then it collapses and you can do it on the should I buy this state too and we should drop
a cookie •
Engineer #2 okay, I can add that. but again, isnt that against compliance? some concerns raised by wildfire in past related to placing cookies on
dismiss events: The remaining issue is the background activation that occurs when a user clicks the "X" on the extension (see screen recording below). This could be flagged by Google as "dropping a cookie without the user's
knowledge." Google's updated Chrome Extension policy requires that affiliate links/cookies only fire after a clear user action. They specifically prohibit injecting affiliate links in the background without related user action. At checkout, I saw a Crocs affiliate link fire automatically in the background, which is what caused my Acorns extension to prompt me to reactivate. This behavior could put your extension at risk of removal
from the Chrome Web Store.
Sophia Kianni Well so we don't do it when they click "X" I guess we could say that the
user is trying to open us and roll it back if they complain
Engineer #2 lol okay, btw its not that helpful. we still have passive trigger dropping cookies every 2 hrs and its working pretty good. as long as user has clicked on phia once for a top 1000 website, we will continue to drop
cookies every 2 hrs. so, this additional drop wont matter much
Sophia Kianni That makes sense yeah I just whatever we can do to keep these cookies dropping will be amazing thank you
Sophia Kianni @[Engineer #2] you can just swipe it to the right and then it collapses and you can do it on the should I buy this state too and we should drop a cookie •
Engineer #2 okay, I can add that. but again, isnt that against compliance? some concerns raised by wildfire in past related to placing cookies on dismiss events: The remaining issue is the background activation that occurs when a user clicks the "X" on the extension (see screen recording below). This could be flagged by Google as "dropping a cookie without the user's knowledge." Google's updated Chrome Extension policy requires that affiliate links/cookies only fire after a clear user action. They specifically prohibit injecting affiliate links in the background without related user action. At checkout, I saw a Crocs affiliate link fire automatically in the background, which is what caused my Acorns extension to prompt me to reactivate. This behavior could put your extension at risk of removal from the Chrome Web Store.
Sophia Kianni Well so we don't do it when they click "X" I guess we could say that the user is trying to open us and roll it back if they complain
Engineer #2 lol okay, btw its not that helpful. we still have passive trigger dropping cookies every 2 hrs and its working pretty good. as long as user has clicked on phia once for a top 1000 website, we will continue to drop cookies every 2 hrs. so, this additional drop wont matter much
Sophia Kianni That makes sense yeah I just whatever we can do to keep these cookies dropping will be amazing thank you
Shady