Right now we are sending conversion events to Google Analytics to track
conversions. Google Ads is linked to Analytics, which means our paid ads
get the imported conversions. This works but the setup is very involved and
the conversion events in Analytics use the date of conversion incorrectly
Hi,
I'm writing an app to help clients (Currently only us) track click to
purchase conversions across a path flow that cannot currently be done via
normal methods. When the app launches for the first time (It is a desktop
app, not a mobile app) it will send the cookie gclid of the original
Is there anyone I can talk with to try to discover a solution to our
particular problem? We are able to change the way we submit event if
necessary. We just need to know what the correct approach is.
On Monday, May 13, 2019 at 8:19:36 PM UTC+1, googleadsapi-forumadvisor
wrote:
>
> Hello Scott,
Hi,
We get our conversions for Ads through Analytics Goals events and that is
currently working. However for reporting we need to be able to match each
conversion recorded by Google Ads with the event that caused it as we
attribute specific value depending on the event action and label.
--
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
We are sending custom events to the Analytics API to trigger goals, which
then cause a conversion in any linked ad campaigns to the user. These
events contain information about the purchase of the product and therefore
the value. The value is not stored in the conversion event as it can be
