You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With 10.1, we have all URLs classified against their responsible entities. It's now easy to identify a 1P/3P URL and understand who it belongs to. It would be good to provide further visibility into who "invited" a URL/entity in — essentially bringing in the full dependency information.
I'm visualizing this as a tooltip on any report URL. We could use dependency graph computed audit / initiator to find the parent of a URL, and expose it in LHR as a Record<url:string, parent:number> (or a minimum-prefix Trie structure if the URL payload increase is a concern).
PS: My mental model around this is: In 10.1 we added the answer to "Who are all in my party?". This should help answer better the question, "Who gave this URL/entity the ticket in?". Since this information could benefit attribution of all URLs and not just 3Ps, it might be better implemented as a report-wide implementation.
The text was updated successfully, but these errors were encountered:
With 10.1, we have all URLs classified against their responsible entities. It's now easy to identify a 1P/3P URL and understand who it belongs to. It would be good to provide further visibility into who "invited" a URL/entity in — essentially bringing in the full dependency information.
I'm visualizing this as a tooltip on any report URL. We could use dependency graph computed audit /
initiator
to find the parent of a URL, and expose it in LHR as aRecord<url:string, parent:number>
(or a minimum-prefix Trie structure if the URL payload increase is a concern).PS: My mental model around this is: In 10.1 we added the answer to "Who are all in my party?". This should help answer better the question, "Who gave this URL/entity the ticket in?". Since this information could benefit attribution of all URLs and not just 3Ps, it might be better implemented as a report-wide implementation.
The text was updated successfully, but these errors were encountered: