HubSpot data
HubSpot, Shopify and Google Ads: send real revenue back to your ads
Most businesses running HubSpot and Shopify have the same gap. The store knows who bought and for how much. HubSpot knows who the contact is and where they are in the lifecycle. Google Ads and Meta know neither. They optimise to whatever conversion you gave them on day one, usually a purchase pixel or a form fill, and nothing that happens after the click.
As Google hands more of the controls to automation through AI Max, Performance Max and broad match, that gap gets more expensive. The algorithm will optimise hard to whatever signal you send. This guide covers how to close the gap so the signal is revenue.
The connected data flow
There are three systems and three jobs:
| System | Job | Data it owns |
|---|---|---|
| Shopify or BigCommerce | Transact | Orders, order value, products, carts, refunds |
| HubSpot | Understand and nurture | Contacts, lifecycle stage, deals, consent, journeys |
| Google Ads and Meta | Acquire | Clicks, click IDs, audiences, bids |
The aim is a loop: the store feeds HubSpot, HubSpot decides who is valuable, and that value goes back to the ad platforms as conversions and audiences.
Step 1: get store data into HubSpot properly
HubSpot has a native Shopify integration that syncs customers as contacts, orders as deals and your products. Switching it on is the easy part. Making the data usable takes a little more work:
- Map the properties you will segment on. First order date, last order date, order count, lifetime value and the category of the first product bought are the ones that drive most journeys.
- Decide how orders show up. A deal per order is fine for reporting, but most journeys trigger off contact level properties, so roll the key values up to the contact.
- Keep consent with the contact. Marketing consent captured at checkout needs to arrive in HubSpot, or you cannot use the contact in email or in ad audiences.
Step 2: fix lifecycle stages before you send anything to the ads
If your lifecycle stages are wrong, everything downstream is wrong. For B2B and lead based businesses, agree what a marketing qualified lead, sales qualified lead, opportunity and customer mean, write the rules down, and automate them. For ecommerce, define stages on behaviour: subscriber, first time customer, repeat customer, lapsed.
Rule of thumb: only send a stage back to Google or Meta as a conversion if your sales team would be happy for the ads to find a thousand more of them.
Step 3: send HubSpot outcomes back to Google Ads
There are two main routes:
- HubSpot's ads tool. HubSpot can send lifecycle stage and deal stage changes to Google Ads and Meta as conversion events, depending on your subscription. This is the simplest route when your ad accounts are connected to HubSpot.
- Offline conversion import with enhanced conversions. Capture the Google click ID on the form, store it on the contact, and send the outcome back when the lead qualifies or the deal closes. Enhanced conversions for leads use hashed first party data, such as email, to improve the match.
For ecommerce, send the real order value with each purchase, ideally net of discounts. If margins vary a lot by product, consider sending profit or a margin adjusted value instead, so the algorithm stops buying cheap, low margin sales.
Step 4: Meta needs the same signal, server side
Browsers now block or drop a meaningful share of pixel events. The Meta Conversions API sends events from your server, alongside the pixel, with deduplication so nothing is counted twice. Use it for purchases and for the HubSpot stages that matter, so Meta's optimisation sees the same truth as Google.
Step 5: use HubSpot lists as audiences and exclusions
- Exclude existing customers from acquisition campaigns, or bid differently for them.
- Retarget high intent contacts, such as people who started a quote or abandoned a large cart.
- Seed lookalikes from your best customers by lifetime value, not from everyone who ever bought.
Step 6: put a server side tagging layer underneath
Server side Google Tag Manager sits between your site and every vendor. It improves data quality, gives you control over what each platform receives and makes consent easier to honour. It is not mandatory for the steps above, but if you spend meaningfully on ads it usually pays for itself in data you would otherwise lose.
What good looks like
- Google and Meta optimise to qualified leads, customers or margin, not form fills.
- HubSpot journeys trigger on purchase behaviour within minutes.
- Existing customers are excluded from acquisition spend.
- One revenue report, from click to deal or order, that sales and marketing both trust.
Common mistakes
- Sending every form fill as a primary conversion, so the ads find more form fillers.
- Changing conversion goals every few weeks, which keeps the algorithm in learning.
- Syncing Shopify to HubSpot without mapping the properties journeys need.
- Forgetting consent, which quietly shrinks every audience you build.
If you want a second pair of eyes on your setup, our free audit checks exactly these points. See how we work as a HubSpot data agency, or how we connect Google Ads and Meta to your CRM.