Map the GA4 schema
GA4 exports events as nested, key-value fields rather than flat columns. Once your GA4 data source is connected (see Connect the data source), map its fields to Data 360 data model objects (DMOs) so Personalization can read them like any other source.
Map GA4 fields to DMOs
- Open the GA4 data lake object (DLO) that your connection created.
- Map
event_name,event_timestampandevent_dateto the matching fields on your engagement DMO. - Map the
user_pseudo_id(anduser_id, if you collect it) to the identifier field your identity resolution rules key on. - Map any
event_paramsoruser_propertiesentries you need to custom fields on the DMO — see the note below. - For e-commerce data, map the
ecommerceanditemsfields to your transaction and product DMOs. - Save the mapping and confirm new GA4 events populate the DMOs.
GA4 field groups you’ll map
| Field group | Example fields | Maps to |
|---|---|---|
| Event identification | event_name, event_date, event_timestamp | Engagement DMO |
| User identification | user_id, user_pseudo_id | Identity/profile DMO |
| Custom parameters | event_params, user_properties (key-value) | Custom fields on the matching DMO |
| Device and geo | device, geo | Engagement or context DMO |
| Traffic source | traffic_source, collected_traffic_source | Engagement or attribution DMO |
| E-commerce | ecommerce, items | Transaction/product DMO |
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).