Tracking Events

Singular can collect data about in-app events to help analyze the performance of your campaigns and measure KPIs. For example, your organization may want to collect data about user logins, registrations, tutorial completions, or leveling up in a gaming app.

Singular supports a variety of standard events. These commonly used events are often supported by ad networks for reporting and optimization. Another advantage is that when you use standard event names, Singular recognizes them automatically and adds them to the Events list without you having to define them manually. We recommend using standard events whenever possible.

The list of events sent to Singular (with the accompanying attributes) should be compiled by the UA/marketing/business team based on your organization's marketing KPIs. The business team can follow the guide at How to Track In-App Events: Guide For Singular Attribution Customers.

With each event you track, you can pass various attributes. See the recommended standard attributes per event.

In your code, send events to Singular using the event or eventWithArgs methods.

/* Send the Standard Event Login */
Singular.event(sngLogin);

/* Send the Standard Event Content View with the recommended attributes */
Singular.eventWithArgs(sngContentView, { 
  sngAttrContentType: 'PrivacyController',
  sngAttrContentId: '130',
  sngAttrContent: 'GDPR Opt-Out Options'
});

Tracking Revenue

Singular can collect data about revenue gained through the app to help analyze the performance and ROI of your campaigns. Singular will make the data available to you in reports, log export, and postbacks.

When reporting revenue events to Singular, we recommend passing the purchase object as returned from Android's or iOS's In-App Purchase (IAP) process. This way, Singular gets all the details of the transaction, which enriches your Singular reports with data. In addition, Singular gets the transaction receipt from Google which can be used to validate the transaction in the context of fighting in-app fraud.

Passing the Purchase Object in React Native

// Add the Singular Purchase classes imports
import {
 Singular,
 SingularConfig,
 SingularIOSPurchase,
 SingularAndroidPurchase,
} from 'singular-react-native';

let singularPurchase = null;

if (Platform.OS === 'ios') {
 singularPurchase = new SingularIOSPurchase(
   product.revenue,
   product.currency,
   purchase.productId,
   purchase.transactionId,
   purchase.transactionReceipt,
 );
} else if (Platform.OS === 'android'){
 singularPurchase = new SingularAndroidPurchase(
   product.revenue,
   product.currency,
   purchase.transactionReceipt,
   purchase.signatureAndroid,
 );
}

Singular.inAppPurchase('report iap', singularPurchase);

Passing the Purchase Object Using Native Code

iOS

// report the transaction details to Singular
[Singular iapComplete:transaction];

// report the transaction details to Singular with a custom name
[Singular iapComplete:transaction withName:@"MyCustomRevenue"];

Android

To take advantage of Android's IAP functionality, first add the following to your app's build.gradle file:

implementation 'com.singular.sdk:singular_sdk:9.+

Singular.revenue("USD", 5.50, purchase);

Singular.customRevenue("MyCustomRevenue", 
    "USD", 5.50, purchase);

Reporting Revenue Events without the Purchase Object

While we strongly recommend reporting revenue events the way described above, you can also send revenue events to Singular just by passing the currency and transaction amount. Note that this way, Singular does not get the purchase receipt and cannot validate the transaction.

Singular.revenue("USD", 5.50);

Singular.customRevenue("MyCustomRevenue", "USD", 5.50);