Subscription Renewal Payments Being Synched Incorrectly

@pgray sorry for the delay on this one. Can you please tell us a little bit more info on the problem you’re experiencing? I’m having a hard time understanding what the actual bug is. We’ll be more than happy to help.

@pgray we’ll close this out for now – if you’re still having trouble please feel free to reach back out.

Thanks for getting back to me, Ryan.

We use Woo, Woo Subscriptions, Woo Memberships with Mailchimp on a membership website. So, members sign up and periodically – quarterly, yearly – their membership renewal payments are automatically processed through the Woo Subscription plugin.

We are using this Mailchimp for Woo plugin to track sales through our newsletters. The plugin accurately assigns revenue correctly to a newsletter. However, renewal payments are marked as a “sale” to some random newsletter – or so it appears.

For example, a member signs up through Newsletter 10 and their renewal is processed 3 months later and revenue assigned to Newsletter 3.

Can we stop recording renewal sales? If they are recorded then why not assign the sale to original newsletter (Newsletter 10)? Even that is not correct but at least it doesn’t give us a false positive on a newsletter (Newsletter 3) that did not result in that sale.

Hello, Ryan, will you please respond to this issue?

Hi @pgray sorry for the delay and thanks for the ping… let me explain how the campaign tracking currently works.

When an email goes out to a member, and the campaign gets a click that makes it to your website, we record that click on the customer. That campaign ID is stored on the customer for ANY future order.

Since your system processes renewals automatically, the renewal order’s “winning campaign” is set based on the last clicked email. I don’t think this is a bug, it’s more of a reporting issue that you’re trying to segment out folks that have not ordered previously for true “first time conversions” right?

I would ask that you reach out to your Mailchimp support rep and see about possibly doing some segmenting in order to view people that purchased within X days for the first time.

I will bring this up to the team and see if there might be a filter hook that we can use while assigning the campaign ID to the orders though, but that would require a custom function on your end to change the campaign ID based on whatever criteria you see fit.

Would that work for your situation? If that comes back as a possibility you can expect a ping here ??