Google Analytics iOS 广告系列跟踪和 URL 构建器 [英] Google Analytics iOS Campaign Tracking and URL Builder
问题描述
我们希望使用 Google Analytics(分析)为我们的 iOS 应用跟踪安装情况.我们已经完成的:
- 我们有最新的
看起来一切正常.但是跟踪链接不起作用.对于从此链接重定向的用户，GA 数据库中的 ga:campaign 和 ga:source 为空:
Google Analytics Acquisition 中没有任何内容，只有直接流量:
我们对 URL Builder 中的现场设备 ID 宏感到非常困惑.填对了吗?关于如何使 GA 跟踪工作的任何其他想法?
以下信息仅适用于 iOS 安装跟踪，针对已拥有该应用和深层链接的用户的营销活动的处理方式完全不同.
这是专为与移动广告网络一起使用而设计的.当您在 adNetwork 中为您的应用创建此广告系列时，您可以与他们合作以了解如何传递 deviceId，每个网络可能有自己的语法，并且它们可以使用 2 种不同的方法(ping 或重定向).
如果您打算在某种社交活动中使用此网址，或者您只是通过访问该网址来测试它，则它不会起作用.因为浏览器无法识别 IDFA，只有一个应用可以.
这也是 Google Analytics 用来将广告点击与应用的实际安装相关联的 ID.
以下是 Google Analytics 在重定向模式下的工作原理:
用户正在玩糖果粉碎游戏并看到您应用的横幅.
用户认为这是一个非常棒的应用，所以他点击它来安装你的应用.
移动网络从糖果粉碎机内部获取 IDFA 并将用户发送到如下所示的谷歌分析重定向 URL:https://click.google-analytics.com/redirect
Google Analytics(分析)为您的 AppId 注册点击您横幅的特定 IDFA，并将与此相关联的活动参数存储一段时间.
发生重定向，用户直接进入您的应用程序的 AppStore.
如果一切按计划进行，用户就会安装并启动您的应用.
当他/她这样做时，Google Analytics 会获取 IDFA 并开始为您的应用注册统计信息，包括 appId.
然后，Google Analytics(分析)注意到几分钟前点击同一个 appId 的链接的 IDFA 是同一个.
Google Analytics(分析)假定点击产生了安装并将广告系列信息分配给该用户.
Ping 模式几乎相同，只是 adNetwork 将 url 发送给分析本身，因此用户不必通过重定向.
正如你所看到的，这是一段相当长的旅程，但如果你:
- 确认已启用 iOS 广告系列跟踪
- 在管理">媒体资源设置">Google Analytics(分析)内的 iOS 广告系列跟踪"
- 确认您的广告系列网址上的 appId 与您的应用的 appId 匹配.
- 与您的 adNetwork 检查您应该在要替换为用户 IDFA 的 url 中使用的内容
- 确保您的 Google Analytics(分析)正在向您发送 IDFA应用程序(默认情况下未启用)
- 使用提供的广告系列网址构建器由 Google 提供.
为了进行测试，您需要通过实时广告或广告的测试版本来进行测试(如果网络提供).
更新 (2015-02-25)
问:您如何对不通过 adNetwork 的广告系列进行安装跟踪?例如(社交活动、电子邮件活动……)
A:Google Analytics(分析)对此不提供支持.其他归因工具可能会尝试在不使用 IDFA 的情况下对用户进行指纹识别，例如使用 IP 地址，但这并不可靠，因此 Google Analytics(分析)选择仅使用 IDFA.
如果活动是通过电子邮件进行的，您可能有其他方式进行指纹识别.您显然知道用户电子邮件，因此您可以将其存储在您的数据库中并为其指定一个 uniqueId.当用户点击您的邮件营销时，您可以在您的系统上进行重定向，您可以在其中将该 userId 注册为自定义维度，并使用 测量协议 通过您的后端.然后，当/如果用户登录您的应用程序，您将获得相同的 userId 并发送与其关联的其他点击.
您必须使用 uniqueId，因为根据 TOS，电子邮件本身在 Google Analytics 中是被禁止的.你不能把它送到那里.
此解决方案还有其他缺点，因为您会为在 GA 中点击您的广告系列的每个用户获得点击量，但只有那些实际安装了 APP 的用户才会在未来获得点击量.因此，您可能会因从未安装该应用程序的一次点击而夸大会话.出于这个原因，我建议将其发送到辅助 Google Analytics 网络媒体资源，以避免污染您的主要媒体资源.
如您所见，这不是一个很好的解决方案，但它是您唯一的方法.我不建议花时间在这样的解决方案上，因为它会产生其他问题并且不可靠.
We want to track installs with Google Analytics for our iOS app. What we already done:
- Build with IDFA available in AppStore ("ready for sale" in itunes connect)
- we have a tracking link that was generated using iOS Campaign Tracking URL Builder
Seems everything OK. But tracking link doesn't work. For user, that was redirected from this link, ga:campaign and ga:source are empty in GA database:
And there is nothing in Google Analytics Acquisition, only direct traffic:
We are very confusing about the field Device ID Macro in URL Builder. Is it filled right? Any other ideas how to make the GA tracking work?
The information below is only valid for iOS Install Tracking, Campaigns that target users that already have the app and deeplink into them are handled completely different.
This was designed to work with mobile adNetworks. When you create this campaign for your app in an adNetwork you can work with them to know how to pass the deviceId, each network might have its own syntax, and they can work in 2 different methods (ping or redirect).
If you are planning to use this url in a social campaign of some sort, or if you are testing it out by just visiting that url it won't work. Because a browser can't figure out the IDFA only an App can.
This is also the id used by Google Analytics to link an Ad click with the actual installation of the App.
Here's how it works for Google Analytics on redirect mode:
The user is playing candy crush and sees a banner for your app.
The user thinks it's a very sweet app so he clicks on it to install your app.
The mobile network grabs the IDFA from inside candy crush and sends the user to a google analytic redirect url that looks like this: https://click.google-analytics.com/redirect
Google Analytics registers that specific IDFA clicked on your banner for your AppId and stores the campaign parameters for a while associated with this.
The redirect takes place and the user lands straight at the AppStore for your App.
If everything goes according to plan, the user hopefully installs your app and launches it.
When he/she does so Google Analytics grabs the IDFA and start to register stats for your app, including appId.
Then Google Analytics notice that's the same IDFA that clicked on that link for the same appId just a few minutes ago.
Google Analytics assumes the click generated an install and assigns the campaign information to that user.
Ping mode is pretty much the same except that the adNetwork sends the url to analytics themselves so the user doesn't have to go through a redirect.
So as you can see it's quite a journey, but it should work fine if you:
- Confirm that iOS campaign tracking is enabled
- On Admin > Property Settings > iOS Campaign Tracking inside Google Analytics
- Confirm the appId on your Campaign url matches the appId for your App.
- Checks with your adNetwork what you should use in the url to be replaced with the user IDFA
- Make sure you have IDFA is being sent from Google Analytics on your app (it's not on by default)
- Use the campaign url builder provided by Google.
And for testing you will need to do that through either a live ad or a test version of your ad, if the network provides that.
UPDATE (2015-02-25)
Q: How can you do install tracking for campaigns that don't go through an adNetwork? eg (social campaigns, email campaigns, ...)
A: Google Analytics doesn't have support for that. Other attribution tools might try to fingerprint the user without using the IDFA, using IP address for instance, but that's not reliable, so Google Analytics opted to use only the IDFA.
If the campaign is through email you might have other ways to fingerprint. You obviously know the user email, so you can store it in your database and give it a uniqueId. When the user clicks on your mail marketing you can go through a redirect on your systems where you register that userId as a custom dimension and send a hit to GA with campaign information using the measurement protocol through your BackEnd. Then when/if the user logs in your application you get the same userId and send other hits associated with it.
You have to use a uniqueId because the email itself is forbidden inside Google Analytics per TOS. You can't send it there.
This solution has other drawbacks as you will get hits for every user that clicks in your campaign in GA, but only those that actually install the APP will have future hits. So you might have inflated sessions with a single hit that never install the App. For that reason I'd recommend sending this to a secondary Google Analytics Web Property to avoid polluting your main property.
As you can see it's not a great solution, but it's the only way you can do it. I wouldn't recommend spending time with a solution like this that creates other problems and is not reliable.
这篇关于Google Analytics iOS 广告系列跟踪和 URL 构建器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
