Hi Rob, have you checked out the documentation at https://developer.twitter.com/en/docs/publisher-tools/amp/overview? The section “Understanding your AMP audience -> Original URL Ping” may have the answer you are looking for.
Specifically, Twitter would ping your original URL with the __twitter_impression=true param, and it’s pretty much up to your APM analytics implementation to handle the rest. For instance, you could use this param to distinguish AMP views from Twitter from organic traffic or other sources, or use it to distinguish from the custom register ping.
Hope this is helpful!
