Hi Scott,
Using the AdWords API, you should be able to upload your external
conversions by following this section
<https://developers.google.com/adwords/api/docs/guides/conversion-tracking#importing_externally_attributed_conversions>
of
our tracking and importing conversions
<https://developers.google.com/adwords/api/docs/guides/conversion-tracking>
guide.
Once uploaded, your conversions details and their value should reflect both
in the Google Ads UI and in the API reports.
If I misunderstood your concern, you may provide more details so I can
better assist you.
Thanks and regards,
Peter
Google Ads API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
https://ads-developers.googleblog.com/search/label/google_ads_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
On 05/05/19 23:53:44 [email protected] wrote:
One of our major sources of income for our software product comes from a
webstore that does not support tracking the user all the way to the
purchase - We only get tracking from ad clicks to the landing page for our
product. We cannot influence them to change this further. We have developed
the ability to read the GCLID cookie token from the users' device when they
launch our software for the first time. We have successfully tested
conversion tracking through the use of Google Analytics Goals tracking by
sending events to the Analytics API. Whilst this works, it seems like a lot
of setup and bother - Is there an easier and more direct way to send a
conversion event with the GCLID cookie token and value of the purchase?
Cheers.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/3e82e275-667b-4ffe-9344-501b1a3cdda6%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/3e82e275-667b-4ffe-9344-501b1a3cdda6%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/ijlio3nsfg00000003r88o000f01bcy6smj6cpk6oo30c1g68r36dph%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
