subscriber-anniversary

Fires whenever a subscriber fires an anniversary alert after a successful resubscription

🚧

This Event is NOT for Real-Time Detection of a Subscriber Renewal!

If a subscriber renews properly, the subscriber-renewed event will fire as soon the successful renewal happens. subscriber-anniversary fires based on action by the subscriber. Namely, initiating an anniversary alert.

Using Socket.IO this event can be listened to as follows:

JavaScript

socketClient.on('subscriber-anniversary', function(data, callback){
  //do something
});

This event fires whenever a subscriber initiates an Anniversary Alert on GameWisp. See below for a description of Anniversary Alerts and how they're used.

The JSON response is as follows:

JSON

{
  event: "subscriber-anniversary",
	channel_id: 4,
	channel: 
  {
    names:
    {
      gamewisp: "gamewisp-channel-name",
      twitch:   "twitch-channel-name",
      youtube:  null,
    },
    ids:
    {
      gamewisp: 4,
      twitch:   123456,
      youtube:  null,
    },
  },
	data:
  {
    id: 16,
    subscriber:
    {
      ids:
    	{
        gamewisp: 83,
        twitch:   null
  		},
      usernames:
  		{
        gamewisp: "subscriber-username",
        twitch:   null
      },
      status: "active",
      amount: "2.50",
      subscribed_at: "2016-02-25 00:00:00",
      end_of_access: "2016-03-25 00:00:00",
      tier:
      {
        id: 6,
        title: "tier name",
        level: 1,
        cost: "2.50",
        description: "tier description",
        published: true
      },
    },
    fired: true,
    url: "https://gamewisp.com/alert/<unique-hash>",
    month_count: 1,
    subscribed_at: "2016-02-24 00:00:00",
    payment_date: "2016-02-25 16:47:34"
  }
}

The data object is described as follows:

Property	Type	Description
id	Integer	The unique identifier of the Alert Anniversary object.
subscriber	Object	The standard GameWisp subscriber object. Described in subscriber-new
fired	Boolean	A boolean indicated whether or not the Anniversary Alert has been fired by the subscriber. When using Singularity, the fired property should always be true.
url	String	A unique URL to fire the Anniversary Alert. Upon receiving this event; however, this URL will no longer be valid since the subscriber used to fire the Anniversary Alert that led to the subscriber-anniversary event.
month_count	Integer	The month count of the particular Anniversary Alert. Example: month_count = 3 indicates that the alert is for the subscriber's third consecutive month of subscription.
subscribed_at	String formatted UTC DateTime	The date of the subscriber's initial subscription.
payment_date	String formatted UTC DateTime	The date that the subscriber was successfully renewed.

What's an Anniversary Alert, Anyway?

🚧

Not all Anniversary Alerts are Fired

Since Anniversary Alerts require a subscriber clicking a link in an email sent to them to actually fire, some number of Anniversary Alerts in our system go unfired.

For this reason, it is generally not a good idea to rely on the subscriber-anniversary event to perform critical operations in your application. Use subscriber-renewed instead.

The following video gives a quick description of Anniversary Alerts and how they work.

An Anniversary Alert is how GameWisp handles providing on-stream recognition for subscribers upon successful renewal of their subscription. The standard flow of an Anniversary Alert is as follows:

1. The subscriber is successfully charged for another month of subscription on GameWisp.
2. The subscriber is sent an email containing a unique URL
3. The subscriber can then click on the URL in the email whenever the channel to which they're subscribed is streaming.
4. Clicking this URL initiates an on-screen alert sent through TwitchAlerts or StreamPro indicating that the subscriber has been subscribed for a particular number of months.

Specifically, the subscriber-anniversary event is fired immediately after the completion of Step 4. An application can use the receipt of this event to indicate that the subscriber is ready to receive some sort of recognition for subscribing for yet another month. This could be a pop up in your application, an automated "Thanks for your continued subscription" in a chat bot, etc.

Do not use this event as indication that the subscriber has been successfully renewed and your application needs to reallocate benefits or take any action related to successful renewal. That's what the subscriber-renewed event is for.