Tag Build 将 GA4 事件需求转换为可直接交给 Google Tag Manager 的 JSON——无需电子表格、服务器配置或 GTM 内部知识。团队可以交付结构化、可审查的 payload,而不是临时拼凑的配置。
追踪需求频繁变化。没有结构化的构建流程,每次 GTM 更新都可能导致 payload 不一致,让分析报告难以调试。Tag Build 将每个事件规格保存为可审查的产物,确保变更有迹可循。
查看 GA4 事件规格如何映射到 Tag Build 的输出格式:
{
"comments": "----- usual event data -----",
"event": "begin_checkout",
"ecommerce": {
"value": "$value",
"currency": "$currency",
"items": [
{
"item_id": "$item_id",
"item_name": "$item_name",
"item_brand": "$item_brand",
"item_category": "$item_category",
"item_category2": "$item_category2",
"item_category3": "$item_category3",
"item_category4": "$item_category4",
"item_category5": "$item_category5",
"discount": "$discount",
"price": "$value",
"quantity": "$quantity",
"coupon": "$coupon",
"index": "$index",
"item_variant": "$item_variant"
}
]
}
}[
{
"comments": "----- Tag Build format -----",
"event": "another_event"
},
{
"comments": "----- usual event data -----",
"event": "begin_checkout",
"ecommerce": {
"value": "$value",
"currency": "$currency",
"items": [
{
"item_id": "$item_id",
"item_name": "$item_name",
"item_brand": "$item_brand",
"item_category": "$item_category",
"item_category2": "$item_category2",
"item_category3": "$item_category3",
"item_category4": "$item_category4",
"item_category5": "$item_category5",
"discount": "$discount",
"price": "$value",
"quantity": "$quantity",
"coupon": "$coupon",
"index": "$index",
"item_variant": "$item_variant"
}
]
}
}
]