You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation does not mention anything about how amp-ad-exit compares to amp-analytics when it comes to pinging click URLs from AMPHTML ads. Are there any differences when it comes to things like reliability vs using a click handler that's attached to the link that opens an external URL?
amp-ad-exit does not appear to currently support all variable substitutions that we need (like COUNTER) and I was wondering if we should submit a feature request so that we can use the exit API, or if using amp-analytics is fine if we're not looking to use the additional features like filtering.
The text was updated successfully, but these errors were encountered:
according to the original design #8515 , ping back URL in amp-ad-exit supports extra features like filtering out "unintentional clicks", which is not supported in amp-analytics click trigger.
Let us know if any useful macros are needed in amp-ad-exit.
The documentation does not mention anything about how amp-ad-exit compares to amp-analytics when it comes to pinging click URLs from AMPHTML ads. Are there any differences when it comes to things like reliability vs using a click handler that's attached to the link that opens an external URL?
amp-ad-exit does not appear to currently support all variable substitutions that we need (like COUNTER) and I was wondering if we should submit a feature request so that we can use the exit API, or if using amp-analytics is fine if we're not looking to use the additional features like filtering.
The text was updated successfully, but these errors were encountered: