Hello everyone,
I’m a bit stumbled with App Pixels and their general purpose and I’d like some help or discussion on some issues here.
As you know both App Pixels and Custom pixels run in sand-boxed environment inside web workers. I understand the idea behind this and the security benefits but from a developer perspective, some things don’t make sense at all, is there anyone experiencing the following:
-
App pixels don’t have access to DOM, Window etc. They can subscribe to events but the only way to transmit these events is to a third party endpoint. They also don’t have access to the app routes due to same origin issues which leaves third party servers as only option. If you are to for example send some events via measurement protocol you can’t send them directly using fetch() because it executes client-side and measurement api secret will become visible to everyone. You can’t send it to a third party server as well due to the same reasons.
-
Custom Pixels have access to DOM, Document and Window and they can be used for client-side tracking but if you are to implement server-side tracking the issue is the same as with App Pixels. Without proper access to app routes to execute server-side request to third party servers, App Pixels are basically useless. They also don’t have access to DOM as well.
-
Furthermore, if we stick to Custom Pixels, we can’t create them using APP, a customer has to copy/paste some code manually which is prone to errors, not to mention impossible to keep up-to-date as well.
Has anyone struggled with all this or am I missing something in the picture?
Thank you all!
