Offline Event Forms

Trade shows, motor shows, test drive events, and showroom activations all generate high-intent leads in environments where internet connectivity can be unreliable. Standard online forms fail in these situations. Offline Event Forms in Driftrock provide a resilient capture solution for physical events: data is collected locally by your event partner's form, then synchronised to Driftrock and your CRM the moment a stable connection is available.

What are Offline Event Forms?

Offline Event Forms use Driftrock's webhook capture infrastructure to ingest lead data collected by an external partner's offline-capable form (tablet apps, kiosk software, custom hardware). Driftrock provides a secure webhook endpoint, an API key for authentication, and a shareable documentation link your partner can use to build their form to the exact specification required.

When connectivity is restored after an event, the partner's system pushes the batched lead data to the Driftrock endpoint. Driftrock validates and processes each lead exactly as it would any other capture, then routes it to your CRM.

Why use Offline Event Forms?

Events generate some of the highest-intent leads in automotive marketing, but they often take place in venues with poor or restricted Wi-Fi. Without a resilient capture solution, leads collected at a motor show or test drive event may be lost, delayed, or arrive in the CRM as unvalidated CSV exports. Offline Event Forms solve this:

No leads lost due to connectivity. Data is stored locally on the event device and pushed to Driftrock only when a reliable connection is available.

The same quality standards as online forms. Driftrock validates, deduplicates, and routes offline event leads through the same pipeline as any other capture, so your CRM receives clean, complete records.

Transparent partner integration. The shareable documentation link gives your event partner the exact field specifications, accepted values, and endpoint details they need to build their form correctly. No ambiguity, no back-and-forth.

Scalable across events. Existing captures can be duplicated for new events, saving setup time.

How it works

Your event partner builds an offline-capable form (tablet or kiosk app) that stores data locally. When the device reconnects to the internet, it sends the collected lead data as a batch to Driftrock's webhook endpoint using a partner-specific API key. Driftrock authenticates the request, validates each lead against your configured rules (required fields, accepted values, deduplication), and routes approved leads to your CRM via the standard automation pipeline.

Leads that fail validation (for example, a missing consent field or an unrecognised vehicle code) are rejected with a specific error code, giving the partner visibility into what needs to be corrected.

Getting started

Setting up an Offline Event Form requires an initial configuration by a Driftrock Admin or your Customer Success Manager, as API access is needed to create the initial capture.

Brief your Driftrock contact on the event details: lead type (test drive request, enquiry, etc.), required fields, accepted values, and the downstream CRM you are routing to.

An Admin creates the Webhook Capture in your Driftrock account.

A partner-specific API key is generated in Settings and API Settings.

Share the API key, Source ID, and documentation link with your event partner. The documentation link shows them exactly what the endpoint expects.

The partner builds and tests their offline form, sending test leads to Driftrock for verification.

Once testing passes, the capture is live and ready for the event.

For subsequent events, an existing capture can be duplicated. Make sure to share the new, unique Source ID from the duplicate with your partner for each new event.

Tips for getting the most out of Offline Event Forms

Run a full test before every event, not just on initial setup. Send test leads covering each lead type and value combination you expect, and verify they arrive correctly in both Driftrock and your CRM before the event day.

If the partner reports a 401 Unauthorized error, the API key is incorrect or expired. Generate a fresh key in Settings and API Settings and share it with them. If they report a 422 error, a required field is missing from their form submission, usually a consent flag or a vehicle code.

When duplicating a capture for a new event, always retrieve the new Source ID from the duplicated capture before sharing credentials with your partner. Each capture has a unique Source ID, and using the wrong one will cause leads to land in the wrong capture.