Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-10-03 Thread Alex Garcia
Any updates in regards to my last question? On Friday, September 29, 2023 at 5:31:43 PM UTC+2 Alex Garcia wrote: > Hi there, thanks for the update in the documentation & system! So now it's > clear that we can send click data the moment it is generated and we no > longer have to wait 6 hours

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-09-29 Thread Alex Garcia
Hi there, thanks for the update in the documentation & system! So now it's clear that we can send click data the moment it is generated and we no longer have to wait 6 hours for that. Can you please check this thread as well?

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-09-26 Thread Alex Garcia
Any updates on this thread? On Friday, September 22, 2023 at 8:51:26 AM UTC+2 Alex Garcia wrote: > At least here: > https://developers.google.com/google-ads/api/docs/conversions/upload-clicks > it still shows: > > "If you encounter a TOO_RECENT_CONVERSION_ACTION or TOO_RECENT_EVENT > response

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-09-22 Thread Alex Garcia
At least here: https://developers.google.com/google-ads/api/docs/conversions/upload-clicks it still shows: "If you encounter a TOO_RECENT_CONVERSION_ACTION or TOO_RECENT_EVENT response message to an upload conversion request, wait at least 6 hours after the action creation or event before

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-09-17 Thread Alex Garcia
Any updates to improve this delay of 6 hours? With Facebook & TikTok Ads API, you can upload the conversions right away, without having to wait 6 hours. On Friday, February 10, 2023 at 4:45:59 AM UTC+1 Robert De Vivo wrote: > Another person here suffering with this, no idea why Google drops

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2023-02-09 Thread Robert De Vivo
Another person here suffering with this, no idea why Google drops the ball here.. Simple fix ?? Can you guys escalate this to your team this is leaving revenue on the table On Wednesday, July 6, 2022 at 3:56:49 PM UTC-4 Mike M wrote: > Alex, I know that I'm responding to this thread very late.

Re: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2022-07-06 Thread Mike M
Alex, I know that I'm responding to this thread very late. (I don't work for Google, btw.) We encountered the same delay issue in our campaigns. To rectify the problem, we added a tracking system called Matomo (which has a free community edition adn was formerly called Piwik) so that we could

RE: iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2022-02-18 Thread 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
Hi, I've already passed along the feedback to the relevant teams. But this is a change that has to happen first at the product level and the API should start behaving the same way. Cheers Anash ref:_00D1U1174p._5004Q2Wvmdh:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find

iRe: The click associated with the given identifier or iOS URL parameter occurred less than 6 hours ago, please retry after 6 hours have passed

2022-02-17 Thread Hustle OU
Hi Anash, Yes, I know how it works, but ideally, it should work in real time, without having to wait 6 hours to post the data. I have already explained the reasons why this is not ideal (current scenario). Would you be able to send a feedback request to the engineering team so they implement