With our Singular integration you can:
- Accurately track subscriptions generated from Singular campaigns, allowing you to know precisely how much revenue your campaigns generate.
- Send trial conversions and renewals directly from RevenueCat to Singular, allowing for tracking without an app open.
- Continue to follow your cohorts for months to know the long tail revenue generated by your campaigns.
The Singular integration requires some device-specific data. RevenueCat will only send events into Singular if the below Subscriber Attributes keys have been set for the device.
These properties can be set manually, like any other Subscriber Attributes, or through the helper method
import AdSupport // ... Purchases.configure(withAPIKey: "public_sdk_key") // ... Purchases.shared.collectDeviceIdentifiers()
//.. Purchases.configure(this, "public_sdk_key") //.. Purchases.sharedInstance.collectDeviceIdentifiers()
You should make sure to call
collectDeviceIdentifiers() after the Purchases SDK is configured, and before the first purchase occurs. It's safe to call this multiple times, as only the new/updated values will be sent to RevenueCat.
Device identifiers with iOS App Tracking Transparency (iOS 14.5+)
If you are requesting the App Tracking permission through ATT to access the IDFA, you can call
.collectDeviceIdentifiers()again if the customer accepts the permission to update the
$idfaattribute in RevenueCat.
Import AdSupport Framework (iOS)
The AdSupport framework is required to access the IDFA parameter on iOS. Don't forget to import this into your project.
Remove any client-side purchase tracking
Make sure to remove all client-side tracking of revenue. Since RevenueCat will be sending events for all revenue actions, tracking purchases with the Singular SDK directly can lead to double counting of revenue in Singular.
RevenueCat itself is not an attribution network, and can't determine which specific ad drove an install/conversion. However, if you're able to collect this information from another source, such as Singular, it's possible to attach it to a user in RevenueCat using Subscriber Attributes as well.
The below reserved key names can be used to optionally attach campaign data to a user. This data will then be sent through to other downstream analytics integrations and accessible via APIs and webhooks.
After you've set up the Purchases SDK to send device data to RevenueCat, you can "turn on" the integration and configure the event names from the RevenueCat dashboard.
- Navigate to your app in the RevenueCat dashboard and choose 'Singular' from the integrations menu.
- Add your Singular API key, and an optional sandbox API key. The sandbox API key will be used for any sandbox purchases so you don't have to send them to your production Singular instance.
- Enter the event names that RevenueCat will send or choose the default event names.
- Select whether you want RevenueCat to report proceeds (after app store cut) or revenue (gross sales).
You can test the Singular integration end-to-end before going live. It's recommended that you test the integration is working properly for new users, and any existing users that may update their app to a new version.
Before you test the integration, make sure you have a Singular API key set in the "Sandbox API key" field in RevenueCat. This is required if you want the integration to trigger for sandbox purchases.
Simulate a new user installing your app, and go through your app flow to complete a sandbox purchase.
Navigate the the Customer View for the test user that just made a purchase. Make sure that all of the required data from step 1 above is listed as attributes for the user.
While still on the Customer View, click into the test purchase event in the Customer History and make sure that the Singular integration event exists and was delivered successfully.
You've done it!
You should start seeing events from RevenueCat appear in Singular
Updated about a month ago