ga4-export-fixer 0.4.1-dev.2 → 0.4.1-dev.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -157,7 +157,7 @@
|
|
|
157
157
|
}
|
|
158
158
|
},
|
|
159
159
|
"session_first_traffic_source": {
|
|
160
|
-
"description": "The data extracted from the collected_traffic_source struct of the session's first event.
|
|
160
|
+
"description": "The data extracted from the collected_traffic_source struct of the session's first event. Can be used for building custom attribution models.",
|
|
161
161
|
"columns": {
|
|
162
162
|
"manual_campaign_id": "Manual campaign ID (utm_id)",
|
|
163
163
|
"manual_campaign_name": "Manual campaign name (utm_campaign)",
|
|
@@ -15,8 +15,8 @@
|
|
|
15
15
|
"ecommerce": "Transaction and revenue data. Filter to purchase or refund events (WHERE event_name = 'purchase') for ecommerce reporting",
|
|
16
16
|
"items": "Product-level data array. Unnest with CROSS JOIN UNNEST(items) for item-level analysis. For product revenue and units sold, filter to event_name = 'purchase' and use item_revenue and quantity. Use item_category to filter or group by product category",
|
|
17
17
|
"collected_traffic_source": "Event-level UTM parameters and click identifiers. For session-level attribution, prefer session_first_traffic_source instead",
|
|
18
|
-
"session_first_traffic_source": "
|
|
19
|
-
"session_traffic_source_last_click": "
|
|
18
|
+
"session_first_traffic_source": "Typically NOT used as the default field for general traffic source reporting. Use when building custom attribution models that require the session's first touchpoint, including sessions that started without a source (reported as direct)",
|
|
19
|
+
"session_traffic_source_last_click": "The default field to use for session-level traffic source analysis. For high-level 'traffic source' reporting, ALWAYS use .cross_channel_campaign.primary_channel_group as the primary dimension. Assume that the user wants the data on the channel grouping level. Even if they ask for \"traffic sources\". Use .cross_channel_campaign.source as a secondary drill-down when granular detail is required",
|
|
20
20
|
"data_is_final": "Data stability flag. Use WHERE data_is_final = true when you need only stable data that will not change in future refreshes",
|
|
21
21
|
"export_type": "Source export type (daily, intraday, fresh). Use for debugging data freshness or filtering by export source",
|
|
22
22
|
"row_inserted_timestamp": "Pipeline metadata. Use to identify when data was last refreshed or to debug incremental update issues"
|