Paid ad platforms like Google Ads and Meta Ads are built to optimize for online actions such as clicks, form fills, or purchases. But many businesses generate value offline: phone calls, in-store visits, signed contracts, or long sales cycles that close days or weeks after the initial ad click. Without connecting your CRM to your ad platforms, those offline conversions remain invisible, and the bidding algorithms are blind to the full picture.<\/p>\n
By integrating a CRM (HubSpot or Salesforce) with your ad accounts, you can import offline conversion events. This enables the platforms to optimize for real business outcomes, not just surface actions. The result is better cost per acquisition, more accurate attribution, and the ability to scale campaigns that drive qualified leads.<\/p>\n
At its core, the integration involves three steps: capturing the ad click identifier (GCLID for Google Ads, click ID for Meta Ads) at the time of lead capture, storing that identifier in your CRM alongside the lead record, and then sending a conversion event back to the ad platform when the lead reaches a defined stage (e.g., opportunity created, deal won, invoice paid).<\/p>\n
Both HubSpot and Salesforce offer native integrations or APIs to accomplish this. The key is to ensure that every lead generated from a paid ad carries the correct click ID and that your CRM automatically passes the conversion signal back at the right time.<\/p>\n
Google Ads allows you to upload offline conversions via a CSV file, the Google Ads API, or integrated partner platforms. The most efficient method for CRM integrations is to use the API or a partner integration like HubSpot\u2019s native Google Ads integration or Salesforce\u2019s Marketing Cloud connectors.<\/p>\n
To start, you need to enable auto-tagging in your Google Ads account so that all ad clicks append a GCLID parameter to your landing page URLs. When a user fills out a form or makes a call, your CRM must capture that GCLID and store it with the lead record. Then, when the lead converts offline (e.g., a sales rep closes a deal), you upload a conversion event containing the GCLID, conversion name, conversion time, and optionally a conversion value.<\/p>\n
Google Ads matches the GCLID to the original click and attributes the conversion to the correct campaign, ad group, and keyword. This data then feeds into your bidding strategies, allowing Smart Bidding to optimize for offline conversions.<\/p>\n
Meta Ads uses a similar concept but with a different identifier. Meta assigns a unique click ID (fbclid) to each ad click. When a user lands on your site, you capture that ID and pass it to your CRM. Later, you can send offline conversion events back to Meta via the Conversions API (CAPI) or the Offline Events API.<\/p>\n
Meta\u2019s Offline Conversions tool allows you to upload offline event data from your CRM. The data must include the click ID, event name, event time, and any optional parameters like value. Meta matches the event to the original ad click and uses it for attribution and optimization.<\/p>\n
If you are using HubSpot, there is a native integration with Meta that can automate this process. HubSpot can send offline events directly to Meta when a contact reaches a specific lifecycle stage (e.g., Customer) or when a deal is closed. For Salesforce, you may need to use a third-party connector or build a custom solution using Meta\u2019s Offline Events API.<\/p>\n
HubSpot offers out-of-the-box integrations for both Google Ads and Meta Ads. The Google Ads integration syncs campaign data, and it also supports offline conversion tracking. To set it up, connect your Google Ads account in HubSpot, then enable the \u201cOffline conversion tracking\u201d feature. HubSpot will automatically send Google Ads conversion events when a contact progresses to a lifecycle stage you define, such as \u201cSQL\u201d or \u201cCustomer.\u201d<\/p>\n
For Meta Ads, HubSpot has a similar integration. After connecting your Meta Ads account, you can set up offline event tracking. HubSpot will send the event when a contact reaches a specified stage or when a deal stage changes. You can also map custom fields to ensure the correct data is passed.<\/p>\n
One important detail: both integrations require that the click ID is captured on the landing page. HubSpot\u2019s tracking code can automatically capture the GCLID and fbclid from URL parameters and store them on the contact record. This happens transparently as long as the tracking code is installed on your site.<\/p>\n
Salesforce does not have a direct native integration for offline conversion tracking with Google Ads or Meta Ads, but it offers several paths. The most common is using the Google Ads API or Meta\u2019s Offline Events API combined with a middleware tool like Zapier, Workato, or MuleSoft.<\/p>\n
For Google Ads, you can create a custom solution that queries Salesforce for leads that have a GCLID and a conversion date, then uploads them via the API. Alternatively, you can use the Salesforce Marketing Cloud connector if you have that product.<\/p>\n
For Meta Ads, the process is similar. You can use the Offline Events API to send events from Salesforce. Tools like Zapier can trigger a webhook when a Salesforce lead or opportunity meets your criteria, then call the Meta API. However, this approach requires careful mapping of fields and handling of click IDs.<\/p>\n
Some third-party platforms (like LeadsBridge or Funnel) provide pre-built connectors that automate the entire flow between Salesforce and ad platforms. These can be a good investment if you need a reliable, low-maintenance solution.<\/p>\n
Accuracy depends on correctly mapping fields between your CRM and the ad platform. The critical fields are the click ID (GCLID or fbclid), the conversion event name, the conversion timestamp, and any monetary value. Additional fields like conversion category or email can be used for deduplication.<\/p>\n
Data quality matters. If your CRM captures multiple GCLIDs for the same lead (e.g., from different sessions), you should use the first click ID or the one from the last ad interaction, depending on your attribution model. Also, ensure that the conversion timestamp is in the correct timezone and format. Google Ads expects UTC, while Meta expects a Unix timestamp in seconds.<\/p>\n
Regularly audit your integration. Check that click IDs are being captured on new leads. Verify that the conversion events sent from your CRM match the definitions in your ad accounts. Discrepancies often arise from missing click IDs, timezone mismatches, or duplicate events.<\/p>\n
Not every offline action is worth sending back. Focus on events that align with your business goals and that have enough volume for the ad platform to learn from. Common events include:<\/p>\n
Qualified lead<\/strong> \u2013 when a lead is accepted by sales (e.g., marketing qualified lead becomes sales qualified lead). If you send too many events, the platform may dilute the signal. If you send only final revenue, you may have long delays and sparse data. A good practice is to send a mid-funnel event (e.g., opportunity created) and a final event (deal won) with value. Then you can set up different conversion actions for bidding and reporting.<\/p>\n Once offline conversions are flowing, you can use them in your Smart Bidding strategies. In Google Ads, you can set a target CPA or target ROAS based on offline conversions. In Meta Ads, you can optimize for the offline event (e.g., Purchase) using the Value Optimization feature.<\/p>\n Attribution will also improve. Instead of only seeing the last click before a form fill, you will see the full path to revenue. This allows you to allocate budget to channels and keywords that drive actual business outcomes, not just leads.<\/p>\n However, be aware of attribution lag. Offline conversions may take days or weeks to occur. Ad platforms handle this by using a conversion window (e.g., 30 days) and by modeling delayed conversions. You can also use offline conversion import to backfill conversions that happened earlier, which helps the model adjust.<\/p>\n Missing click IDs<\/strong>: If your landing page does not capture the GCLID or fbclid, offline conversions cannot be matched. Ensure your CRM tracking code is set to read URL parameters and store them on the contact record. Test with a few ad clicks.<\/p>\n Duplicate conversions<\/strong>: If the same lead converts multiple times (e.g., multiple deals), you may send duplicate events. Use deduplication rules in the ad platform. For Google Ads, you can set a conversion count method to \u201cunique\u201d per click. For Meta, you can use the event ID to prevent duplicates.<\/p>\n Timeouts and delays<\/strong>: Some integrations have a delay of a few hours. If you need real-time updates, consider using the API directly. For most businesses, a daily sync is sufficient.<\/p>\n Privacy and consent<\/strong>: Offline conversion data includes personal information. Ensure you comply with data protection regulations (GDPR, CCPA). Obtain consent for tracking and for sharing data with ad platforms. Anonymize or hash data where required.<\/p>\n Before going live, run a test. Create a test lead from a paid ad, ensure the click ID is captured, then manually mark that lead as converted in your CRM. Check that the conversion appears in the ad platform\u2019s \u201cConversions\u201d section within 24 hours. Use the diagnostics tools in Google Ads (Offline Conversion Import reports) and Meta Ads (Offline Events Manager) to validate the data flow.<\/p>\n Also monitor the conversion lag report. This tells you how long after the click the conversion typically occurs. Use this information to adjust your conversion window settings.<\/p>\n Once the basic integration is stable, you can explore advanced use cases. For example, pass back conversion value using different currencies or product categories. You can also use offline conversion data to build custom audiences in Meta Ads: for instance, create a lookalike audience based on people who converted offline.<\/p>\n For Google Ads, you can import offline conversions with different attribution models (e.g., first-click, data-driven). This gives you more nuanced reporting. You can also use the offline conversion data to improve your Google Ads Quality Score indirectly by showing that your ads lead to high-value outcomes.<\/p>\n If you have multiple CRMs or a complex sales process, consider a customer data platform (CDP) that unifies data before sending to ad platforms. This can reduce duplication and simplify management.<\/p>\n An integration is not a set-and-forget solution. Regularly review the data flow. Check for gaps: if you see leads with no click ID, investigate your landing page tracking. If you see conversion events with missing values, update your CRM automation rules. Also, keep an eye on changes to ad platform APIs. Google and Meta occasionally update their offline conversion requirements (e.g., new hashing requirements). Stay informed through their developer documentation.<\/p>\n Finally, align your sales and marketing teams on the definitions of conversion events. If sales changes the deal stages, you may need to update the integration so that the correct events are sent. A quarterly review of the mapping is a good practice.<\/p>\n","protected":false},"excerpt":{"rendered":" This article explains how to integrate HubSpot or Salesforce with paid ad platforms like Google Ads and Meta Ads to track offline conversions. You will learn the technical setup, field mapping, data quality checks, and how to use the synced data to improve bidding and attribution.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[183,206,239],"tags":[],"class_list":["post-1921","post","type-post","status-publish","format-standard","hentry","category-crm-integration","category-offline-conversions","category-paid-ads"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1921","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/comments?post=1921"}],"version-history":[{"count":1,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1921\/revisions"}],"predecessor-version":[{"id":1922,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1921\/revisions\/1922"}],"wp:attachment":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/media?parent=1921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/categories?post=1921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/tags?post=1921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Opportunity created<\/strong> \u2013 when a deal is opened in the pipeline.
Deal won<\/strong> \u2013 when a contract is signed or payment is received.
Revenue<\/strong> \u2013 the actual amount closed.<\/p>\nAttribution and Bidding Implications<\/h2>\n
Common Pitfalls and How to Avoid Them<\/h2>\n
Testing the Integration<\/h2>\n
Scaling Beyond Basic Integration<\/h2>\n
Maintaining the Integration<\/h2>\n