Offline Conversions

Offline Conversions allow you to send conversion events (such as a "Lead" or "Purchase") that happen outside the immediate browser session directly to advertising platforms, like Facebook CAPI or Google Ads. This is perfect for businesses that track final sales or status changes in a CRM system.

Offline conversions require an active Grow or Business plan. Check our pricing page for volume limits and plan details.

Send events that occur days or weeks after the initial form submission. Whether a lead converts to a sale over the phone, in an email thread, or in your physical store, you can still attribute that success back to your digital ad campaigns.

Moving tracking offline does not bypass privacy directives like GDPR or ePrivacy. Our platform automatically manages user consent to ensure compliance. The system requires explicit user consent captured at the exact time of the form submission:

• ad_storage: must be granted for a submission to be eligible for offline conversions.

• ad_user_data (optional): this consent level is optional for sending offline conversions. However, it must be granted alongside ad_storage if you want to send hashed Personally Identifiable Information (PII) like email, phone, name, etc. (used for features like Meta Advanced Matching or Google Enhanced Conversions).

The consent state is saved securely alongside the lead data. When an offline conversion is triggered, our system checks this saved consent state to determine whether the conversion event can be sent at all, and whether PII can be included in the payload.

To successfully send hashed customer data to conversion APIs and achieve a high event match quality, you must map your form fields to standard platform parameters.

1. On the form edit page, navigate to the "Conversion tracking" section.

2. Click on "Field mapping".

3. Expand the section for your desired advertising platform. Here, you will find default platform fields that can be mapped to your form fields.

4. Select the appropriate form field for each platform PII field (e.g., Email, Phone Number, First Name).

If you realize your field mappings were missing or incorrect, you can fix them and try again. The data payload is calculated dynamically at the time of sending the offline conversion, meaning updated mappings will apply immediately.

You can trigger offline conversions directly from your submissions view.

Click on the "View Submissions" button next to your form.

Select the leads you want to send offline conversions for by checking the boxes next to their rows.

Next, click on "Bulk actions" at the top of the table and select "Send Offline Conversions".

Hint: you can use the "Available for Offline Events" filter to display only submissions that are eligible for offline conversions (i.e., those with ad_storage permission granted and submitted within the last 90 days).

In the popup window:

1. Select the platform you want to send the offline conversion to.

2. Select the event/conversion. Some conversions require you to provide a value and currency for each submission (e.g., a Facebook Purchase event).

3. Select the integration (e.g., your Facebook pixel).

4. Click the "Send offline conversions" button.

The platform will extract and hash your customer data based on your field mappings, then securely dispatch the payload to the respective platform API in the background.

You can view the status of your server events directly in the submissions table. Click the "Server Events" button to see every event sent for a specific submission (whether sent immediately upon submission or offline later). A status column indicates if the conversion was sent successfully, is still pending, or failed.

Offline conversions can only be sent for submissions created within the last 90 days. Advertising platforms typically reject offline conversions older than this window.

If you fail to map your form fields, the offline conversion may fail or suffer from poor match quality scores on the ad platform.

For Google Ads, IP address matching is not supported for end users in the European Economic Area (EEA), United Kingdom (UK), or Switzerland (CH).