Hey Troy Media, The network-wide tracking code works just like a normal tracking code. You can create a property in GA using your network site URL (that is your main site URL). And it will track the whole network. The tracking code will be placed on all the subsites and the GA stats will be shown from all the subsites. You can still setup different tracking code in subsites. So when both are set up, the network tracking code will also be placed along with the subsite's tracking code. You may need to setup view filters if you would like to see the stats separately from each subsite when using network-wide tracking code. This tutorial can help you with that. Regards, Joel James

Yes, Stripe customer will be the same for all blog subscriptions of a user. So one Stripe customer can have multiple subscriptions. If you see different Stripe customer accounts for different subscriptions of the same user, then those accounts should be old. But it should work without any issues. Could you please check the Stripe customer table of Pro Sites and see if those customer IDs and Subscription IDs are synced properly there? Regards, Joel

Hey Ben, Yes, Pro Sites need those metadata. Basically blog_id, level and period are stored in metadata for an active blog. You can check that by creating a new site and check the subscription meta of the newly created site. Old blog data may not have all these, but Pro Sites will try to get those data from the database in that case. But I don't think this should affect the logging feature of Pro Sites. If you could grant support access we can have a look. Regards, Joel

Hey Ben, Sorry for the trouble. Are you sure that the webhook is setup properly? If the payment logs are not available in Pro Sites, somehow the webhook delivery is failed. Can you give us support access to your site and share the blog id of the customer? If that's not possible, can you share the screenshots of the Pro Sites dashboard and the logs of the site? Regards, Joel

Hey Ben, Are you sure that the old site's subscription is recurring? Cancellation link is not set when the subscription is already cancelled or not recurring. I have tested this from version 3.5.6, but could not reproduce this. If you are sure that the old subscription is recurring and not cancelled, can you share the old version number, from which you upgraded to the latest version? It will be helpful for us to debug this further. Regards, Joel

Hey Guy, Sorry for the confusion. Kasia Swiderska was referring to the WPMU DEV Hosting dashboard. You will find the Object Cache flush option in Tools -> Object Cache -> Flush, within your hosting dashboard. Regards, Joel

Hey Mr Right Now, Sorry for the trouble. We have fixed those duplicate queries issue in the upcoming version, which is currently in QA testing. I have attached the beta version here. Could you please try that? I strongly suggest you take a backup before you install the beta version. Regards, Joel