Google Ads Event Form Submission Mapping to an existing conversion action
SOLVE
Hi,
we use Google Tag Manager for the Google Ads conversion Tracking, also for the Hubspot Forms embedded on our website (hosted through TYPO3).
Now I wonder, if we can create an Ads event and use the feature "Map Hubspot Form to an existing conversion action" to add it to the very same conversion action which is tracked through GTM. We would like to do that for two reasons: 1. To track/add conversions which hasnt been tracked through GTM (due to ad blocker etc.)
2. to enrich the conversion action with enhanced conversion information
Is this a proper way to do that?
After creating such an event, we see the following message:
Please note: This event type adds a new Google tag to your site. To help prevent errors, any previously installed pixels on this conversion action should be removed.
What does that exactly mean, is there now a conflict between the GTM Conversion Tracking and this new event?
Yes, it’s possible to map HubSpot form submissions to an existing Google Ads conversion action, but there are a few considerations.
Why this might be a good idea,
It helps capture conversions missed by GTM due to ad blockers or privacy restrictions. HubSpot’s integration can pass more detailed conversion data to Google Ads, enriching your conversion tracking. The warning message is letting you know that when you map a HubSpot event to a Google Ads conversion action, HubSpot will add its own Google tag to your website.
If you’re already tracking that conversion via GTM, it could potentially double-count the conversions or cause conflicts between the GTM and HubSpot tags.
How to handle this, If you proceed, you should remove the existing GTM tag for that specific conversion action to prevent double-counting.
Instead of creating a new HubSpot event, consider configuring GTM to directly capture HubSpot form submissions. This way, you can manage everything through GTM and avoid conflicts.
Final recommendation, If you want to use HubSpot’s mapping for enhanced conversions, disable or remove the existing GTM tag for that action to ensure you’re not duplicating data.
Yes, it’s possible to map HubSpot form submissions to an existing Google Ads conversion action, but there are a few considerations.
Why this might be a good idea? It helps capture conversions missed by GTM due to ad blockers or privacy restrictions. HubSpot’s integration can pass more detailed conversion data to Google Ads, enriching your conversion tracking.
The warning message is letting you know that when you map a HubSpot event to a Google Ads conversion action, HubSpot will add its own Google tag to your website. If you’re already tracking that conversion via GTM, it could potentially double-count the conversions or cause conflicts between the GTM and HubSpot tags.
How to handle this? If you proceed, you should remove the existing GTM tag for that specific conversion action to prevent double-counting.
Instead of creating a new HubSpot event, consider configuring GTM to directly capture HubSpot form submissions. This way, you can manage everything through GTM and avoid conflicts.
Final recommendation, If you want to use HubSpot’s mapping for enhanced conversions, disable or remove the existing GTM tag for that action to ensure you’re not duplicating data.
Yes, it’s possible to map HubSpot form submissions to an existing Google Ads conversion action, but there are a few considerations.
Why this might be a good idea? It helps capture conversions missed by GTM due to ad blockers or privacy restrictions. HubSpot’s integration can pass more detailed conversion data to Google Ads, enriching your conversion tracking.
The warning message is letting you know that when you map a HubSpot event to a Google Ads conversion action, HubSpot will add its own Google tag to your website. If you’re already tracking that conversion via GTM, it could potentially double-count the conversions or cause conflicts between the GTM and HubSpot tags.
How to handle this? If you proceed, you should remove the existing GTM tag for that specific conversion action to prevent double-counting.
Instead of creating a new HubSpot event, consider configuring GTM to directly capture HubSpot form submissions. This way, you can manage everything through GTM and avoid conflicts.
Final recommendation, If you want to use HubSpot’s mapping for enhanced conversions, disable or remove the existing GTM tag for that action to ensure you’re not duplicating data.
Yes, it’s possible to map HubSpot form submissions to an existing Google Ads conversion action, but there are a few considerations.
Why this might be a good idea,
It helps capture conversions missed by GTM due to ad blockers or privacy restrictions. HubSpot’s integration can pass more detailed conversion data to Google Ads, enriching your conversion tracking. The warning message is letting you know that when you map a HubSpot event to a Google Ads conversion action, HubSpot will add its own Google tag to your website.
If you’re already tracking that conversion via GTM, it could potentially double-count the conversions or cause conflicts between the GTM and HubSpot tags.
How to handle this, If you proceed, you should remove the existing GTM tag for that specific conversion action to prevent double-counting.
Instead of creating a new HubSpot event, consider configuring GTM to directly capture HubSpot form submissions. This way, you can manage everything through GTM and avoid conflicts.
Final recommendation, If you want to use HubSpot’s mapping for enhanced conversions, disable or remove the existing GTM tag for that action to ensure you’re not duplicating data.
Thanks a lot for your fast response, this is really appreciated.
Just one last question: Would it be ok, to create a new conversion goal for such an event, but keep the Tracking through GTM. Surely I would set this up as seconday conversion goal, to avoid double counting in Google Ads. But I wonder, if there still would be a tag conflict, as the same form is tracked once through GTM with conversion goal A and through Hubspot Ads Event with Conversion Goal B.
