Bug 218127 – AdClickAttribution logs not being shown in system log

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: WebKit Misc.

[Marçal]

Hi,

Safari Technology Preview: Release 115 (Safari 14.1, WebKit 15611.1.3.5)
Both Ad Click Attribution and Ad Click Attribution Debug Mode Experimental Features are enabled.

Different domains used for publisher and advertiser & publisher with the following tag included:
<a href="https://click.advertiser.example?pid=3" adcampaignid="52" addestination="https://advertiser.example" target="_blank"><img src="https://ad.example/creative_1.png" alt="click now!"></a>

As explained here: https://webkit.org/blog/8943/privacy-preserving-ad-click-attribution-for-the-web/ I expect to see the logs when using: log stream -info | grep AdClickAttribution

No other errors or warnings are shown in the Web Inspector

[Smoley]

Thanks for filing, please attach a reduced test case in the form of an HTML, codepen etc.

[Radar WebKit Bug Importer]

<rdar://problem/70692530>

[John Wilander]

(In reply to Marçal from comment #0)
> Hi,
> 
> Safari Technology Preview: Release 115 (Safari 14.1, WebKit 15611.1.3.5)
> Both Ad Click Attribution and Ad Click Attribution Debug Mode Experimental
> Features are enabled.
> 
> Different domains used for publisher and advertiser & publisher with the
> following tag included:
> <a href="https://click.advertiser.example?pid=3" adcampaignid="52"
> addestination="https://advertiser.example" target="_blank"><img
> src="https://ad.example/creative_1.png" alt="click now!"></a>

What happens if you drop the target="_blank" attribute?

> As explained here:
> https://webkit.org/blog/8943/privacy-preserving-ad-click-attribution-for-the-
> web/ I expect to see the logs when using: log stream -info | grep
> AdClickAttribution
> 
> No other errors or warnings are shown in the Web Inspector

[Marçal]

Hi,

After enabling/disabling the features & restarting several times, logs are working as expected now, so I'm going to close the ticket.

Thanks!

[Marçal]

Hi John,

My bad, forget the previous comment.
Removing the target="_blank" attribute did the trick and now it works.

Not sure if that's by design, but I'm reopening as using target="_blank" shouldn't be a privacy concern.

Thanks,

[John Wilander]

*** This bug has been marked as a duplicate of bug 214176 ***