There should be a standard and a specification for pageviews and events. And all of that should be sent from various clients to the hiive. Then hiive can send it to GA, Data Warehouse, whatever else.
Each consumer shouldn't have to figure it out themselves or look at an existing implementation and figure out how to use it for a new use case.
The shape needs to have some default key values, and then a way for additional meta, so that it can support all use cases easily.
This might already exist, but we need documentation for the wp rest api for collecting events, a JS example, a PHP example. Engineers shouldn't have to reverse engineer an existing implementation, we should be able to just reference the docs.
Documentation should live in confluence.
Tracking number 0a14f99f-0e66-49fb-a77f-16fe591fb1cd
There should be a standard and a specification for pageviews and events. And all of that should be sent from various clients to the hiive. Then hiive can send it to GA, Data Warehouse, whatever else.
Each consumer shouldn't have to figure it out themselves or look at an existing implementation and figure out how to use it for a new use case.
The shape needs to have some default key values, and then a way for additional meta, so that it can support all use cases easily.
This might already exist, but we need documentation for the wp rest api for collecting events, a JS example, a PHP example. Engineers shouldn't have to reverse engineer an existing implementation, we should be able to just reference the docs.
Documentation should live in confluence.
Tracking number 0a14f99f-0e66-49fb-a77f-16fe591fb1cd