You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'd like to propose a change and check to see if it would engender support from the maintainers...
I'd like to make it possible to sync ecommerce data (and list signups) for guest orders as well. In our store, 75% of orders aren't associated with a user at checkout, but that shouldn't stop us from subscribing them to a list and having their orders tracked in Mailchimp.
I propose removing the checks around order.user_id being nil, and allowing the creation of Mailchimp customer resources for emails with a new Mailchimp customer_id schema.
If an order comes in with a user attached, continue to use customer_<spree_user_id> as the Mailchimp customer_id.
However, if an order comes in with no Spree user attached, use email_<email_address> as the Mailchimp customer_id.
Does anyone see challenges with this approach? If well implemented, would you consider adoption?
The text was updated successfully, but these errors were encountered:
Hi, I'd like to propose a change and check to see if it would engender support from the maintainers...
I'd like to make it possible to sync ecommerce data (and list signups) for guest orders as well. In our store, 75% of orders aren't associated with a user at checkout, but that shouldn't stop us from subscribing them to a list and having their orders tracked in Mailchimp.
I propose removing the checks around
order.user_id
being nil, and allowing the creation of Mailchimp customer resources for emails with a new Mailchimpcustomer_id
schema.customer_<spree_user_id>
as the Mailchimp customer_id.email_<email_address>
as the Mailchimp customer_id.Does anyone see challenges with this approach? If well implemented, would you consider adoption?
The text was updated successfully, but these errors were encountered: