well. if your goal isn't tracking individuals, then why are you attaching unique ID's (in cookies) to track individuals on your website?
And I'm not talking about third-party cookies disguised as first-party.
logglytrackingsession (lifetime: session)
notion_experiment_device_id (lifetime: 1 year)
Both are unique to a specific user and are used to identify a single individual. The first one is short-lived, but obviously meant for tracking and the second one can be used for tracking, identifies a single individual and is long-lived.
edit: turning off my adblocker, some more appear.
_ga, _ga_4GMCF7E1GC, intercom-id-gpfdrxfd, notion_browser_id, amp_af43d4
none of these are listed or explained in your privacy policy.[1]
[1] - https://shared-crater-f3a.notion.site/Sticky-Privacy-Policy-...
My real point is, if you use a service to provide your own service, you give them your blessing to do whatever they want with your brand. This includes facebook and their tracking scripts.
Thus we need to audit what our service providers are doing and limit their impact once we've completed the evaluation, making sure they don't alter the deal later.
Also tracking ad conversions is as simple as using a unique parameter per campaign, when buying the add. Just append `?campaign=facebook_campaign-name_202202` to your link and that's enough to measure the ads effectiveness. No need to attach unique ID's to users, sessions etc... Aggregates keep the users anonymous and give you enough actionable insight.
As for your second point, yes, that is precisely what I referred to in my original post - that we could deal with the end of IDFA / that we just want to make sure ads are effective - SKAN which provides aggregated statistics is mostly ok for us.
While I agree, that a full audit would be difficult for smaller operations, it took me 2-5 minutes to do a quick check on what is being stored client-side and to come to a logical conclusion if individual users are being tracked or not.
It's a decision, one that you can (probably) make. For me, in the EU, it's no longer a choice and I personally think regulation(GDPR) was needed because, without it, no one took user-privacy seriously.
> As for your second point, yes, that is precisely what I referred to in my original post - that we could deal with the end of IDFA / that we just want to make sure ads are effective - SKAN which provides aggregated statistics is mostly ok for us.
GDPR would also apply here. If there's an option to process less data and achieve a similar result, one should use that option and using a more invasive method(identifying individuals) for tracking would be illegal. It's called "the data minimisation principle"
the fact that they're cracking down on partner privacy in a hamfisted way surely doesn't help matters but I can't see how angry devs are driving the share price down
Regarding your second point, yes, I agree - it's not obvious. Assuming this did indeed affect many developers like us and that it happened to everyone at the same time (which may not be the case - that it happened to us and that it coincided with their earnings report may have just been a coincidence - I haven't seen a mass outcry on twitter or anything), I was wondering whether it might be hedge funds that buy/track aggregated ad spend or attribution data, perhaps from MMPs or media buying agencies. I know they buy app download data from the likes of App Annie, but don't know if equivalent data is available and timely for ad spend. In any case, my point is more that this is illustrative of how they make bad situations worse for themselves.
They did that to us yesterday: https://shared-crater-f3a.notion.site/Facebook-is-Breaking-A...
We spend hundreds of thousands of dollars on facebook app ads per month. We can deal with IDFA giving way to more aggregated attribution (we don't want to track individuals - we just want to measure if the ads we paid for led to sales). But facebook breaking our app in production because they can't be bothered doing their job properly is very serious. It can't be solved by reducing ad spend, only by removing their SDK from our app.
If this is also happening to many other developers right now, that, more than the Q4 results or the IDFA issue itself, could be causing the drop in the share price.
In fact, if you look at the Q4 results, the earnings miss was more because of growth in G&A (which grew by 3 percentage-points of revenue if I'm not mistaken) than because of a top-line slowdown. And if you read the comments as to what made G&A grow, it's 'legal costs'.