Get help with webhooks, third-party integrations, and attribution providers.
Recently active
Hi, I have the following questionIn your documentation, under the Subscription Status tab, it clearly states that the subscriptions field is a collection (array) that stores Subscription objects within it. And this response I expect from the REST API. But as far as I noticed, making request to API "subscriptions" is an object that stores fields in itself - so it is not a collection. And this can be seen in the "Rest API endpoints" documentation where in the "Get or Create Subscriber" request the example "subscriptions" is just an object instead of a collection. Could you please clarify this inaccuracy for me? Because when I currently make a request to the API in "sandbox" mode, I also get the subscriptions{...} object instead of the subscriptions[...] array.Thanks in advance.
I've configured an attribution integration but no events are sent?The attribution integrations in RevenueCat (e.g. Appsflyer, Adjust, Branch, Facebook, etc.) require two steps to setup.The network specific attribution data needs to be sent to RevenueCat from within your app. This is done through Subscriber Attributes in the SDK. Refer to the attribution integration guides for the specific network to see which Subscriber Attributes need to be set and how to test this: https://docs.revenuecat.com/docs/attribution The integration needs to be configured in the RevenueCat dashboard for your app.If no events are being sent, you should check that step 1 above is set up properly for your app and the specific attribution network. Integration events will only be sent for users that have these attributes collected.If events are being sent but the data doesn't seem right, check out our post on Data Discrepancies.
When integrations aren't working as expected, debugging can be challenging. This guide is designed to walk you through the steps you should take to identify what could be going wrong, and steps you can take to resolve any issues. Identifying the issueWhen debugging integrations, we usually hear about three categories of issues:No events are being sent from RevenueCat into third-party Only some events are being sent from RevenueCat into third-party All events appear to be sent, but the data in third-party does not match RevenueCatWe'll dig into each of these categories further in the sections below. Check that events are being sentThe first thing to check is if any events are being sent from RevenueCat into the third-party. This is easy to check in the RevenueCat dashboard under the integration settings for your app.Below every integration configuration, you'll see a table of Recent Events (example below). (Tip: click on any event in the table to see the payload that was delivered)If y
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.