Skip to main content
About Dependencies and Package NamesFlashduty Android SDK is fully compatible with the Datadog open-source protocol. In build.gradle, use cloud.flashcat group for dependencies, but in Kotlin/Java code, import classes from the com.datadog.android package. You can seamlessly leverage Datadog ecosystem documentation, examples, and best practices while enjoying Flashduty platform services.
Flashduty Android RUM SDK provides rich advanced configuration options to help you customize data collection and context information based on business needs.
Supported Configuration Scenarios:
  • Enrich user sessions - Add custom views, actions, resources, and error information
  • Protect sensitive data - Mask personally identifiable information and sensitive data
  • Associate user sessions - Link user sessions with internal user identifiers
  • Control data volume - Optimize data collection through sampling and event filtering
  • Enhance context - Add custom attributes to data

Enrich User Sessions

Custom Views

When using ActivityViewTrackingStrategy or FragmentViewTrackingStrategy, the RUM SDK automatically tracks views. You can also manually send custom RUM views when a view becomes visible or interactive.
Parameter Description:
  • viewKey (String) - Unique identifier for the view, same viewKey used for startView() and stopView()
  • viewName (String) - Name of the view
  • attributes (Map<String, Any?>) - Attributes attached to the view (optional)

Custom Actions

In addition to auto-tracked user interactions, you can track specific custom user actions (like clicks, swipes, likes).

Custom Resources

In addition to auto-tracked resources, you can manually track specific custom resources (like network requests, third-party library loading).

Custom Errors

To record specific errors, notify the RUM SDK when an exception occurs:
For more error reporting details, see Android Error Reporting.

Custom Timing

In addition to RUM SDK’s default performance metrics, you can use the addTiming API to measure the duration of key operations. Timing is an offset relative to the current RUM view start time.
After setting timing, access it via @view.custom_timings.<timing_name>, e.g., @view.custom_timings.hero_image.

Set User Information

The RUM SDK supports standard user information.
Only standard user fields are supported: id, name, email, and anonymous_id. Other user attributes are not supported. If needed, configure them under context.

Event and Data Management

Clear All Data

Use clearAllData to clear all unsent data currently stored in the SDK:

Sampling

You can control the percentage of sessions that collect RUM data:
Sampled-out sessions will not collect any page views or related telemetry data.
To comply with privacy regulations like GDPR and CCPA, you can set user tracking consent state:

Global Context

Add global context attributes that will be attached to all RUM events:

Event Mappers

Use Event Mappers to modify or filter events before they are sent:
View events cannot be discarded (returning null has no effect).

SDK Integration

Learn how to quickly integrate the RUM SDK

Data Collection

Learn about data types and attributes collected by the SDK

Compatibility

Learn about SDK compatibility requirements