website logo
Navigate through spaces
⌘K
OVERVIEW
ORDER MANAGEMENT (OMS)
SHIPPING - SETUP
Shipping Methods
Shipping Zones
Shipping Method Setup Examples
TAXES - Setup
Tax Automation with Stripe Tax
Tax Automation with Avalara
CONTENT MANAGEMENT (CMS)
DATA
CUSTOMER LIFETIME REVENUE
Customer Lifetime Revenue Explanation
Customer Lifetime Revenue and Purchase Likelihood
Recency Frequency and Monetary
CLR and RFM Data Table Glossary
RFM and CLR in the Hub
LOOKER
Modifying a Dashboard
Timestamp differences between Looker, OMS and Shopify
How to create custom calculations in Looker
Looker and Shopify data models
Custom fields
How to 'Save and Schedule' reports
Creating Custom Reports or Look
Looks vs Dashboards
Login Looker FAQ
Looker Glossary
SEGMENT EVENT TRACKING
What are event tracking
Adding Tracking
What is the Tracking Plan?
The Chord Tracking Plan
The Shopify Tracking Plan
Event Tracking FAQ
EVENT UPDATES PAGE
Email Subscription Payment Event Update
Product Feed Setup
Getting Segment to Production
Consent Management
Installing in Next.js
Installing in Gatsby
Integrations
👩‍💻Developer Tools
Using Chord with Shopify
Docs powered by archbee 

Email Subscription Payment Event Update

5min



Why is this change being made?

Previously, when payments failed for a Subscription, we would track the # of payment failures for that subscription. That failure value would be sent to email providers via Segment Track event, with the count of failures in the email name. Unfortunately, that created an issue for some email services because they receive the 'same' email with different names (depending on the number of failures). See screenshot below "Original event".

This update will:

  • Standardize email payment failure events on a single email name, and
  • Include the # of failures in the payload.



Event changes

The Email Subscription Payment Failed event will change as follows:

*email_name: This will change from Email Subscription Payment Failed (First Time) to Email Subscription Payment Failed

*failure_counter: This count will be added to the payload and will include the number of payment failures for the current installment of the subscription (e.g., failure_counter: 2 if the subscription payment failed twice).

Original event

Analytics.track( user_id: '1', event: 'Email Queued', properties: { affiliation: 'Plant', email: 'admin@example.com', email_context: { account_setting_link: nil, actionable_date: '04/11/2023', address: {...}, brand: 'plant', delay_link: nil, firstname: 'John', id: 2, interval_length: 1, interval_units: 'day', lastname: 'Smith', paused: false, prepaid: false, prepaid_subscription: {}, processing_state: 'success', products: [...], reactivation_link: nil, state: 'active', subscription_id: 2 }, email_name: 'Email Subscription Payment Failed (2nd time)', meta: {...}, ownership: {...} } )

New event

Analytics.track( user_id: '1', event: 'Email Queued', properties: { affiliation: 'Plant', email: 'admin@example.com', email_context: { account_setting_link: nil, actionable_date: '04/11/2023', address: {...}, brand: 'plant', delay_link: nil, failure_counter: 2, firstname: 'John', id: 2, interval_length: 1, interval_units: 'day', lastname: 'Smith', paused: false, prepaid: false, prepaid_subscription: {}, processing_state: 'success', products: [...], reactivation_link: nil, state: 'active', subscription_id: 2 }, email_name: 'Email Subscription Payment Failed', meta: {...}, ownership: {...} } )



Updated 18 Apr 2023
Did this page help you?
Yes
No
PREVIOUS
EVENT UPDATES PAGE
NEXT
Product Feed Setup
Docs powered by archbee 
TABLE OF CONTENTS
Why is this change being made?
Event changes
Original event
New event