...
If you have other traffic sources apart from Google Ads, and in the moment of sending the conversion (e.g. from a server script) you cannot tell whether the click ID value that you have stored is a Google Ads click ID, we recommend to pass the value in the query parameter cli because it accepts all other click IDs as well.
(For details about how to pass click IDs with conversions, have a look at our article describing the conversion tracking codetag.)
When the Ingenious system receives the conversion, it will search for all relevant user interactions based on all tracking methods that you have in use. As part of that, the system will find the click with your specified ID. The system will proceed then to attribute conversions based on the attribution settings of your advertiser.
...
(For details about how to pass click IDs with conversions, have a look at our article describing the conversion tracking codetag.)
When the Ingenious system receives the conversion, it will search for all relevant user interactions based on all tracking methods that you have in use. As part of that, the system will find the click with the specified ID. The system will proceed then to attribute conversions based on the attribution settings of your advertiser.
...
(For details about how to pass click IDs with conversions, have a look at our article describing the conversion tracking codetag.)
When the Ingenious system receives the conversion, it will search for all relevant user interactions based on all tracking methods that you have in use. As part of that, the system will find the click with the specified ID. The system will proceed then to attribute conversions based on the attribution settings of your advertiser.
...