Connect calls to GA4 and a CRM: a reproducible example

A useful connection preserves the contact ID from the call to the opportunity in the CRM. GA4 can receive the phone event and help analyze the web tour; the CRM confirms what happened commercially. The two reports may differ due to their criteria and limitations.

The example uses WhatConverts, GA4, and HubSpot with Zapier because its steps are documented. This is not a claim that it is the only combination nor a test conducted by CallsIQ. To play it you will need accounts, permissions, and a plan that includes the features; The cost of the integrator must also be confirmed.

Prepare the test environment

Use a page you control, a test GA4 property, and fictional business records. Set up labels and consent before collecting data. Do not use customer information to verify that fields arrive.

In the example, the visit source is “essay”, the medium “test” and the campaign “callsiq_demo”. These labels do not simulate real advertising attribution. The call must be directed to an authorized trial number. Mark all created contacts as tests and exclude them from business reports and objectives.

1. Connect telephone measurement with GA4

The WhatConverts documentation indicates that, from Tracking and Integrations, you can add a property in the Google Analytics module. Requests the Measurement ID and an API Secret from GA4 and allows you to select the types of contacts sent. Keep the secret only in the provider's authorized settings; do not copy it to the public code of the page. Official connection with GA4 .

First choose only rehearsal calls and note the exact name of the event received. A connector can send phone_call , while a self-implementation could follow recommended names such as generate_lead . Don't blindly rename or send both versions as if they were different contacts. GA4 Recommended Events .

2. Send the contact to HubSpot

The WhatConverts documentation describes the flow to HubSpot using Zapier. Enabling the capture of a HubSpot visitor ID doesn't by itself set up a sync: the workflows are required. Preparation of the connection .

1. Prepare a property in HubSpot to hold the WhatConverts Lead ID. One contact is enough to test a single call; If there will be multiple opportunities, preserve the relationship in each one and avoid overwriting the origin of a previous sale.
2. In Zapier, use the WhatConverts New Lead event as input.
3. Configure the create or update contact action in HubSpot and relate the necessary fields, including the Lead ID.
4. Run the test before activating the flow. Check which key the connector uses to update an existing record.

For testing, use a test email that you check if the action requires it and disable automatic messages. In production, a call may not contain email: don't invent one to complete the flow. Confirm an action consistent with the available data or send the case for review. Avoid overwriting the Lead ID of previous opportunities when the same person calls again.

These steps follow the guide sending contacts to HubSpot . CRM personal data is governed by its specific processing; They should not be copied indiscriminately to GA4.

3. Reproduce a fictional lead and closed sale

Open the tagged page in a new session, make the rehearsal call, and note the time. Check the registration in WhatConverts, the event in GA4 and the contact in HubSpot. You then link the opportunity and change its status to won.

To return the closure, configure a second flow. The supplier guide uses the business record and contact ID to update the value in WhatConverts. Don't assume that the first lead generation flow also returns sales. Returning sales value to the measurement system .

4. Check for errors that alter results

Repeat the same submission and check that a second sale does not appear. Also make an unanswered call and a visit without measurement consent. The site must continue to function and not generate the same analytics logs as an authorized visit when the applicable settings do not allow this.

Review the fields sent to GA4: names, telephone numbers, emails and transcripts should be left out. An internal random identifier also does not by itself eliminate data protection obligations. Avoid URL parameters or dimensions with identifying data. Analytics Personal Data Policy .

A late sale does not reconstruct the original session

If Measurement Protocol is used to associate an event with a particular session, Google requires conditions such as session_id , sending within 24 hours of start, and supported timestamps. A CRM shutdown that occurred weeks later cannot be arbitrarily backdated to comply. Advertising export rules are different from session attribution. Measurement Protocol Requirements .

Therefore preserves the original source in the CRM and in the attribution report. If self-developed, validate events before producing data: the validation server does not ingest events into reports, and an HTTP success does not prove that a measurement was processed correctly. Validation of events .

The connection is proven when you can follow the same contact and its sale, see its limits and reproduce the result without duplicates. Keep screenshots, configuration, and test date before claiming it works in your environment.

Sources and limitations

Documentary review: 30 September 2026. Content type: Documentation-based procedure.

Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.

• Official connection with GA4www.whatconverts.com
• GA4 Recommended Eventsdevelopers.google.com
• Preparation of the connectionwww.whatconverts.com
• sending contacts to HubSpotwww.whatconverts.com
• Returning sales value to the measurement systemwww.whatconverts.com
• Analytics Personal Data Policysupport.google.com
• Measurement Protocol Requirementsdevelopers.google.com
• Validation of eventsdevelopers.google.com

How to report a correction