Timing can be a hard challenge (especially when your site is running efficiently).
Honestly, I try to avoid as many "click based" tracking calls as I can, instead I use Activity Map (with modifications) to collect information about what is being clicked.
At other times, this is unavoidable, and I have to track information that is only available on the first page... one such example for me is Newsletter Signups... The user can sign up for one or more newsletters, but they are then taken to a new page with a success message... however, the information about the newsletters doesn't exist here...
Taking a page out of how Activity Map works, I have a small lighter weight script to write the JSON of the newsletter signups into a session storage variable; then on the success page, I read the session storage, process the data into a tracking call, send the data to Adobe, and then I delete the session storage so that the information cannot be double (or more) tracked.
I built this logic into my general page tracking, if the session storage exists, add it to the tracking call... hence why the session storage must be removed... but even if you had a designated rules for the success page, it's still better to remove, in case the user later in their session decides to hit their browser's back button multiple times and goes through that page again... it's built-in security to prevent over-counting.
If you are really set on tracking the click action as a click, on the specific page... you may have to work with your developers to build in an artificial delay on the clicks... but your business may not like that approach....