Advanced Options
Optional and advanced configuration for the Singular Cordova SDK. These settings are not required for a standard integration.
BETA Features
Not generally available: The features in this section are in BETA. Singular must enable them for your account before they will work, and their behavior may change. Talk to your Customer Success Manager before building against them.
Attribution Callback
The Attribution Callback delivers Singular's attribution result for the install — such as the network and campaign that drove it — to your app on the device, during the user's first session after install.
Enablement is required: This feature is off by default. If it has not been enabled for your account, the callback never fires, even when your code is correct. Contact your Customer Success Manager to request it.
Setting it up
- Ask your Customer Success Manager to enable the Attribution Callback for your account.
- Register your handler on the SDK configuration object before initializing the SDK. For the signature and a code sample, see
deviceAttributionCallbackHandler. - Test on a device that has not opened the app before. The callback fires only on a first session.
What to expect
- First session only: The callback fires once, during the first session after install. It is not called on later app opens.
- Organic is a result, not a failure: When no touchpoint is found, the callback still fires and reports the network as "Organic". If the callback does not fire at all, the cause is a setup problem rather than an attribution one.
- A best guess, not the final attribution: The result reflects the last touchpoint available at the moment the session is processed. It will not always match the attribution shown in Singular's reports, which is decided later with more information.