New changes from Firefox costing your commissions?

New changes from Firefox costing you your commissions?

The speed at which browser vendors are pushing privacy first initiatives to the center stage is picking up rapidly.
By now you know about how Apple’s ITP is already blocking affiliate cookies on Safari (desktop and mobile).

Yesterday, Firefox started blocking tracking & 3rd party cookies by default.
Right now, this is happening on new installs and users.
But before the end of the year, all Firefox users (current and new) will have tracking cookies automatically blocked by default.
So what’s the big deal?
When affiliate tracking cookies get deleted or blocked, you don’t get paid for the sales and leads you generated.
The messed up part for you is that, the merchant you drove the sale to still makes money, but they don’t have to pay you commissions because there’s no affiliate cookie attached.
Once again, to protect your revenue, I highly recommend you contact your networks and ask them to confirm what solutions they have in place to address this issue.
TIP: Don’t settle for your network rep saying they are using S2S (server to server) or postback tracking so “Everything’s ok”.
Because this doesn’t fully solve the problem, especially when cookies are still being used to identify conversions.
Here’s what you want to hear from your affiliate network:
1. That, advertisers all have a custom CNAME for tracking domains that match their sales page domain. (This makes it so that cookies being set are not classified as 3rd party cookies, plus it also enables the ability to lengthen cookies from the 7 day limits imposed by Apple on all Safari Browsers)
2. Affiliate ids are stored into a server side database such as MySQL etc, and they are directly linked to leads in the advertiser’s CRM if possible. (This makes it possible to have long term storage of attribution data by linking subids to something that is more permanent like an email address or a user account.)
3. On the client side, localStorage is being used instead of just cookies. localStorage is more private by design and has no cross domain tracking capabilities (cross domain tracking is what Apple and Firefox is trying to get rid of). The main key here is that localStorage much more permanent than cookies, and it provides a less invasive way of attribution for your clicks.
4. When conversions happen, attribution matching should happen from the server side as much as possible, but also be able to pull data out of localStorage.
Feel free to send this to the networks you work with. Even if you don’t understand what I said above, their tech team will understand and let you know what parts they are implementing.
By doing the above, it means they are getting paid for all the leads you are driving, and by proxy, you are also getting paid for all your leads. ”