App channel source tracking technology that allows more efficient invite App

With the rapid development of the market, mobile Internet growth pattern is beginning to be confirmed, the moment almost all types of App can see the invitation mechanism figure, such as: IT apprenticeship class App, App electricity supplier's fight groups like cut price, battle games category App's invitation, even a large number of traditional channels promotion push, CPS, there are also invited to link nature.

 

In the form of an invitation mechanism similar, basic is an invitation to friends of invitees, a friend accepts the invitation, the invitation is automatically established relationship for both parties, and issue an appropriate reward.

 

We did product all know that in this process the most vexing is not a form of reward, such as the number of commission incentives, after all these through the strategic research and testing are at any time to adjust. The key is to invite the process of design as it relates to the user experience, conversion efficiency, a wrong product flow once on the line, unless heavy losses, or in most cases will continue to do so, so try to avoid tasteless as tasteless gesture of invitation process.

Design invitation process

 Since the invitation process is so important, then what kind of process is most reasonable to invite it?

 

Current mainstream App invite There are two main processes:

 

One is invited to share the landing page, fill in your friends phone number + SMS verification code in the page, and then download the App, using the same phone number registered App sign, background uploaded by landing page and App registered mobile phone number twice alignment, it is binding can invite relationship between the two.

 

The disadvantage is that the invitation of the overall process is too long and needs to enter a friend code + phone number twice, once in the H5 landing page, once registered in the App, the operating cost is too high.

1.png

(Landing page invitation form)

 

Another is to fill out an invitation code, invite people to generate unique invitation code within the App, after the invitation code sent to friends, friends copy the download App, for the first time fill in when registering, backstage invitation code data by comparing uploaded on You can invite relations binding the two sides and an award.

 

Obviously, an invitation code is a bunch of garbage disorderly, and not a very good brand image inviting broadcast, invite people to pay the costs of the benefits of education to explain to your friends download the App, and friends need to copy the invitation code in chat history in and then paste in the invitation code App, this mode of operation is also simple enough.

 2.png      

(Invitation code invitation form)

 

Both have advantages and disadvantages, in that case, we can consider doing a process optimized for both:

 

1、是否能让邀请落地页不必输入手机号码。即用户在落地页下载时自动记录用户信息,待新用户在App上注册时,再调取落地页上的用户信息进行绑定。

 

2、同理,是否能让用户不必填写邀请码。即隐藏邀请码,改为发送邀请落地页形式,并在url上记录邀请码ID,当好友通过该落地页下载并登录App时,写入邀请码参数进行绑定。

 

其中最关键的点在于如何记录用户信息,即获取用户的邀请来源。

 

如何获取邀请来源?

 

技术上,如果自己开发需要打磨一套高精准度的信息采集方案,并且还要花费大量时间和测试成本到市场中验证可行性,一个不成熟、精度不够高的技术方案在实际推广中会存在巨大的风险隐患。总的来说,从头开始研发一套技术方案成本和风险还是太高了。想要快速实现这一方案可以考虑使用专业第三方开发商的产品,以渠道追踪工具openinstall举例。

 

openinstall将这一方案称之为免填邀请码,技术流程方面,就是在发送的落地页url里,通过集成openinstall的js sdk来写入用户ID(邀请码)参数,好友一旦进入该页面就会被记录到有效参数,通过该页面下载App再注册时,调取渠道信息写入,即可匹配双方邀请关系。

 

有了完美的解药后,回到邀请流程上思考,理论上一个完美的邀请流程也就应运而生:

 

邀请人发送邀请链接(即H5落地页)给好友,好友只需点击进入,通过该页面下载App并打开注册,即可自动获得奖励。

 

整个流程中用户只需点击下载登录即可。对于平台方而言,点击落地页时会自动上传新用户和邀请者的信息,暂存到服务器中,当用户新用户下载App并注册时,就能从服务器中调取相应的信息匹配双方关系。

 

这是减少邀请流程的一小步,却是提高用户体验和转化效率的一大步。

  3.png      

(免填邀请码形式)

 

更多应用场景

 

技术是生产变革的根本之一,事实上只要打通技术难题,就能带来无限的想象空间。在这种渠道来源追踪技术下,我们可以优化许多传统推广场景中不必要的繁琐环节。

 

比如:

  • 与App邀请同理,将App地推推广中的用户ID作为渠道参数,即可省去填写地推码环节,自动识别邀请关系并计入地推员业绩。

  • In a social invitation, the invitation will automatically write ID as a parameter, you can achieve the automatic download as a friend, without the user having to manually search for friends nickname.

  • In the game invitation for a match, the war room number ID as a parameter write, will be able to achieve a key to enter the war game room, without the user having to manually search for the room number.

openinstall a variety of application scenarios 1.png      

 You can actually use scenarios to develop brain-hole according to their business, to take advantage of this technology. such as:

  • Banking, insurance App, through the sharing of account managers to make their business card to the development of new users scan code, the new user downloads automatically binds him to account manager.

  • Information App class apprenticeship recommendation, inviting people to share their invitation landing page, friends download through the App page, automatically binds the parties to the mentoring relationship, and issued the task reward.

  • 12K educational App, can each generate two-dimensional code unique parameters for each class cadre of teachers or partner institutions, allowing them to promote their products with their own two-dimensional code, automatically included in the results, and give the commission reward.

 

In addition, statistical data channel can also be used, reducing the scene, link promotion channels (free channels play package) and so on. I believe we can apply these scenarios to optimize product flow and user experience, improve efficiency and promote the flow conversion rate, let App grow more with less.

Guess you like

Origin blog.51cto.com/14379116/2454835