The OWOX BI GA4 event-based web streaming allows you to enhance web streams by sending events directly to the OWOX BI Access point via HTTP requests.
Before you start
Before you start sending events, check the following statements:
- In the OWOX BI interface, you've created a new GA4 event-based web streaming (step-by-step guide).
How it works
- Use a unique access point URL, e.g. 'https://streaming.bi.owox.com/ga4/…/mp'. Note that there is no slash at the end.
This URL you can find on the Settings tab on the Streaming page:
- The access point processes each request sent to it and stores it in the
debug_info.raw_request
field as it is without changes. - You can send any events, for example:
- Regardless of when these events happened (events from yesterday can be sent today with the actual date and time).
- Any events with your list of
event_params
fields can be sent. The OWOX BI algorithm does not automatically add parameters (with the key name '&ep.*') to events sent via the Measurement Protocol.
Request requirements
- According to the official documentation, the request must comply with the Measurement Protocol (Google Analytics 4).
- The
events[]
array must contain at least one object. - Parameter
client_id
is required for data blending with session data. OWOX BI algorithm saves this parameter in theuser_pseudo_id
field.
Optional parameters
-
Query parameters (
api_secret
andmeasurement_id
). If you send it, we will ignore it. -
Transaction sources. To transfer transaction source information for use in marketing reports, include relevant fields about the source in the
params
field. This data will then be stored in the final table. Here's an example:
{ "client_id":"client_id", "events":[ { "name":"campaign_details", "params": { "campaign_id":"google_1234", "campaign":"Summer_fun", "source":"google", "medium":"cpc", "term":"summer+travel", "content":"logolink" } } ] }
Issues
If the request structure does not match, data parsing will not occur. You can see the original request in the debug_info.raw_request
field.
0 Comments