Subscription Data Integration

Blueshift helps you track the subscription data of your users.

Users Attributes:
If user subscription information is easily accessible in your system, you can use User Creates/Updates API to update Blueshift user attributes and segment your users.

Events

If the subscription information is not readily accessible, you can use Blueshift subscription events to manage the subscription data of the user.

Blueshift supports the following standard events to manage the subscription status on the user:

  • subscription_start
  • subscription_upgraded
  • subscription_downgraded
  • subscription_billing
  • subscription_cancel

1. Subscription User Attributes

Blueshift infers standard attributes based on the subscription events, which are available as user attributes for segmentation.

  • subscription_created_at: When the first subscription happened
  • subscription_started_at: When the most recent subscription started
  • subscription_updated_at: When the most recent subscription event happened
  • subscription_period_type: The Period type for the subscription Ex: monthly/annually. This attribute is optional, but if you want to set this attribute you can pass it in the subscription event or update the user attribute.
  • subscription_plan_type: The Plan type for the subscription Ex: free, starter, premium, gold etc. This attribute is optional, but if you want to set this attribute you can pass it in the subscription event or update the user attribute.
  • subscription_canceled_at: When the subscription got canceled
  • subscription_status: active/canceled/paused. The most recent subscription event determines the status of the subscription. 

2. Subscription Events

Blueshift infers some standard user attribute's based on the subscription events. Please find more information below

a. subscription_start

Sample Event:

Screen_Shot_2018-09-17_at_6.17.30_PM.png

 User Attributes inferred:

  • subscription_started_at: Will be set to subscription_started_at event attribute or the time when we received this event
  • subscription_created_at: Will be set to the current date if it's a new subscription
  • subscription_status: Set to active
  • subscription_canceled_at: This attribute will be reset

b. subscription_upgrade
Sample event:

Screen_Shot_2018-09-17_at_6.18.31_PM.png

 User Attributes inferred:

  • subscription_started_at: Will be set to subscription_started_at event attribute or the time when we received this event, if it was not previously set
  • subscription_created_at: Will be set to the current date if it's a new subscription
  • subscription_updated_at: The time when we received the event
  • subscription_status: Set to active
  • subscription_canceled_at: This attribute will be reset

c. subscription_billing
Sample event:

Screen_Shot_2018-09-17_at_6.19.30_PM.png

 User Attributes inferred:

  • lifetime_orders: Lifetime orders get incremented
  • revenue: Increments the lifetime revenue on the user
  • subscription_status: Set to active

d. subscription_cancel

Sample event:

Screen_Shot_2018-09-17_at_6.20.34_PM.png

 

User Attributes inferred:

  • subscription_status: Set to canceled
  • subscription_canceled_at: Will be set to subscription_started_at event attribute or the time when we received this event, if it was not previously set
  • subscription_started_at: Will be reset

 

3. Segmentation

You can use these user attributes to segment users based on their subscription status. Please find some sample use cases below:

## New users who are on free trial

Screen_Shot_2018-09-17_at_6.21.33_PM.png

 

## Paid users who churned recently

Screen_Shot_2018-09-17_at_6.22.26_PM.png

  

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request