To ensure proper attribution validation, the tag must be triggered with a delayed request, ideally 8 to 23.5 hours after the original conversion event (it can be earlier).
The reason is that the Google Ads Conversions Improver Tag checks in Google Ads if a conversion has been recorded or not. For this check to work properly, the tag must execute later than the actual conversion time, allowing Google Ads enough time to process the original conversion. When the tag queries Google Ads, it can then correctly detect whether the conversion was attributed or not and resend it if needed.
Just looking for a clarification. If an adjustment is logged earlier than 8 hours, is the expectation that you would receive this (200) response or would you expect a CONVERSION_NOT_FOUND error?
If an adjustment is logged earlier than 8 hours, is the expectation that you would receive this (200) response or would you expect a CONVERSION_NOT_FOUND error?
It can receive any. This depends on whether or not Google has already successfully processed the original conversion.
If it has been processed, a successful 200 code is received, and the tag makes no further requests. Otherwise (if a CONVERSION_NOT_FOUND error is received), the tag makes a new request to record the conversion.
The minimum 8-hour delay is merely a flexible recommendation to ensure Google has had time to process the original conversion. This avoids resending a conversion request for something that would be recorded anyway.
It seems to me that the API is always returning 200 and no errors so we never fall through to the offline conversion upload branch.
If that’s the case, then it means that these conversions are being recorded just fine by Google.
Note that I read in this blog post from Google that the 24hr window for adjustments is no longer required, but the up to 24hrs thing isn’t mentioned.
Also a flexible recommendation to avoid sending a conversion too late. You can test with different delays and see the results.
