RevenueCat

Documentation Index

Fetch the complete documentation index at: https://docs.datalyr.com/llms.txt

Use this file to discover all available pages before exploring further.

​

What Gets Tracked

​

Webhook Events (RevenueCat to DATALYR)

​

Attribution Data (DATALYR to RevenueCat)

​

Setup

​

1. Connect RevenueCat in DATALYR

1. Go to Settings -> Integrations in DATALYR
2. Click “Connect” next to RevenueCat
3. Enter your RevenueCat Project ID
4. Copy the generated webhook URL

​

2. Configure Webhook in RevenueCat

1. Go to your RevenueCat Dashboard -> Project Settings -> Integrations
2. Select “Webhooks”
3. Add a new webhook URL
4. Paste the DATALYR webhook URL
5. Under “Events to send”, select all event types
6. Save

​

3. Push Attribution to RevenueCat (Mobile SDK)

import { Datalyr } from '@datalyr/react-native';
import Purchases from 'react-native-purchases';

// After DATALYR SDK is initialized and user has been identified
const attrs = Datalyr.getRevenueCatAttributes();
Purchases.setAttributes(attrs);

import DatalyrSDK
import RevenueCat

// After DATALYR SDK is initialized and user has been identified
let attrs = DatalyrSDK.shared.getRevenueCatAttributes()
Purchases.shared.attribution.setAttributes(attrs)

​

How Attribution Works

​

Attribution Flow

User clicks a Google ad
DATALYR web SDK captures: gclid, utm_source=google, utm_medium=cpc
Stores in visitor profile

User installs your app
DATALYR mobile SDK initializes
Attribution data captured via web-to-app matching

Your app calls:
const attrs = Datalyr.getRevenueCatAttributes();
Purchases.setAttributes(attrs);

This passes $datalyrId (visitor ID) and attribution data to RevenueCat

User signs up with email: [email protected]

Your app calls:
Datalyr.identify('user_456', { email: '[email protected]' });

RevenueCat subscriber attribute set:
Purchases.setAttributes({ $email: '[email protected]' });

DATALYR links the mobile visitor to the original web visitor

User purchases subscription through RevenueCat paywall
RevenueCat sends webhook to DATALYR
Webhook includes subscriber_attributes with $datalyrId and $email

DATALYR receives the webhook
Looks up visitor by $datalyrId from subscriber_attributes (fastest, most accurate)
Falls back to email lookup if $datalyrId not found
Finds match with gclid from Step 1
Links subscription_started event to the Google ad click

DATALYR sends conversion to Google Ads API
Includes: gclid, conversion_action, value=$9.99
Google attributes the conversion to the original ad

​

Identity Resolution Order

1. Visitor ID lookup — Checks subscriber_attributes.$datalyrId (set automatically by getRevenueCatAttributes()). This is the most accurate method because it directly matches the DATALYR visitor.
2. Email lookup — Searches subscriber_attributes.$email (also checks email, Email, $Email) against identified visitors
3. Aliases lookup — Iterates through the aliases array in the webhook payload, skipping RevenueCat anonymous IDs (those starting with $RCAnonymousID:), and searches each alias as a user ID

​

Requirements for Attribution

• The user must have been tracked by the DATALYR web or mobile SDK before the subscription event
• For best results, call getRevenueCatAttributes() and pass the result to Purchases.setAttributes() — this ensures the $datalyrId is available for direct visitor matching
• Alternatively, the user must have been identified with an email that matches the $email subscriber attribute in RevenueCat
• The subscription event must be within the attribution window (default 30 days)

​

Conversion Postbacks

​

How Postbacks Work

1. RevenueCat sends a webhook (e.g., INITIAL_PURCHASE)
2. DATALYR maps it to the appropriate event (subscription_started, trial_started, trial_converted, or subscription_renewed)
3. DATALYR resolves the user’s attribution (fbclid, gclid, ttclid)
4. If a conversion rule matches the event, DATALYR sends a postback:
   • Meta: Conversions API (CAPI) with fbclid, fbp, fbc
   • Google: Google Ads Conversion API with gclid
   • TikTok: TikTok Events API with ttclid

​

Supported Platforms

​

Setting Up Postbacks

