The Mobile SDK

Ayesha Akhtar
Ayesha Akhtar
  • Updated

Feature Snapshot

Summary:
The Mobile SDK is a dedicated Software Development Kit designed for integrating consent capture into mobile applications. It enables apps to generate certified leads by recording an audit trail of user interactions such as taps, keystrokes, and screenshots, all stored in a unique certificate URL.


Mobile certificates include:

  • Screenshots at key moments
    Screenshots allow you to document important points in the consent flow, including form submission and other required steps.


  • Event Log
    A textual representation of the actions the lead took is shown in the Event Log. This helps reconstruct what happened at each moment.


  • Metadata about When, Where, and Who
    Mobile certificates provide deeper insight into the timing, context, and user identity associated with the lead event.


  • High-value transparency
    These certificates provide a verifiable record of:

    • Consumer behavior
    • Key consent actions
    • App context surrounding the lead event

This makes them highly effective for compliance, QA, and auditing requirements.

Typical Use Cases:

  • Integrating consent documentation into mobile lead forms
  • Capturing and retaining consumer consent for compliance in mobile applications
  • Enhancing lead verification and audit trails for regulated industries

How the TrustedForm Certify Mobile SDK works

When integrated into your mobile application, the Mobile SDK functions similarly to its web counterpart but is optimized for mobile conditions. It embeds a lightweight consent widget into your lead form, monitors user interactions in real time, and records key events—such as taps, keystrokes, and screenshots. Upon form submission, it automatically generates a unique certificate URL that encapsulates the entire consent event trail, including timestamps and metadata.

Step‑by‑Step Instructions

  1. Integrate the SDK:
    Add the Mobile SDK library to your mobile app project using your standard dependency management system.

  2. Configure the SDK:
    Follow the TrustedForm configuration guidelines to set necessary parameters (e.g., field names for certificate URL and metadata).

  3. Embed the Consent Widget:
    Insert the provided widget into the mobile form interface at the point where consumers enter their details.

  4. Capture Consumer Interactions:
    Allow the SDK to monitor and record real-time actions—including taps, keystrokes, and screenshots—as users interact with the form.

  5. Generate and Transmit Certificate:
    Upon lead submission, the SDK automatically creates a unique certificate URL containing the full audit trail and attaches it to the lead data for secure transmission.

Expected Result:
After a lead is submitted, your mobile application will generate a TrustedForm Certificate URL that encapsulates a complete audit trail of user interactions. This URL is then transmitted along with the lead data, ensuring proof of consent is available for compliance and verification.


Validation & Monitoring (optional)

  • Test the Integration: Verify the certificate URL is generated by submitting test leads across different mobile devices and network conditions.
  • Where to Monitor?: Review the certificate details on your TrustedForm dashboard (recently issued certificates) to confirm that event data, including screenshots and metadata, have been accurately captured.

Best Practices

  • Integrate the SDK early in your mobile app’s workflow to ensure all user interactions are captured
  • Regularly test the integration on various devices and network environments to maintain data integrity
  • Securely transmit and store the generated certificate URL alongside other lead information
  • Periodically review retained certificates to validate compliance and improve lead quality

Troubleshooting

Symptom / Error Likely Cause Resolution
Certificate URL not generated SDK not properly integrated or misconfigured Revisit integration steps and verify SDK configuration settings
Incomplete event data (e.g., missing screenshots) Unstable network connection or performance issues on mobile Test under stable network conditions and optimize device performance
Certificate URL missing in lead payload Incorrect field mapping during SDK setup Confirm that the mobile form’s field names match the SDK configuration

Frequently Asked Questions (FAQ)

Q: What is the Mobile SDK?
A: The Mobile SDK is a software toolkit designed to capture consumer interactions on mobile lead forms and generate a verifiable certificate URL that documents consent.

Q: Why is the Mobile SDK important?
A: It is crucial for regulatory compliance as it provides a secure, detailed audit trail of user interactions, ensuring that consent is both captured and documented transparently.

Q: Is the Mobile SDK available for all customers?
A: No. The Mobile SDK is currently in beta and not accepting new testers.

Q: How do I join the beta program?
A: Contact your ActiveProspect representative to request placement on the waitlist.

Q: Does the mobile certificate include session replays like the Web SDK?
A: No. Mobile certificates include screenshots and event logs, but not full HTML-based session replays.


Glossary

Term Definition
Mobile SDK A toolkit for integrating consent capture into mobile applications, generating certified leads.
Certificate URL A unique URL generated by the SDK that contains an audit trail of user interactions and consent data.
Consent Documentation The process of securely capturing and storing proof of a user’s explicit agreement to be contacted.
Audit Trail A detailed recording of user interactions—such as events, screenshots, and metadata—that verify consent.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.