Title: Feedback - Moonbase
Open Graph Title: Feedback - Moonbase
X Title: Feedback - Moonbase
Description: Give Moonbase feedback on how they could improve their product.
Open Graph Description: Give Moonbase feedback on how they could improve their product.
X Description: Give Moonbase feedback on how they could improve their product.
Keywords:
Domain: feedback.moonbase.sh
| None | default-src 'self'; base-uri 'none'; script-src 'self' 'report-sample' 'unsafe-inline' https://app.intercom.io https://widget.intercom.io https://js.intercomcdn.com https://featurebase.app https://*.featurebase.app https://app.posthog.com https://r.wdfl.co/rw.js https://js.stripe.com https://maps.googleapis.com https://www.googletagmanager.com https://*.googletagmanager.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ assets.customer.io https://static.ads-twitter.com https://static.zdassets.com https://tb.featurebaseapp.com https://tbi.featurebaseapp.com https://cdnjs.cloudflare.com https://fb-resources.fra1.cdn.digitaloceanspaces.com https://scripts.simpleanalyticscdn.com; style-src 'report-sample' 'self' 'unsafe-inline' https://featurebase.app https://*.featurebase.app https://fb-usercontent.fra1.cdn.digitaloceanspaces.com https://fb-usercontent.fra1.digitaloceanspaces.com https://fonts.googleapis.com https://r.wdfl.co/rw.js; frame-src *; child-src *; object-src 'none'; block-all-mixed-content; upgrade-insecure-requests; img-src 'self' data: blob: https://featurebase.app https://*.featurebase.app https://fb-usercontent.fra1.digitaloceanspaces.com https://fb-usercontent.fra1.cdn.digitaloceanspaces.com https://*.featurebase-attachments.com https://cdn.jsdelivr.net https://emoji.slack-edge.com https://a.slack-edge.com https://js.intercomcdn.com https://static.intercomassets.com https://downloads.intercomcdn.com https://downloads.intercomcdn.eu https://downloads.au.intercomcdn.com https://uploads.intercomusercontent.com https://gifs.intercomcdn.com https://video-messages.intercomcdn.com https://messenger-apps.intercom.io https://messenger-apps.eu.intercom.io https://messenger-apps.au.intercom.io https://*.intercom-attachments-1.com https://*.intercom-attachments.eu https://*.au.intercom-attachments.com https://*.intercom-attachments-2.com https://*.intercom-attachments-3.com https://*.intercom-attachments-4.com https://*.intercom-attachments-5.com https://*.intercom-attachments-6.com https://*.intercom-attachments-7.com https://*.intercom-attachments-8.com https://*.intercom-attachments-9.com https://static.intercomassets.eu https://static.au.intercomassets.com https://*.google-analytics.com https://*.googletagmanager.com https://*.analytics.google.com https://*.g.doubleclick.net www.googletagmanager.com track.customer.io https://instatus.com https://dashboard.instatus.com ads-twitter.com ads-api.twitter.com analytics.twitter.com https://*.zendesk.com https://api.mapbox.com https://*.mapbox.com https://queue.simpleanalyticscdn.com https://simpleanalyticsbadges.com; media-src 'self' data: blob: https://featurebase.app https://*.featurebase.app https://fb-usercontent.fra1.cdn.digitaloceanspaces.com https://fb-usercontent.fra1.digitaloceanspaces.com https://js.intercomcdn.com https://customer-wdqko9h3ubekuskt.cloudflarestream.com https://customer-wdqko9h3ubekuskt.videodelivery.net https://global.featurebase-attachments.com https://*.featurebase-attachments.com; form-action 'report-sample' 'self' 'unsafe-inline' https://featurebase.app https://*.featurebase.app https://intercom.help https://api-iam.intercom.io https://api-iam.eu.intercom.io https://api-iam.au.intercom.io; font-src 'self' https://fonts.gstatic.com https://fonts.googleapis.com https://js.intercomcdn.com https://fonts.intercomcdn.com https://fb-usercontent.fra1.cdn.digitaloceanspaces.com; connect-src 'self' data: https://featurebase.app https://*.featurebase.app https://*.algolia.net https://*.algolianet.com https://*.algolia.io https://via.intercom.io https://api.intercom.io https://api.au.intercom.io https://api.eu.intercom.io https://api-iam.intercom.io https://api-iam.eu.intercom.io https://api-iam.au.intercom.io https://api-ping.intercom.io https://nexus-websocket-a.intercom.io wss://nexus-websocket-a.intercom.io https://nexus-websocket-b.intercom.io wss://nexus-websocket-b.intercom.io https://nexus-europe-websocket.intercom.io wss://nexus-europe-websocket.intercom.io https://nexus-australia-websocket.intercom.io wss://nexus-australia-websocket.intercom.io https://uploads.intercomcdn.com https://uploads.intercomcdn.eu https://uploads.au.intercomcdn.com https://uploads.intercomusercontent.com https://o4504213851144192.ingest.sentry.io https://app.posthog.com https://eu.i.posthog.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://firebaseinstallations.googleapis.com https://fcmregistrations.googleapis.com https://api.stripe.com https://maps.googleapis.com track.customer.io ads-twitter.com ads-api.twitter.com analytics.twitter.com https://fb-usercontent.fra1.cdn.digitaloceanspaces.com https://*.featurebase-attachments.com https://tb.featurebaseapp.com https://tbi.featurebaseapp.com https://api.mapbox.com https://*.mapbox.com https://customer-wdqko9h3ubekuskt.cloudflarestream.com https://customer-wdqko9h3ubekuskt.videodelivery.net https://fb-resources.fra1.cdn.digitaloceanspaces.com wss://ws.featurebase.app https://queue.simpleanalyticscdn.com https://www.google.com/recaptcha/ https://recaptcha.google.com/recaptcha/; manifest-src 'self' https://featurebase.app https://*.featurebase.app https://fb-usercontent.fra1.digitaloceanspaces.com https://fb-usercontent.fra1.cdn.digitaloceanspaces.com https://*.featurebase-attachments.com; worker-src 'self' blob: https://youtube.com https://share.descript.com/ https://*.descript.com/ https://www.loom.com/ https://intercom-sheets.com https://www.intercom-reporting.com https://player.vimeo.com https://fast.wistia.net; |
| msapplication-TileColor | #4f46e5 |
| theme-color | #4f46e5 |
| author | Moonbase |
| og:image | https://og.featurebase.app/?type=root&title=Have+something+to+say?&description=Tell+Moonbase+how+they+could+make+the+product+more+useful+to+you.&companyLogo=https://695b9a10c803dc1f3bd85a76.featurebase-attachments.com/c/static/019b8dd2-5360-78de-be90-df6035420a37/qh9i7z573k.png&companyName=Moonbase&companyThemeColor=#947bff&companyTLP=bottom&category=Feedback |
| og:type | website |
| twitter:image | https://og.featurebase.app/?type=root&title=Have+something+to+say?&description=Tell+Moonbase+how+they+could+make+the+product+more+useful+to+you.&companyLogo=https://695b9a10c803dc1f3bd85a76.featurebase-attachments.com/c/static/019b8dd2-5360-78de-be90-df6035420a37/qh9i7z573k.png&companyName=Moonbase&companyThemeColor=#947bff&companyTLP=bottom&category=Feedback |
| twitter:card | summary_large_image |
| referrer | origin |
Links:
| Roadmap | https://feedback.moonbase.sh/roadmap |
| Changelog | https://feedback.moonbase.sh/changelog |
| Help Center | https://help.moonbase.sh |
| Add a GET endpoint for customer identity and billing addressIt looks like the Storefront API currently allows us to set and update a customer’s billing address, but there does not appear to be an endpoint for retrieving the currently stored address. The sign-in and refresh responses only return the customer ID, name and email, and there is no documented GET endpoint for /api/customer/identity. For a custom customer portal, it would be very useful to have an authenticated endpoint such as: GET /api/customer/identity returning the customer’s name, email, billing address and communication preferences. Without this, we can update the billing address but cannot display or prefill the existing data.Marc Wensauer about 6 hours ago💡Feature Request | https://feedback.moonbase.sh/p/add-a-get-endpoint-for-customer-identity-and-billing-address |
| Add a GET endpoint for customer identity and billing addressIt looks like the Storefront API currently allows us to set and update a customer’s billing address, but there does not appear to be an endpoint for retrieving the currently stored address. The sign-in and refresh responses only return the customer ID, name and email, and there is no documented GET endpoint for /api/customer/identity. For a custom customer portal, it would be very useful to have an authenticated endpoint such as: GET /api/customer/identity returning the customer’s name, email, billing address and communication preferences. Without this, we can update the billing address but cannot display or prefill the existing data.Marc Wensauer about 6 hours ago💡Feature Request | https://feedback.moonbase.sh/p/add-a-get-endpoint-for-customer-identity-and-billing-address |
| Show the tax percentage in the checkout summaryHi Moonbase team, in the checkout summary, the tax is currently displayed only as an amount, for example: Sales tax: €7.18 It would be much clearer to also show the applied tax rate: VAT (19%): €7.18 This is especially useful for international customers, since the tax rate may vary depending on the customer’s country. For European checkouts, “VAT” would also be more appropriate than the generic term “Sales tax.” Thanks!Marc Wensauer about 7 hours ago2💡Feature Request | https://feedback.moonbase.sh/p/show-the-tax-percentage-in-the-checkout-summary |
| Show the tax percentage in the checkout summaryHi Moonbase team, in the checkout summary, the tax is currently displayed only as an amount, for example: Sales tax: €7.18 It would be much clearer to also show the applied tax rate: VAT (19%): €7.18 This is especially useful for international customers, since the tax rate may vary depending on the customer’s country. For European checkouts, “VAT” would also be more appropriate than the generic term “Sales tax.” Thanks!Marc Wensauer about 7 hours ago2💡Feature Request | https://feedback.moonbase.sh/p/show-the-tax-percentage-in-the-checkout-summary |
| Allow customization of the embedded checkout background colorHi, we are embedding the Moonbase checkout on our own branded portal. The checkout works well, but the large gray background around the checkout card does not match our design. Is it possible to customize that background color for our store. We only mean the outer page background behind the checkout card, not the checkout card itself. Thanks!Marc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/allow-customization-of-the-embedded-checkout-background-color |
| Allow customization of the embedded checkout background colorHi, we are embedding the Moonbase checkout on our own branded portal. The checkout works well, but the large gray background around the checkout card does not match our design. Is it possible to customize that background color for our store. We only mean the outer page background behind the checkout card, not the checkout card itself. Thanks!Marc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/allow-customization-of-the-embedded-checkout-background-color |
| SSO/session handoff between Custom Integration and Embedded StorefrontHi Moonbase team, we use the Custom Integration storefront mode. Customers authenticate through our server-side PHP integration using the Storefront API, and the access and refresh tokens remain securely stored in the PHP session. When we open the Embedded Storefront checkout, the browser widget does not recognize the existing customer session and asks for the customer details again. Is there a documented and supported server-to-browser session handoff or SSO mechanism for the Embedded Storefront? For example: a short-lived one-time token a signed session-exchange endpoint or another supported way to initialize the widget with an already authenticated customer We do not want to expose access or refresh tokens in the HTML or manually write the widget’s internal moonbase_authlocalStorage entry. What is the recommended architecture for sharing authentication between a server-rendered custom storefront and the Embedded Storefront checkout? Cheers, MarcMarc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/ssosession-handoff-between-custom-integration-and-embedded-storefront |
| SSO/session handoff between Custom Integration and Embedded StorefrontHi Moonbase team, we use the Custom Integration storefront mode. Customers authenticate through our server-side PHP integration using the Storefront API, and the access and refresh tokens remain securely stored in the PHP session. When we open the Embedded Storefront checkout, the browser widget does not recognize the existing customer session and asks for the customer details again. Is there a documented and supported server-to-browser session handoff or SSO mechanism for the Embedded Storefront? For example: a short-lived one-time token a signed session-exchange endpoint or another supported way to initialize the widget with an already authenticated customer We do not want to expose access or refresh tokens in the HTML or manually write the widget’s internal moonbase_authlocalStorage entry. What is the recommended architecture for sharing authentication between a server-rendered custom storefront and the Embedded Storefront checkout? Cheers, MarcMarc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/ssosession-handoff-between-custom-integration-and-embedded-storefront |
| Internationalization of customer surfacesHi, our storefront supports both English and German. Is there currently a way to set the language or locale of the embedded storefront and checkout, for example through Moonbase.setup()? Ideally, when our website is set to German, the complete checkout UI should also appear in German. I could not find a documented locale or language option. Is this already supported, or is localization planned? Cheers, MarcMarc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/german-localization-for-the-embedded-checkout |
| Internationalization of customer surfacesHi, our storefront supports both English and German. Is there currently a way to set the language or locale of the embedded storefront and checkout, for example through Moonbase.setup()? Ideally, when our website is set to German, the complete checkout UI should also appear in German. I could not find a documented locale or language option. Is this already supported, or is localization planned? Cheers, MarcMarc Wensauer 1 day ago2💡Feature Request | https://feedback.moonbase.sh/p/german-localization-for-the-embedded-checkout |
| PlannedCustom groups/segmentsWe want to support both static groups where you add customers manually or through APIs, and “segments” which are auto-updated groups of customers decided based on a combination of conditions on customer attributes and/or events.Tobias Lønnerød Madsen 3 days ago💡Feature Request | https://feedback.moonbase.sh/p/custom-groupssegments |
| PlannedCustom groups/segmentsWe want to support both static groups where you add customers manually or through APIs, and “segments” which are auto-updated groups of customers decided based on a combination of conditions on customer attributes and/or events.Tobias Lønnerød Madsen 3 days ago💡Feature Request | https://feedback.moonbase.sh/p/custom-groupssegments |
| Product AnalyticsToday, we support attaching custom metadata to licensing events, but we’d like to also be able to record custom events. This would enable actual product analytics, to know what features are used, and could also be fed into the marketing pipeline through custom segments/groups.Tobias Lønnerød Madsen 4 days ago💡Feature Request | https://feedback.moonbase.sh/p/product-analytics |
| Product AnalyticsToday, we support attaching custom metadata to licensing events, but we’d like to also be able to record custom events. This would enable actual product analytics, to know what features are used, and could also be fed into the marketing pipeline through custom segments/groups.Tobias Lønnerød Madsen 4 days ago💡Feature Request | https://feedback.moonbase.sh/p/product-analytics |
| CompletedMailchimp Integration Fails with Multiple AudiencesI am experiencing an issue connecting Moonbase to Mailchimp. My Mailchimp account has multiple audiences, and the integration fails with a "Multiple audiences found" error. The current integration does not provide an option to select a specific audience, which prevents successful connection.Thioune Philipp 6 days ago🐛Bug Reports | https://feedback.moonbase.sh/p/mailchimp-integration-fails-with-multiple-audiences |
| CompletedMailchimp Integration Fails with Multiple AudiencesI am experiencing an issue connecting Moonbase to Mailchimp. My Mailchimp account has multiple audiences, and the integration fails with a "Multiple audiences found" error. The current integration does not provide an option to select a specific audience, which prevents successful connection.Thioune Philipp 6 days ago🐛Bug Reports | https://feedback.moonbase.sh/p/mailchimp-integration-fails-with-multiple-audiences |
| Start a Trial Flow from Mobile Device - for Instagram or Tiktok marketingI want to use Instagram or Tiktok advertising to encourage people to start a trial of my plugin. This way I can get trial sign-ups, and potentially grow a remarketing list without requiring people to make a purchase directly from the advertisement. The problem is there is no good way to start a trial from a mobile device. The usual trial flow requires getting a download, and then activating the trial from within the app/plugin, all of which has to happen on a desktop device. So I want some flow that I can put on a landing page for mobile advertising that does not require a desktop download. One alternative would be to ask a customer to start a new account, and for them to remember that they wanted a trial of a given product when they open the email later on a desktop (if they even do this). This will be quite obscure and unlikely to be successful, since even if they create a new account on the mobile advertising landing page, it will not link directly to the product for the advertisement they responded to. Another alternative is to request an email address and send them a special email to start a trial of the product. The only way to do this right now would be with the third party mailing list service. I understand Moonbase may add this possibility with the Email Campaigns feature in development. However there is currently already an way to create a new license for a product in the management app, which sends a specific email to the customer to collect a license of a product. Theoretically I could have a duplicated product just for the trials with bundling to cross-grade to a full license of the same app with a purchasable product (if this makes sense). Or maybe [here’s the feature request] there could be a way to send a trial flow starter email via an API in a similar way to this. Then I could put that flow into a landing page for my mobile marketing campaign, and the email the customer receives would encourage them to complete the rest of the flow. As it is, I either need to build a mobile flow myself using third party email marketing services, or just send email marketing directly to purchase pages instead. I’m concerned this may have less success than encouraging a trial only. I hope you can help support mobile marketing strategies other than purchase only. Best regards, NickNick 16 days ago💡Feature Request | https://feedback.moonbase.sh/p/start-a-trial-flow-from-mobile-device-for-instagram-or |
| Start a Trial Flow from Mobile Device - for Instagram or Tiktok marketingI want to use Instagram or Tiktok advertising to encourage people to start a trial of my plugin. This way I can get trial sign-ups, and potentially grow a remarketing list without requiring people to make a purchase directly from the advertisement. The problem is there is no good way to start a trial from a mobile device. The usual trial flow requires getting a download, and then activating the trial from within the app/plugin, all of which has to happen on a desktop device. So I want some flow that I can put on a landing page for mobile advertising that does not require a desktop download. One alternative would be to ask a customer to start a new account, and for them to remember that they wanted a trial of a given product when they open the email later on a desktop (if they even do this). This will be quite obscure and unlikely to be successful, since even if they create a new account on the mobile advertising landing page, it will not link directly to the product for the advertisement they responded to. Another alternative is to request an email address and send them a special email to start a trial of the product. The only way to do this right now would be with the third party mailing list service. I understand Moonbase may add this possibility with the Email Campaigns feature in development. However there is currently already an way to create a new license for a product in the management app, which sends a specific email to the customer to collect a license of a product. Theoretically I could have a duplicated product just for the trials with bundling to cross-grade to a full license of the same app with a purchasable product (if this makes sense). Or maybe [here’s the feature request] there could be a way to send a trial flow starter email via an API in a similar way to this. Then I could put that flow into a landing page for my mobile marketing campaign, and the email the customer receives would encourage them to complete the rest of the flow. As it is, I either need to build a mobile flow myself using third party email marketing services, or just send email marketing directly to purchase pages instead. I’m concerned this may have less success than encouraging a trial only. I hope you can help support mobile marketing strategies other than purchase only. Best regards, NickNick 16 days ago💡Feature Request | https://feedback.moonbase.sh/p/start-a-trial-flow-from-mobile-device-for-instagram-or |
| search in feedback doesn't work how I would expectIf I search for a term that doesn’t exist in any feedback posts, I would expect no posts to be returned. I expect exact term search in this case. Instead I seem to get every post back so I don’t know what’s relevant or not. If I search for a term that is in a post title, then I can see that term is highlighted in the results, so that is useful, but I still get a lot more results and I don’t know if the term is somewhere in the body of the post that I can’t see. This makes it difficult to know whether my feedback has already been provided by someone else, so I’m more likely to just make a new post. In time this might lead to a deeper backlog for you than there should be, since some posts might largely duplicate each other. This is feedback, but also a feature request to improve the search in feedback.Nick 16 days ago📥Feedback | https://feedback.moonbase.sh/p/search-in-feedback-doesnt-work-how-i-would-expect |
| search in feedback doesn't work how I would expectIf I search for a term that doesn’t exist in any feedback posts, I would expect no posts to be returned. I expect exact term search in this case. Instead I seem to get every post back so I don’t know what’s relevant or not. If I search for a term that is in a post title, then I can see that term is highlighted in the results, so that is useful, but I still get a lot more results and I don’t know if the term is somewhere in the body of the post that I can’t see. This makes it difficult to know whether my feedback has already been provided by someone else, so I’m more likely to just make a new post. In time this might lead to a deeper backlog for you than there should be, since some posts might largely duplicate each other. This is feedback, but also a feature request to improve the search in feedback.Nick 16 days ago📥Feedback | https://feedback.moonbase.sh/p/search-in-feedback-doesnt-work-how-i-would-expect |
| Reduce friction on Checkout flow by requiring address only after selecting payment typeI’m concerned that for some customers, requiring a billing address at the first page of the check-out flow might cause them to bounce. I think for ecommerce for software, many people are used to checking out via Paypal or Google/Apple Pay where they don’t need to provide an address directly to a new unknown, boutique vendor. I.e. to feel like they remain more anonymous with less data being provided. I don’t know legal requirements or what the payment APIs provide/require, but I’m pretty sure many checkout flows online don’t require explicitly entering a new address unless selecting credit card as payment type. So my request is could you please investigate this and consider whether you can move address collection to after choosing payment type. Then for online, email-based, pre-verified payment services, people can feel like they have not had to share information. I think the competition here is plugin vendors using checkouts like those from Shopify where friction like entering an address for each new vendor is not necessary.Nick 16 days ago💡Feature Request | https://feedback.moonbase.sh/p/reduce-friction-on-checkout-flow-by-requiring-address-only-after |
| Reduce friction on Checkout flow by requiring address only after selecting payment typeI’m concerned that for some customers, requiring a billing address at the first page of the check-out flow might cause them to bounce. I think for ecommerce for software, many people are used to checking out via Paypal or Google/Apple Pay where they don’t need to provide an address directly to a new unknown, boutique vendor. I.e. to feel like they remain more anonymous with less data being provided. I don’t know legal requirements or what the payment APIs provide/require, but I’m pretty sure many checkout flows online don’t require explicitly entering a new address unless selecting credit card as payment type. So my request is could you please investigate this and consider whether you can move address collection to after choosing payment type. Then for online, email-based, pre-verified payment services, people can feel like they have not had to share information. I think the competition here is plugin vendors using checkouts like those from Shopify where friction like entering an address for each new vendor is not necessary.Nick 16 days ago💡Feature Request | https://feedback.moonbase.sh/p/reduce-friction-on-checkout-flow-by-requiring-address-only-after |
| Social logins for customersWe should allow customers to sign up and log in with social accounts like Google, Facebook, etc. This should streamline anonymous sign-ups.Tobias Lønnerød Madsen 19 days ago2💡Feature Request | https://feedback.moonbase.sh/p/social-logins-for-customers |
| Social logins for customersWe should allow customers to sign up and log in with social accounts like Google, Facebook, etc. This should streamline anonymous sign-ups.Tobias Lønnerød Madsen 19 days ago2💡Feature Request | https://feedback.moonbase.sh/p/social-logins-for-customers |
| Request for dedicated notes and attachments section on customer profilesWe need a dedicated section on customer profiles specifically for adding notes and attachments. This would be incredibly useful for logging all client communications, such as follow-up emails, directly on their profile. While custom metadata can store text, it's not intuitive for this purpose and doesn't support attaching files, making it difficult to keep a complete communication history.Rai Fan 21 days ago💡Feature Request | https://feedback.moonbase.sh/p/request-for-dedicated-notes-and-attachments-section-on-customer-profiles |
| Request for dedicated notes and attachments section on customer profilesWe need a dedicated section on customer profiles specifically for adding notes and attachments. This would be incredibly useful for logging all client communications, such as follow-up emails, directly on their profile. While custom metadata can store text, it's not intuitive for this purpose and doesn't support attaching files, making it difficult to keep a complete communication history.Rai Fan 21 days ago💡Feature Request | https://feedback.moonbase.sh/p/request-for-dedicated-notes-and-attachments-section-on-customer-profiles |
| Allow breaking down analytics by properties on customers and licensesThe licensing analytics already support breaking down by custom metadata from the licensing client, but we want to also break down by parameters set on customers, licenses, trials and more. This way, we can segment analytics by our custom properties easily.Christian Haase 26 days ago💡Feature Request | https://feedback.moonbase.sh/p/allow-breaking-down-analytics-by-properties-on-customers-and-licenses |
| Allow breaking down analytics by properties on customers and licensesThe licensing analytics already support breaking down by custom metadata from the licensing client, but we want to also break down by parameters set on customers, licenses, trials and more. This way, we can segment analytics by our custom properties easily.Christian Haase 26 days ago💡Feature Request | https://feedback.moonbase.sh/p/allow-breaking-down-analytics-by-properties-on-customers-and-licenses |
| Customer support systemThe one thing almost all Moonbase merchants have in addition to Moonbase is a ticketing system for handling customer support cases. If we could build a simple system within Moonbase, exposed in the embedded storefront and connected to customer accounts, it would alleviate and simplify the common setups merchants have. If you have specific thoughts and ideas around this, please share!Tobias Lønnerød Madsen 27 days ago💡Feature Request | https://feedback.moonbase.sh/p/customer-support-system |
| Customer support systemThe one thing almost all Moonbase merchants have in addition to Moonbase is a ticketing system for handling customer support cases. If we could build a simple system within Moonbase, exposed in the embedded storefront and connected to customer accounts, it would alleviate and simplify the common setups merchants have. If you have specific thoughts and ideas around this, please share!Tobias Lønnerød Madsen 27 days ago💡Feature Request | https://feedback.moonbase.sh/p/customer-support-system |
| Admin/Merchant user rolesWe want to be able to have different kinds of users on merchant accounts, restricting their actions and visibility. Typically for scenarios like: Marketing users who need access to marketing tools and analytics Financial users who need access to payouts and invoices Support users who need access to customer and license dataTobias Lønnerød Madsen about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/adminmerchant-user-roles |
| Admin/Merchant user rolesWe want to be able to have different kinds of users on merchant accounts, restricting their actions and visibility. Typically for scenarios like: Marketing users who need access to marketing tools and analytics Financial users who need access to payouts and invoices Support users who need access to customer and license dataTobias Lønnerød Madsen about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/adminmerchant-user-roles |
| CompletedRecoupable Expenses for Revenue Share AgreementsCreators and labels often enter into revenue share agreements where one party covers upfront costs (e.g., music video production, photography, marketing, artwork, or other project expenses). Currently, revenue shares are distributed immediately according to the agreed split, making it difficult to recover those initial investments before payouts begin. Proposed Solution: Allow users to attach one or more recoupable expenses to a revenue share agreement. Revenue generated from the sales would first be applied toward recovering these costs before any payouts are distributed according to the agreed revenue split. Once the recoupable balance has been fully recovered, distributions would automatically revert to the standard revenue share percentages, with all parties able to track the remaining recoupable balance and recoupment progress.Tobias Lønnerød Madsen about 1 month ago1💡Feature Request | https://feedback.moonbase.sh/p/recoupable-expenses-for-revenue-share-agreements |
| CompletedRecoupable Expenses for Revenue Share AgreementsCreators and labels often enter into revenue share agreements where one party covers upfront costs (e.g., music video production, photography, marketing, artwork, or other project expenses). Currently, revenue shares are distributed immediately according to the agreed split, making it difficult to recover those initial investments before payouts begin. Proposed Solution: Allow users to attach one or more recoupable expenses to a revenue share agreement. Revenue generated from the sales would first be applied toward recovering these costs before any payouts are distributed according to the agreed revenue split. Once the recoupable balance has been fully recovered, distributions would automatically revert to the standard revenue share percentages, with all parties able to track the remaining recoupable balance and recoupment progress.Tobias Lønnerød Madsen about 1 month ago1💡Feature Request | https://feedback.moonbase.sh/p/recoupable-expenses-for-revenue-share-agreements |
| Referrer information for downloadsWould be nice if referrer information was also available for downloads, not just purchasesJussi Viiri about 1 month ago1💡Feature Request | https://feedback.moonbase.sh/p/referrer-information-for-downloads |
| Referrer information for downloadsWould be nice if referrer information was also available for downloads, not just purchasesJussi Viiri about 1 month ago1💡Feature Request | https://feedback.moonbase.sh/p/referrer-information-for-downloads |
| IntegrationBrevo integration for automations. Currently we can not set up automated emails because of this.Sabol Hill about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/integration |
| IntegrationBrevo integration for automations. Currently we can not set up automated emails because of this.Sabol Hill about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/integration |
| Allow payouts to currency accountsWould be great to allow paying out each holding currency separately to avoid conversion fees on receipt.Benjamin D'urso about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/allow-payouts-to-currency-accounts |
| Allow payouts to currency accountsWould be great to allow paying out each holding currency separately to avoid conversion fees on receipt.Benjamin D'urso about 1 month ago💡Feature Request | https://feedback.moonbase.sh/p/allow-payouts-to-currency-accounts |
| ⚡ Powered by Featurebase | https://featurebase.app/?utm_campaign=moonbase&utm_content=feedback-board&utm_medium=referral&utm_source=powered-by&utm_id=695b9a10c803dc1f3bd85a76 |
Viewport: width=device-width, initial-scale=1.0