Hi @eszterbk
well, you have the link clicks happening on the other websites where they are counted from the ad networks.
But once the visitor reaches your website, you have factors like a not given cookie consent that will affect the analytics traffic that ends in your AA report suite.
On top of that, ad blockers play an important role, but should not play a huge role in your case since they would also likely block the initial click on the ad.
Which cookie consent provider do you use? Sometimes they can give you the opt-in rate for your defined consent categories e.g., Analytics/Performance, Marketing, etc.
To enhance tracking accuracy and maybe hide some of the calls from ad blockers, you can also define a CNAME / subdomain through which the tracking calls can be sent through.
https://experienceleague.adobe.com/en/docs/id-service/using/reference/analytics-reference/cname This was primarily designed to have the Adobe Analytics cookies being written in a 1st-party cookie context, but was also considered as a way to potentially hide some tracking calls by cloaking them through your own domain.
Though honestly, many ad blockers work on URL patterns and not only on host names, so if a standard Adobe Analytics call looks like this
https://sc.omtrdc.net or 2o7.net/b/ss/... , even if you sent the call through https://tracking.mydomain.com/b/ss/... instead, most ad blockers will likely identify this as an Adobe Analytics tracking call anyway.
Side note: I would also take reported clicks on ad networks with a grain of salt. In the past, I have come across cases, where the (big job network...) page was reporting many time higher number than the numbers we could see on AA side. And that was definitely not explainable by cookie opt outs.
