Google Ads not detecting Google GTag AdWords conversion tag

[zigojacko]

Preconditions and environment

Magento 2.4.5-p1

Steps to reproduce

Configured GA4 Google GTag and disabled the original Google Analytics and Google AdWords tracking for UA.

Expected result

Didn't expect the purchase conversion in Google Ads to fail to detect the conversion tracking.

Actual result

Tag inactive in Google Ads conversions since the date of enabling the GA4 Google GTag and removing the previous tracking.

Additional information

Both the GA4 and AdWords conversion tracking exists in the page source.

Are we meant to leave the previous tracking for the old UA in place and active in addition on the site?

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @zigojacko. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Delta. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Delta, here is your Magento Instance: https://9c8a4d3eb02430e6258d9e80e11d55cf.instances-prod.magento-community.engineering Admin access: https://9c8a4d3eb02430e6258d9e80e11d55cf.instances-prod.magento-community.engineering/admin_4466 Login: ac644f7b Password: d4d2bc070fb1

[engcom-Delta]

Hi @zigojacko,

Can you please provide more information on this issue.

Thanks,

[zigojacko]

Hi @engcom-Delta,

With the default Magento Google Gtag GA4 and AdWords enabled and configured and the original two (Google Analytics and Google AdWords above disabled), in Google Ads, the purchase conversion tag is not detected and shows as 'Inactive'.

Sorry, I am unsure how else to add to this - that's literally the issue.

Thanks,

[ricomonkeon]

Out of interest, is your Google Ads tag ID of the format AW-1234567 or GT-1234567?
I'm having a similar problem, and my suspicion is that the former format is no longer supported, despite it being the format suggested by the Magento admin. AW- is considered a legacy prefix by Google.

[dtfdigital]

We were able to get Adwords conversion tracking working in 2.4.6 by using the "AW" conversion ID, and the conversion label value from the Sales- > Google API -> Google GTag -> Google AdWords section.

The only caveat is that it doesn't appear that the Magento code is setup to pass the order value, currency, transaction ID over within the google-adwords.js file:

`gtag( 'event', 'conversion', {'send_to': config.conversionId + '/'

• config.conversionLabel} );`

Google expects the following in order to properly register the conversion value:

gtag('event', 'conversion', { 'send_to': 'CONVERSIONID/CONVERSIONLABEL', 'value': ORDERVALUE, 'currency': 'GBP', 'transaction_id': 'ORDERIDHERE' });

This seems like a step backwards from the older google ads conversion implementation??

[m2-assistant[bot]]

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[Georgexp97]

Google Ads campaigns can be really problematic. I am constantly trying to read and expand my knowledge on this post. Recently I read this sarcastic post about Google Ads.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.