[CANCELLED] Discord Server Analytics (Paid)

Bounties
#1

Bounty Request Format:

Discord Username - LGA.Code#0001

Payment Information - Willing to pay up to $500 depending on the full level of complexity completed for this cog. This is a serious undertaking and will require time commitment and examples of past cog work to be accepted for this request. Will also need to discuss legal compliance for GDPR and other privacy rights in regards to this project.

Description of Cog

Google Analytics but for Discord Servers. Please PM me for more info.

V2 or V3
Both - Will discuss possible payment of continued ongoing support

API’s or other information
Discord RedBot
Discord
WordPress (to output analytics data)

Other info (Bounty, issues, ETC) This is a bounty of up to $500 depending on level of commitment and quality. Must be on Red - Discord Bot and Red - Cog Support servers to be considered. Please PM me on Discord for questions or application.

1 Like
#2

Sinbad was originally going to take on this request but had to drop it due to some personal issues. This bounty is still available for others who are interested in the $500 reward.

#3

Sure, I’m willing to take this request on after learning more about it.

#4

One of the few public bots I know that has this is Yagpdb.
It has a web output aswel.

Sadly enough not usable for red but hey, the idea is there!
Here is a link to the code:

#5

Hey there,

We’re closing any bounties that have gone unclaimed for over 60 days. If you feel like this is an error, or are still interested in this bounty. Please flag this post with the Something Else category and state if you believe if this was a mistake, or if you’re still interested in this bounty.

#6
#7
#8

Reopened by request.

#9

This is now for V3 only.

#10

I’m potentially interested in this one.

#11

Connecting to the Google Analytics API is now a requirement for this request. This is where data from this cog will be outputted and stored. Find more info about it here:


#12

I also highly recommend that anyone that is interested in taking this on seriously review the Discord API Terms of Service and understand what they’re getting themselves into, especially the following sections: Sections 2.2.v, 2.4, 2.5.c, 2.5.d, 2.5.f, and Section 13. This is not easy to comply with and although we know many bots do not comply with all aspects of the ToS, we intend to.

#13

Cancelling and recreating because this post is bugged and won’t let me edit. Please see new post here:

#14