Information sent to Attentive

Updated October 11, 2023 19:33

With the Attentive Integration, Ordergroove can send customer and event data for you to use in your marketing campaigns. The following is a list of all of the events and customer properties sent over for your Attentive segments and flows.

Subscriber Events

We send events about subscriber activities, detailed below.

Ordergroove Action	Attentive Event	Data sent to Attentive
Subscriber Created	Attentive Event Name: ordergroove.subscriber.create The Subscriber Create event is sent to Attentive when a customer creates a subscription for the first time only. You should use this event to start a drip campaign that reinforces the benefits of your subscription program to get them to the first subscription order.	These events are synced in real-time, and include the following data in each event: first_name last_name email phone_number subscriptions_subset: [ { frequency_days frequency_description id quantity product: { id name sku image_url detail_url } } ... ] We also update the customer profile, setting Ordergroove Subscriber Status to active.
Subscriber Canceled	Attentive Event Name: ordergroove.subscriber.cancel The Subscriber Cancel event is sent to Attentive whenever a customer cancels all of their existing subscriptions. You should use this as a way to identify customers who have fully churned from your brand.	These events are synced in real-time, and include the following data in each event: first_name last_name email phone_number subscriptions_subset: [ { frequency_days frequency_description id quantity product: { id name sku image_url detail_url } } ... ] We also update the customer profile, setting Ordergroove Subscriber Status to inactive.
Subscriptions Created	Attentive Event Name: ordergroove.subscriber.subscriptions_created The Subscriptions Created event is sent to Attentive whenever a customer checks out with one or more subscriptions. You should use this event to communicate that new subscriptions have been created.	These events are synced in real-time, and include the following data in each event: first_name last_name email phone_number subscriptions_subset: [ { frequency_days frequency_description id quantity product: { id name sku image_url detail_url } } ... ] We also update the customer profile, setting Ordergroove Subscriber Status to active.

Subscription Events

We send events about subscription activities, detailed below.

Ordergroove Action

Attentive Event

Description

Subscription Created

Attentive Event Name: ordergroove.subscription.create

The Subscription Created event is sent to Attentive whenever a customer creates a subscription.

You should use this event to gain a better understanding of your customer's journey and what subscriptions they chose to add. This event can be used to segment specific people who subscribed to and/or canceled specific products.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

We also update the customer profile, setting Ordergroove Subscriber Status to active.

Subscription Canceled

Attentive Event Name: ordergroove.subscription.cancel

The Subscription Canceled event is sent to Attentive whenever a customer cancels a subscription.

You should use this event to start a re-engagement and win-back journey.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Subscription Frequency Changed

Attentive Event Name:

ordergroove.subscription.change_frequency

The Subscription Frequency Changed event is sent to Attentive whenever a subscription's frequency is adjusted (by either customers or support agents).

You should use this to track trends in user behavior.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Subscription Payment Changed

Attentive Event Name:

ordergroove.subscription.change_payment

The Subscription Payment Changed event is sent to Attentive whenever a subscription's default payment method is adjusted (by either customers or support agents).

You should use this to track trends in user behavior. It can also be used as a way to exclude users from drip campaigns asking users to update their credit cards.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Subscription Quantity Changed

Attentive Event Name:

ordergroove.subscription.change_quantity

The Subscription Frequency Changed event is sent to Attentive whenever a subscription's quantity is adjusted (by either customers or support agents).

You should use this to track trends in user behavior.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Subscription Shipping Address Changed

Attentive Event Name:

ordergroove.subscription.change_shipping_address

The Subscription Address Changed event is sent to Attentive whenever a subscription's address is adjusted (by either customers or support agents).

You should use this to track trends in user behavior.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Subscription SKU Swapped

Attentive Event Name:

ordergroove.subscription.sku_swap

The Subscription SKU Changed event is sent to Attentive whenever a subscription's product is changed (by either customers or support agents).

You should use this to track trends in user behavior. There may be an opportunity to see if people who switch SKUs are more or less loyal.

These events are synced in real-time, and include the following data in each event:

frequency_days
frequency_description
id
product: {
  detail_url
  id
  name
  sku
  image_url
}
product_id
product_name
product_sku
quantity

Order Events

We send events about order activities, detailed below.

Ordergroove Action

Attentive Event

Description

Order Reminder

Attentive Event Name:

ordergroove.order.reminder

The Order Reminder event is sent to Attentive a predefined number of days before an order is placed (the default is five days prior).

You should use this to notify users of an upcoming order with a call to action to make any changes before it is placed.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Credit Card Expiration Warning

Attentive Event Name:

ordergroove.order.credit_card_expiration_warning

The Credit Card Expiration event is sent to Attentive when Ordgroove discovers the credit card on file is set to expire before the next order is placed.

You should use this to notify users of an upcoming issue preventing them from getting their next order with a call to action to update their card information before the next order is placed.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Canceled

Attentive Event Name:

ordergroove.order.cancel

The Order Canceled event is sent to Attentive when an order is canceled (either by a support agent or customer).

You should use this to notify users an upcoming order has been canceled.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Success

Attentive Event Name:

ordergroove.order.success

The Order Success event is sent to Attentive when an order is placed successfully.

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Date Changed

Attentive Event Name:

ordergroove.order.success

The Order Success event is sent to Attentive when an order is placed successfully.

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Payment Changed

Attentive Event Name:

ordergroove.order.change_payment

The Order Payment Changed event is sent to Attentive when an order's payment method is changed (by either a support agent or the customer).

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Address Changed

Attentive Event Name:

ordergroove.order.change_shipping_address

The Order Address Changed event is sent to Attentive when an order's shipping address is changed (by either a support agent or the customer).

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Rejected

Attentive Event Name:

ordergroove.order.reject

The Order Rejected event is sent to Attentive when an order fails to be placed. We include a reject reason and reject code to help tailor custom messaging around why we couldn't place an order.

You should use this message to tell customers that their order failed and to take steps to fix it.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
reject_reason
reject_code
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Sent Now

Attentive Event Name:

ordergroove.order.send_now

The Order Sent Now event is sent to Attentive when an order's place date is changed to as soon as possible (by either a support agent or the customer).

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Order Skipped

Attentive Event Name:

ordergroove.order.skip_order

The Order Skippedevent is sent to Attentive when an order has been skipped (by either a support agent or the customer).

You should use this to track user behavior.

These events are synced in real-time, and include the following data in each event:

discount_total
shipping_total
sub_total
total
items_subset: {
  product: {
    detail_url
    id
    image_url
    name
    price
    sku
  },
  subscription: {
    frequency_days
    frequency_description
    id: 
  },
  price: 0.01, 
  quantity: 1,
  total_price: 0.01
}
payment: {
  cc_number_ending
  cc_exp_date
  cc_type_description
}
place_date 
shipping_address: {
  address
  address2
  city
  state_province_code
  zip_postal_code
  country_code
}

Item Out of Stock

Attentive Event Name:

ordergroove.item.out_of_stock

The Out of Stock event is sent to Attentive when an item on an order is found to be out of stock. When an item is out of stock, we try the order daily until we can place it (maximum of 30 days).

You should use this to inform your customers of item delays, ideally choosing specific days by choosing specific intervals with the `days_since_first_attempt` variable. Ordergroove recommends Day 1, 15, and 30.

These events are synced in real-time, and include the following data in each event:

days_since_first_attempt
price
quantity
total_price
product: {
  id
  name
  sku
  image_url
  detail_url
}