Google Analytics iOS广告系列跟踪和网址构建器 [英] Google Analytics iOS Campaign Tracking and URL Builder

问题描述

我们希望使用Google Analytics跟踪iOS应用的安装情况。
我们已经完成的工作：

• 我们有上次

看起来一切正常。但跟踪链接不起作用。
对于用户，该链接已重定向，GA：campaign和ga：source在GA数据库中为空：

/i.stack.imgur.com/ZeMVY.pngalt =在Google Analytics Acquisition中没有任何内容，只有直接流量：

我们对URL Builder中的设备ID宏字段非常困惑。它填满了吗？任何其他的想法如何使GA追踪工作？ 解决方案

针对已经拥有应用和深入链接的用户的广告系列的处理方式完全不同。

设计用于移动adNetworks。当您在adNetwork中为您的应用创建此广告系列时，您可以与他们一起了解如何传递deviceId，每个网络可能都有自己的语法，并且可以使用两种不同的方法（ping或重定向）工作。

如果您打算在某种社交活动中使用此网址，或者只是通过访问该网址进行测试，则无法使用此网址。由于浏览器无法找出IDFA 只有应用程序可以。

这也是Google Analytics用来将广告点击与应用程序的实际安装相关联的ID。

以下是重定向模式下Google Analytics的工作原理：
$ b

1. 用户正在玩糖果粉碎，并为您的应用程序看到一个横幅。

用户认为这是一个非常可爱的应用程序，所以他点击它来安装你的应用程序。 移动网络从candy crush内部抓取IDFA，并将用户发送到如下所示的Google分析重定向网址： https://click.google-analytics.com/redirect



2. Google Analytics注册了针对您的AppId点击横幅广告的特定IDFA，并将广告系列参数存储了一段时间。

重新定向需要如果一切按计划进行，用户希望安装您的应用程序并启动它。 p>


3. 当他/她这样做Google Analytics时g收起IDFA并开始为您的应用注册统计信息，包括appId。

4. 然后，Google Analytics注意到，与点击相同应用ID的链接相同的IDFA就在几分钟前。 Google Analytics（分析）假设点击产生了一次安装，并将该活动信息分配给该用户。


>



Ping模式几乎相同，只是adNetwork自己发送url到analytics，所以用户不必经过重定向。





因此，您可以看到这是一段旅程，但如果您符合以下条件，它应该可以正常工作：





• 确认iOS启用广告系列跟踪
  
  
  
  
  • 开启管理>属性设置> Google Analytics内的iOS广告系列跟踪
  
  


• 确认Campaign网址上的appId与您的应用的appId匹配。


• 检查您的广告联盟中您应该使用哪些网址替换为用户IDFA


• 确保您拥有IDFA正在通过您的应用从Google Analytics（分析）发送（它不在d上默认）
使用广告系列网址构建工具。





测试中需要通过实时广告来实现或者广告的测试版本，如果网络提供的话。



更新（2015-02-25）



<问：如何为不通过广告联盟的广告系列安装跟踪？例如（社交活动，电子邮件活动......）



答：Google Analytics不支持此功能。其他归因工具可能会尝试在不使用IDFA的情况下对用户进行指纹识别，例如使用IP地址，但这不可靠，所以Google Analytics选择仅使用IDFA。





如果该活动是通过电子邮件发送的，您可能有其他指纹识别方法你显然知道用户的电子邮件，所以你可以将它存储在数据库中并给它一个uniqueId。当用户点击您的邮件营销时，您可以在您的系统上进行重定向，并将该用户ID注册为自定义维度，然后使用测量协议通过您的后端。
然后当/如果用户登录你的应用程序，你会得到相同的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:

• we have last iOS SDK 3.10
• we enabled idfa collection like it says here
• 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:

1. The user is playing candy crush and sees a banner for your app.

2. The user thinks it's a very sweet app so he clicks on it to install your app.

3. 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

4. Google Analytics registers that specific IDFA clicked on your banner for your AppId and stores the campaign parameters for a while associated with this.

5. The redirect takes place and the user lands straight at the AppStore for your App.

6. If everything goes according to plan, the user hopefully installs your app and launches it.

7. When he/she does so Google Analytics grabs the IDFA and start to register stats for your app, including appId.

8. Then Google Analytics notice that's the same IDFA that clicked on that link for the same appId just a few minutes ago.

9. 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广告系列跟踪和网址构建器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！