1. Go to Settings -> Connections in DATALYR
2. Connect your ad platform (Meta, Google, or TikTok)
3. Create conversion rules for the events you want to track:
   • trial_started → Meta StartTrial / TikTok StartTrial (optimizes for trial signups)
   • trial_converted → Meta Purchase / TikTok CompletePayment (optimizes for trial-to-paid)
   • subscription_started → Meta Subscribe / TikTok Subscribe (direct paid subscriptions)
   • subscription_renewed → Meta Purchase / TikTok CompletePayment (recurring revenue)

​

Revenue Tracking

​

Gross Revenue

​

Net Revenue

net_revenue = price * (1 - tax_percentage) * (1 - commission_percentage)

​

Commission Rates

​

Trials

• trial_started — Fires when a user begins a free trial (period_type=TRIAL). Value is $0.
• trial_converted — Fires when a trial user is charged for the first time (is_trial_conversion=true). Value is the subscription price.
• subscription_started — Fires only for direct paid subscriptions (no trial period).

​

Refund Reversals

​

Store Platforms

​

Event Data

• subscription_id — Original transaction ID
• product_id — RevenueCat product identifier
• platform — Store name (APP_STORE, PLAY_STORE, etc.)
• platform_type — Normalized platform (ios, android, web, macos, amazon, roku)
• app_id — RevenueCat app ID
• period_type — Subscription period (NORMAL, TRIAL, INTRO, PROMOTIONAL)
• gross_revenue — Full price in USD
• net_revenue — After commission and tax
• commission_rate — Applied commission percentage
• tax_percentage — Applied tax percentage
• is_trial_conversion — Whether this converted from a trial
• experiment_id — RevenueCat Experiments ID (if the user is in an experiment)
• presented_offering_id — RevenueCat offering ID shown to the user (for offering attribution)
• app_user_id — RevenueCat app user ID
• original_app_user_id — Original app user ID
• aliases — Array of all user ID aliases

​

RevenueCat Experiments

​

Deduplication

​

Troubleshooting

​

Webhook Events Not Appearing

1. The webhook URL in RevenueCat matches the URL generated in DATALYR Settings -> Integrations
2. Your RevenueCat Project ID is correct in DATALYR
3. All event types are selected in the RevenueCat webhook configuration
4. The webhook is active (not paused) in RevenueCat

• Go to Event Stream in the DATALYR dashboard
• Filter by source: revenuecat
• Check if events appear after a test purchase

• In RevenueCat Dashboard -> Project Settings -> Integrations -> Webhooks
• View recent webhook deliveries and response codes
• A 200 response from DATALYR means the webhook was received

​

Events Not Attributed

1. You are calling getRevenueCatAttributes() and passing the result to Purchases.setAttributes() — this sets the $datalyrId for direct visitor matching
2. If not using getRevenueCatAttributes(), the $email subscriber attribute must be set in RevenueCat for the user
3. The same email was used when calling identify() in the DATALYR SDK
4. The user was tracked by DATALYR before the subscription event
5. The attribution window has not expired (default 30 days)

// After DATALYR SDK is initialized
const attrs = Datalyr.getRevenueCatAttributes();
Purchases.setAttributes(attrs);

// Also identify in DATALYR and set email in RevenueCat
Datalyr.identify(user.id, { email: user.email });
Purchases.setAttributes({ $email: user.email });

​

Postbacks Not Sending

1. A conversion rule exists that matches the DATALYR event name (e.g., trial_started, trial_converted, subscription_started)
2. The ad platform is connected in Settings -> Connections
3. The user has a valid click ID (fbclid, gclid, or ttclid) from their original ad click

​

Revenue Showing Incorrect Values

• Commission rate mismatch: Check the commission_percentage field in the RevenueCat webhook payload against your expected rate
• Tax deductions: DATALYR deducts both tax and commission from net revenue. Check the tax_percentage field on the event
• Currency conversion: RevenueCat converts to USD. The price_in_purchased_currency field shows the original price in the user’s local currency

​

SDK Attributes Not Populating

1. The DATALYR mobile SDK is initialized before calling getRevenueCatAttributes()
2. Attribution data has been resolved (the user visited your site or app via a tracked link)
3. You are passing the result to Purchases.setAttributes() correctly

const attrs = Datalyr.getRevenueCatAttributes();
console.log('RevenueCat attributes:', attrs);
// Should contain keys like $datalyrId, $mediaSource, utm_source, etc.

​

ATT Consent Status Values

​

Next Steps