Skip to main content

This post was split from topic: 

 

Hello! That Q&A was very helpful and it did solve the same issue I had.

However, I get another error in the execution of the path 3 step ( gclid=exists, email=exists, phone=exists).
Despite all the records are in place, I get the following error:

“Unable to run the step, because conversion date is prior to click date”.

I assume that it tracks back the click from the gclid and gets the click timestamp and compares it with the conversion date in the excel. The excel is fed with data from webflow, which is set up in Eastern European Time (EET). Google Ads account is also set up in EET so theoretically, no problem should occur there.

I assume that maybe the problem is that the click data is reported back directly from Google Ads db with the timestamp of the db location.

How can I resolve this? Any ideas?

Hi there @Sofia Sk,

I have moved you reply to a new topic. I hope you don’t mind!

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the “CONFIGURE” section of the action step that shows all of its fields.

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!


Hi @Sofia Sk 👋

Just came across this and wanted to see how things are going, did you manage to solve this on your own? 

If so, we’d love to here what the solution was! 🙏

And if not, I wonder if using the timestamp for when the Zap runs instead of the conversation date from Excel might work better? Thinking that might help to ensure it uses a date time that’s after the click date. See: Insert the time your Zap runs into a field for more details on how to use that timestamp in a Zap. Can you give that a try and let us know if that works better?

Looking forward to hearing from you on this!


Reply