Attribution Setup Checklist
Check app setup, provider configuration, event settings, and testing steps for attribution integrations
Use this checklist alongside the provider setup page when configuring or testing an attribution integration. For the conceptual walkthrough behind these checks, see Getting Started with Attribution Integrations.
Install and initialize the provider SDK
- Provider SDK is installed and initialized if the provider requires one.
- RevenueCat SDK is configured before purchases and before collecting provider identifiers or attribution data.
Connect your app to RevenueCat
- Required device identifiers, provider identifiers, or attribution data are sent to RevenueCat from your app.
- Required RevenueCat customer attributes are present before the test purchase.
- Advertising identifiers are re-collected after consent changes when applicable.
- Reserved campaign fields are only set after final attribution values are available.
Configure provider communication
Many event-forwarding providers use this core subscription lifecycle set:
| Event | Sent when |
|---|---|
| Initial purchase | A user makes their first paid purchase of a subscription |
| Trial started | A user starts a free trial |
| Trial converted | A trial converts to a paid subscription |
| Trial cancelled | A user cancels before their trial converts |
| Renewal | A paid subscription renews |
| Cancellation | A user turns off auto-renew for their paid subscription |
- RevenueCat integration is enabled for the correct project.
- Production credentials, app tokens, event tokens, API keys, dataset IDs, or other required provider settings are configured.
- Sandbox credentials or authentication requirements are configured, or sandbox delivery is intentionally skipped.
- Sales Reporting mode is selected to match the financial reports where the provider data will be used.
- Required event names or tokens are configured or automatically mapped by the provider.
- Optional event types are configured for all events you want to send.
- Provider SDK purchase or revenue tracking is turned off or deduplicated when RevenueCat is sending the same events server-to-server.
Test before comparing dashboards
- Test purchase uses a new customer created after the app and dashboard setup are complete.
- Customer Profile shows the required identifiers or attribution data.
- Customer History shows the expected provider delivery row.
- Provider-side sandbox, debug, or reporting tools are checked after expected reporting delays.
Was this page helpful?