Tracking signups from shared content

Contribute Feature
1

Hello

Following my question here I’m suggesting this feature.
https://meta.discourse.org/t/tracking-signups-from-referrals/56521/8?u=wil

I think shared content leading to a signup should count as an invitation

I believe users are more likely to share interesting content than send email invitations.

Each time a user lands on Discourse through a ?u=username link and then signs up, this should be counted as an invitation by @username

This could appear like this on the user profile (screen from /users/username/invited/redeemed in french )

image.png1117×244 32.6 KB

Pros

  • Able to track influencers based on actual signups not only traffic
  • Removing steps to invite people (literally 2 clicks away on any URL)

Cons

  • Risk of fake signups (but no incremental risk compared to email invitations)

Who else is interested in this?

Any comments or ideas?

12개의 좋아요
2

I like this idea, and I don’t think its too hard to implement.

I think if you share a link on twitter that somehow leads to someone signing up you had some influence on the account creation and this should be tracked.

I am putting a pr-welcome on this for now, but we can revise later and see if we add it to a release.

11개의 좋아요
3

What exactly is expected here?

From a developer’s point of view:

  • include a schema change (to add a referred_by field to table users)
  • look for the parameter that says who is the referral and store it in a session
  • change sign up mechanism to save the referral field from sessions into the referred_by field

From an administrator’s view of point:

  • dashboard with statistics that show the user that brought the most users
  • and the user who brought most visitors (did not register an account)

From a user’s view of point:

  • can he specify the name of the user that referred him even though he did not do that by giving him a link
  • should the part that is used for link sharing to be modified to also include the referral parameter
5개의 좋아요
4

Sure, but this is stretch-goal territory.

Same as above I think, but I’m also not entirely clear on what you’re proposing here. Could you please rephrase, with a bit more detail?

2개의 좋아요
5

Nevermind. I did not notice that ?u=<username> part in the links that are shared and thought that this is a requirement as well.

2개의 좋아요
6

I’d love to see this feature also! This would be extremely useful. Any updates on this?

2개의 좋아요
7

This will likely be part of this year’s GSoC. Stay tuned :wink:

3개의 좋아요
8

Just checking in to see if there are any updates on this?

9

It did not get picked up for GSoC, but if @nbianca or anyone else wants to take this on we’d be happy to sponsor the work.

10

Not looking to go off the topic, but my question here seems not far off from this one

13

I want to do this.

How does the sponsorship work?

1개의 좋아요
14

I’ll send you a pm about it.

16

이 기능이 실제로 프로덕션에 적용된 적이 있나요? :slight_smile: 저도 꽤 관심이 있습니다.

4개의 좋아요
17

최근에 초대 기능을 대폭 개편했는데요, @sam 이 이슈를 분류해 주시겠어요?

3개의 좋아요
18

OP(원포스터)가 언급한 것은 우리가 아직 구현하지 않은 부분이며, 그가 도달하려는 개념은 다음과 같습니다:

  1. 내가 공유합니다: https://meta.discourse.org/t/tracking-signups-from-referral/56911?u=sam

  2. 세션에 "Sam이 이 사용자를 사이트로 유도했다"는 정보를 저장합니다.

  3. 나중에 이 사용자가 계정을 생성합니다.

  4. 해당 계정은 "Sam"에게 귀속됩니다.

기술적으로 이 기능을 구축하는 것은 그리 어렵지 않습니다. @codinghorror 님이 모든 세부 사항과 UI를 일관되게 구현하는 데 약 1주일이 소요될 것으로 예상합니다. 이 작업을 일정표에 포함할 시기가 되면 알려주세요.

4개의 좋아요
19

아 네, 설명해 주셔서 감사합니다. 우리가 의도했던 것과는 조금 다른 방향이네요. 저는 게시물 공유를 명시적 초대보다는 암시적 초대라고 봅니다.

주요 목적은 초대받은 사람이 초대를 수락할 경우, 명시적 초대가 추적되도록 하는 것입니다.

1개의 좋아요