What is offline conversion import?

When someone clicks an ad, the platform adds an identifier to the landing page URL. Google Ads uses the GCLID and related IDs; Meta uses its own click ID. The website captures that ID with the form submission or call and stores it in the CRM. Later, when the lead becomes a qualified lead, a booked appointment or a paying patient, the practice uploads a conversion record with the click ID, the conversion name, time and optionally a value. The platform matches it to the original click and reports it as a conversion.

Uploads can be manual files, scheduled imports or API connections from the CRM. Google also offers enhanced conversions for leads, which match using hashed contact details instead of or alongside click IDs. Meta's equivalent runs through its Conversions API.

The benefit is better optimization. Automated bidding learns from the outcomes you send, so sending booked appointments rather than all form fills can shift spend toward people more likely to book.

The biggest risk is treating this as a purely technical project. Telling an ad platform that a specific clicker became a patient of a healthcare provider can itself be a PHI disclosure, depending on the setup and the data. Some practices use only pre-appointment stages, de-identified signals or vendors that sign a BAA. This needs a compliance decision, not just a developer.

Common technical mistakes include losing click IDs when forms or booking widgets sit on other domains, uploading duplicates, and sending conversions too late for the platform's import window. Match rates are never perfect, so compare imported numbers to your CRM totals.