一些电子商务数据未被GTM拾取
我们目前正在使用标准电子商务推动交易，尽管我们的大多数交易出现在Google Analytics（分析）中，但却没有。通过比较Google Analytics（分析）与我们目的的交易记录中出现的内容，已经确认了这一点。我们尝试通过将相同的JSON/对象发送到我们的服务器，然后将其登录AS-IS后立即添加“记录”对象成功。
在Google Analytics（Google Analytics）中注意到了几个新的丢失交易之后，我们刚刚检查了日志，我们注意到当交易丢失时，交易JSON/对象都缺少Uniqueeventid属性。在发送事件时，GTM似乎会自动添加该属性，但是目前尚不清楚什么会导致其不添加。
这是我们当前发送到GTM的数据：
{
event: "deposit",
transactionId: <uuid string>,
transactionTotal: (<cents> / 100),
user_id: <uuid string>
}
我们使用window.datalayer.push将其发送到GTM。这也是我们将JSON推到GTM对象之后发送给服务器进行登录的内容。所有日志都显示了上述JSON带有附加属性iniqueeventid，除了在GA中没有出现的交易，而GA中所有属性都缺少该日志中的属性。
最终，我们只想解决GA中缺失的交易。
We're currently pushing transactions using Standard Ecommerce, and while the majority of our transactions appear in Google Analytics, a few do not. This has been confirmed by comparing what appears in Google Analytics vs the transactions records we have on our end. We tried adding "logging" immediately after the transaction data object was pushed to GTM by immediately sending that same JSON/object to our servers and then just logging that as-is, so that there was something to verify that we at least pushed the data object successfully.
Having just checked the logs after noticing a couple new missing transactions in Google Analytics, we noticed the transaction JSON/object was missing the uniqueEventId property whenever a transaction went missing. It would seem that the property is automatically added by GTM when an event is sent out, but it's unclear what would cause it to not be added.
Here's the data we're currently sending to GTM:
{
event: "deposit",
transactionId: <uuid string>,
transactionTotal: (<cents> / 100),
user_id: <uuid string>
}
we send this to GTM using window.dataLayer.push. That's also what we send to our servers to log after the JSON has been pushed to GTM's object. All of the logs show the above JSON with an additional property uniqueEventId, except for the transactions that don't appear in GA which all are missing that property in the logs.
Ultimately we just want to address the missing transactions in GA.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个显着的差异吗？如果没有，您也许可以解释广告障碍物等的区别。他们会阻止请求出现在Google Analytics（分析）中，从而准确地反映了您的建议。
Was it a significant difference? If not, you might be able to explain the difference with ad-blockers and the like. They'd prevent the requests from showing up in Google Analytics, reflecting exactly what you're suggesting.