Offline Forms

Driftrock's Offline Forms capture is designed for physical marketing events such as motor shows, dealership open days, and field activations. It provides a secure webhook endpoint that partner-built offline forms can send lead data to once an internet connection is available, so no leads are lost due to connectivity issues at the event.

What is Offline Forms?

The Offline Forms capture is a specialised webhook endpoint within Driftrock that accepts batched lead data from third-party offline form tools. Partners build the offline form themselves, storing data locally on a device when there is no internet connection, then sending all collected leads to the Driftrock endpoint once connectivity is restored.

Driftrock receives the data, authenticates it using a partner-specific API key, validates all fields, and routes clean leads to your CRM with the same rules and automations as any other capture source.

Why use Offline Forms?

Large-scale events often have unreliable Wi-Fi or cellular coverage. Standard online forms fail in these conditions, risking lost lead data. Offline form tools store submissions locally on the device, but without a structured sync process, getting that data into your CRM quickly and cleanly is a challenge.

Driftrock's Offline Forms capture provides the secure transport layer and validation engine to move data from the partner's system into your CRM at scale, without manual CSV exports or compromises on data quality. Every lead goes through the same validation and routing pipeline as an online submission.

How it works

A partner builds an offline-capable form that stores lead data locally on the event device.

The partner configures their system to send batched submissions to the Driftrock endpoint using the API key and Source ID provided.

Once the device has an internet connection, the partner's system sends the leads to Driftrock.

Driftrock authenticates the request, validates the fields, and processes each lead through the standard pipeline.

Clean leads are delivered to your CRM according to your configured automations and routing rules.

Getting started

Prerequisites: Admin access to your Driftrock account. An Admin or Driftrock Customer Success contact must set up the initial capture, as API key access is required.

Work with your Driftrock Customer Success contact to plan the event setup: agree on lead type, required fields, accepted values, and routing logic.

An Admin creates the initial Webhook Capture in Driftrock and generates a partner-specific API key in Settings, then API Settings.

The Admin sends a manual test lead (for example via Postman) to create the payload structure and make fields visible for mapping.

Share the API key, Source ID, and the Share Documentation link with the partner.

The partner builds the offline form and configures it to POST to the Driftrock endpoint.

Test leads for each use case (for example, test drive request and keep me informed) to confirm all fields are correctly mapped and routed.

For each new offline event, duplicate the existing capture rather than building from scratch — but remember to share the new, unique Source ID with the partner before the event.

Tips for getting the most out of Offline Forms

Each duplicated capture generates a unique Source ID: always share the new Source ID with the partner before the event, or leads from that event will not reach Driftrock. For events with multiple lead types (for example, both test drive requests and general enquiries), create a separate capture per type to keep routing rules and reporting clean.