Dashboard & Tools

Hi there - I know that some of the charts features are still Beta. But we put a lot of work into a exit paywall cascade and right now I can’t even see if people vsiting the paywalls at all.Firebase doesn’t count events. Our devs say that’s just not working for exit paywalls.So I hoped the paywall charts within RC give me numbers. But when I a look at Paywalls where I have firebase data AND rc paywall chart data I see that the numbers of the rc paywall charts (“paywall encounter”) are way off compared to firebase.Like: Firebase says 90 visits and RC paywall chart says 3.So if numbers that I can doublecheck with a second source are way off I don’t have much trust in the rc numbers for the exit paywalls, for which I don’t have a second source.I just wanted to know: Is that a common issue? Are others experiencing the same: firebase data and rc paywall charts not matching at all?Thanks a lot for any responses. So I can try to figure out if there is a solution for this issue.

Hello,I have a problem with the Retention Message API. The default message is not displayed to users when they try to cancel their subscription in the device's Settings app.The request to use this API was approved by Apple for our account. After configuring it for the Sandbox environment, everything worked as expected the image and text were displayed to users.Later, I applied the same configuration to the Production environment. I received the Approved status for the message, but after purchasing the subscription from the App Store, although I can see the subscription in Settings, the retention message is not displayed when I attempt to cancel it.I have tried different Apple accounts from different regions (both EU and non-EU) and tested from physical locations without using a VPN.Also, for clarification, we do not use real-time communication only the default retention message. For additional information:I also tried configuring this message from App Store Connect, as shown in WWDC 20

## TL;DROne of the **product-store-state** MCP tools served from `https://mcp.revenuecat.ai/mcp` has a JSON Schemacontaining an integer literal that exceeds the signed 64-bit range (most likely a `maximum` / `default` /`multipleOf` on a price/amount/timestamp field). When an MCP client forwards that tool definition to theAnthropic Messages API, the API rejects the **entire** `tools` array with:    API Error: 400 tools.61.custom.input_schema: int too big to convertBecause the failure happens at tool-definition validation time, *every* request that includes that toolfails — so the tools can't be loaded at all, which blocks any workflow that uses them (e.g. creating /submitting products to App Store Connect through the MCP).This is a different bug from the earlier `create-webhook-integration` null-in-string-enum issue(community tid=7623, fixed 2026-04-28) — same class of problem (an illegal schema value served by the MCP),different tool and field.## Affected toolsThe error appears while l

Hi team,Great work on shipping the new charts for Paywalls 🚀For macOS we use RevenueCat paywalls, but can only see macOS data for chart type “Paywall Encounter”, not Paywall Conversion, Paywall LTV, or Paywall Abandonment.Questions:Is there a timeline for these chart types support macOS? If so, will these charts provide historical data for SDK 5.51.1+ users once they are functional? 

This is a feature request for Rico.When a user starts a new chat, they often have to repeat the same app details, such as: What the app does Whether it is premium / subscription / freemium / hard paywall When it launched Basic business info like user acquisition cost It would be helpful to have a place to save this as a system instruction or project context for Rico.Rico could then use this saved context in every new chat for that project, so users do not need to repeat it and the answers can be more accurate.

I have`Purchases.shared.attribution.enableAdServicesAttributionTokenCollection()`which according to https://www.revenuecat.com/docs/integrations/attribution/apple-search-ads should give me the following fields:https://cln.sh/41P1JJ7THowever these are the fields that I see:https://cln.sh/dPCvFb77 I have used ASA Basic in the past, but have been using advanced for months.Is there anything else that I’m missing?

Every paywall I duplicate shows up in the dashboard but not in the RevenueCat mobile app for preview. Then when I go to actually deeplink into the paywall in my app, I get a fallback paywall. When I ask Rico about these duplicated paywalls he doesn’t know they exist (they don’t return in the API).Has anyone had this problem? Is there another way to duplicate easily?

Hi, we’ve encountered an issue where nothing shows up in the Experiment report, as attached below, even though (1) it’s been 2 days since we started the experiment, and (2) we do see that new customers are properly assigned to each respective variants and (3) nearly 5K new customers signed up in our app in the past 2 days. So apparently the experiment is running properly and there’s enough data to display, but there’s an issue with the report? Thank you.   

I use AI editor primarly for paywalls, and i already had this active paywall which contained monthly and yearly plan for individual plan type and i added new packages in the offering for family plan type which are also monthly and yearly but the AI editor can’t see them no matter i do. 

Hi, we’re running an experiment and later realized that we’ve set the wrong primary metric. So I tried editing it, but got his message when I clicked “Save Changes”. I didn’t change anything related to variants, but this error keeps showing up. How do I solve this problem? Thank you.

Hi RevenueCat team,We are seeing what looks like the same offering_id: null experiment issue reported here, but our setup does not use live targeting rules or placements:https://community.revenuecat.com/dashboard-tools-52/why-does-my-experiment-not-override-live-targeting-7732Setup:React Native / Expo app react-native-purchases: 10.3.0 react-native-purchases-ui: 10.3.0 RevenueCat Paywalls via RevenueCatUI.Paywall App fetches Purchases.getOfferings() and renders offerings.current Design experiment Enrollment: New customers Audience: 100% Criteria: Any audience No placements in the experiment No targeting rules imported or active on the experiment Two variant offerings:   - Variant A: PW Basic Weekly + Yearly 2   - Variant B: PW Basic Weekly + YearlyObserved:Customer history shows EXPERIMENT_ENROLLMENT experiment_variant is present offering_id is null The customer profile’s Current Offering still shows the default offering, not an experiment override We know from screen recordings that t