CRM Integration for Paid Ads: Connecting HubSpot and Salesforce to Capture Offline Conversions

Why offline conversions matter for paid media

Online click data tells you who visited a landing page, but many high‑value actions happen later in a sales system. When a lead closes in HubSpot or a deal is marked won in Salesforce, that revenue should feed back into the ad platform so bidding algorithms can reward ads that truly drive profit.

Preparing CRM data for export

Both HubSpot and Salesforce store a rich set of fields. Before you export, define a minimal schema that includes:

1. Unique click identifier that matches the ad click ID (gclid, fbclid, etc.).
2. Conversion timestamp in UTC.
3. Revenue amount or other value metric.
4. Customer or lead ID for deduplication.

Remove any personally identifiable information unless the ad platform explicitly supports it.

Integrating HubSpot with Google Ads

Google Ads offers a native connector for HubSpot. Follow these steps to enable the flow:

1. In HubSpot, navigate to Settings → Integrations → Google Ads.
2. Connect the Google Ads account and grant read/write permissions.
3. Map the HubSpot field that stores the GCLID to the Google Ads click ID column.
4. Configure the offline conversion upload schedule – daily is typical.
5. Validate the first batch by checking the Offline conversions report in Google Ads.

When a contact reaches a stage marked as “Customer” in HubSpot, the system automatically pushes the conversion back to Google Ads using the stored GCLID.

Integrating Salesforce with Meta Ads

Meta’s Conversions API allows you to send offline events directly from Salesforce. The process involves three parts: an API endpoint, a data mapping layer, and a secure authentication token.

1. Create a custom field in Salesforce to capture the Facebook click ID (fbclid) during the lead capture form.
2. Set up a Salesforce Process Builder or Flow that triggers when a Deal stage changes to Closed Won.
3. In the flow, call a middleware (for example a small Azure Function) that formats the payload and posts it to the Meta Conversions API endpoint.
4. Include the event name “Purchase”, timestamp, value, and the fbclid.
5. Monitor the API response in Salesforce logs to catch any errors.

After the first successful upload, Meta will attribute the offline purchase back to the original ad, improving the relevance score for future bidding.

Best practices for data hygiene and attribution

Accurate offline conversion tracking relies on clean data. Adopt these habits:

• Always store click IDs in a dedicated field at the moment of capture – never generate them later.
• Standardise timestamps to UTC and use ISO 8601 format.
• Apply a deduplication rule that discards duplicate click IDs within a 30‑day window.
• Regularly audit the mapping between CRM fields and ad platform parameters.

These steps reduce attribution errors and keep cost‑per‑acquisition metrics reliable.

Automating the sync workflow

Manual uploads are prone to delay. Use one of the following automation patterns:

1. Schedule a nightly extract‑transform‑load (ETL) job that pulls new closed‑won records, formats them to CSV, and pushes to Google Ads via the API.
2. Leverage a serverless function that reacts to a Salesforce Platform Event and immediately posts the conversion to Meta.
3. Employ a third‑party integration platform (e.g., Zapier, Tray.io) that maps HubSpot or Salesforce fields to the respective ad API calls without writing code.

Choose the pattern that matches your technical resources and latency requirements.

Common pitfalls and troubleshooting

If conversions are not appearing, check these areas first:

• Missing click ID – the form may not be capturing gclid or fbclid correctly.
• Time lag – some platforms only accept conversions within 90 days of the click.
• Currency mismatch – ensure the value field uses the same currency as the ad account.
• Authentication errors – API tokens expire; rotate them on schedule.

Review the platform’s error logs, correct the root cause, and re‑upload the affected rows.