This is really dependent on how your redirects are set up... if the redirect is server-side you won't be able to capture anything since the page doesn't actually load.. the request goes to the server, the server realizes that it should redirect you and then sends the user to the specified page....
Now in theory, with the above, you might be able to append some sort of query param on redirects, or inject some custom values into the page headers on the redirected page that you can read and add tracking on the AEM page indicating that it was redirected....
The other option, if you have client-side redirects in place... you could potentially add a delay, to allow tracking to happen on the page before the redirect occurs.. but this will also cause a negative impact on user experience (because they will see the Marketo Page load or start to load, then they will be redirected....
Or if using client-side redirects, you could add to that code a query string parameter (like above) onto the page you are redirecting people to, and read that on the AEM page to determine if the user was redirected.
The one caveat to remember with query strings is that you could potentially over-count value, as those URLs could end up being indexed by Search Engines, or shared by users so that other users are actually coming directly to the page with those query strings... but you can compensate for most search engines by ensuring proper canonical tags on the page, and making sure the query string parameter is added as an "ignore" in Search Console / Webmaster tools for major search engines... and the risk of user to user sharing should be fairly limited.... (just make sure your marketing team doesn't do some mass marketing campaign using the url with the parameters that they are using your proper marketing campaign params)
