How to Send HubSpot Conversions to Google Ads as Offline Events

You can see a sale in HubSpot, but Google Ads still sees only the original enquiry. The missing piece is a conversion event that connects the business outcome to the earlier ad interaction.

Start by deciding what you want to send: a contact becoming qualified, or a deal closing with an actual revenue amount. Those are different events, and the available connection methods don’t all carry the same data.

Choose the workflow that fits the outcome

Your goal	Starting point	What to check
Track contacts reaching a lifecycle stage	HubSpot’s native Google Ads conversion events	Subscription eligibility, event setup and data-sharing settings
Connect HubSpot from inside Google Ads	Google’s HubSpot data source	Supported lifecycle-stage conditions and field mappings
Upload selected deals with their actual amounts	Prepare a deal-and-contact CSV, then use TUOCA’s manual upload	Contact association, original identifiers, event timestamp and value
Automate a recurring HubSpot deal feed through TUOCA	Confirm event coverage with us first	The current connector reads contacts, not a closed-won deal revenue feed

HubSpot’s native integration supports lifecycle-stage conversion events. Its current documentation says these use a fixed value, rather than each associated deal’s amount. It also counts stage changes after the event is created; don’t assume it will backfill your existing pipeline.

Google’s HubSpot connection is another option. Its record-selection conditions depend on the Lifecycle Stage field. Review its mapping before treating it as a deal export.

Prepare one complete business event

For a revenue upload, work through one real closed-won deal before exporting hundreds. Can you trace its amount, the time it actually closed, and the contact whose earlier interaction you intend to match?

Information	Why it matters	Common mistake
Conversion action	Identifies the outcome Google should record	Sending a sale into a form-submission action
Event time and time zone	Places the outcome at the time it happened	Using the export date or a future expected close date
Conversion value and currency	Describes the value of this outcome	Repeating the whole deal amount for every associated contact
Original GCLID, when available	Links the outcome to a Google ad click	Using a campaign name or UTM parameter instead
Eligible contact email or phone	Supports enhanced-conversion matching when configured	Assuming any CRM contact is automatically attributable
Stable event reference in your records	Helps reconcile uploads and avoid sending the same event twice	Exporting the full closed-won list every week without tracking prior uploads

This is a preparation checklist, not a CSV header template. Use the fields and mapping presented by your chosen upload route.

A deal can involve several people. Choose and document which associated contact represents the lead you are measuring; don’t turn one sale into several revenue conversions merely because several contacts are attached. Likewise, define whether your event means a signed deal, a completed job or collected payment. The timestamp and value should describe that same event.

Check the identifier before troubleshooting the upload

For GCLID-based imports, the original click ID needs to survive from the landing page into the lead record. Google’s GCLID setup guide describes capture, storage and passing it with the lead. Adding a hidden form field alone doesn’t establish that the value is populated or preserved across pages.

Test the whole journey: arrive with a test parameter, navigate as a visitor would, submit the form, and inspect the resulting contact. A test string proves the capture path works; it is not a real ad click and cannot prove attribution.

If you don’t have a GCLID, review enhanced conversions for leads. Google supports matching with eligible first-party customer data under the required setup. An uploader cannot manufacture a missing ad interaction, and a successfully submitted record is not a promise of a match.

Use TUOCA for the prepared CSV upload

If your CRM export is ready but the upload process is the part you want help managing, TUOCA’s manual upload workflow is the place to start. It lets you work with a prepared file without building an API integration yourself.

1. Choose one outcome and date range. Prepare only the qualifying events you intend to measure.
2. Bring the records together. Include the relevant deal information and the associated contact identifiers. A deals-only export may need additional preparation.
3. Select Google Ads, the account and conversion action in TUOCA. Use the file mapping and review steps to check your prepared data.
4. Start with a small batch. Compare the submitted events with your source records and review the upload results before expanding the batch.
5. Check Google Ads diagnostics and reporting. Keep a record of what you submitted so you can investigate rejected or unmatched events without repeatedly resending everything.

The CSV Validator can catch basic formatting issues before this step. Its checks don’t verify your Google account configuration or predict whether a conversion will be attributed.

What the current HubSpot connector does

TUOCA’s current HubSpot connection uses a private token and reads recent contacts, including email and phone. It does not currently extract the contact’s GCLID or fetch closed-won deal amounts.

That means connecting HubSpot is not, by itself, a complete revenue-tracking setup. For actual deal values, use a prepared file or confirm a supported event source with us before relying on automation. A contact’s creation time also should not be treated as proof of when its deal closed.

Fusion addresses a related problem: matching a later conversion event to an earlier tracked lead using shared phone or email. It still needs a supported source supplying that conversion event and usable attribution data on the earlier lead. Don’t assume the current HubSpot contact connection supplies the missing deal feed.

Decide which outcome should guide bidding

You may want to observe qualified leads and sales separately. Give each outcome a clear conversion action, then choose which goal the campaign should optimize toward.

Google’s primary and secondary action guidance explains the distinction: primary actions are used for bidding when their standard goal is selected; secondary actions normally appear in All conversions for observation. Custom goals are an exception and can use secondary actions for bidding.

Sending several stages doesn’t automatically make every stage a bidding signal, or extend the eligibility window for a later sale. Review the campaign’s actual goals before adding another action.

Your next step

Pick one closed-won deal and assemble its event time, value and matching identifiers. If you can do that reliably, try the TUOCA upload workflow with a small batch. If the missing piece is a recurring HubSpot deal feed, contact us with the outcome and fields you need so we can confirm the supported path before you build around it.