-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documenting supported app<->web attribution flows #545
Comments
It is also possible that an ad impression and a click may happen in a different context from where the link is opened. Consider the following example:
In this case, the app will need to register the ad impression with the Android system API directly. However, because the click happened within the Webview, the app will need to be sure to track InputEvents in order to properly register a click with API. Here is one example of how that could be achieved: MainActivity.kt
EventCapturingWebView.kt
|
The app_to_web explainer doesn't explicitly document what conversion flows are supported on a single device, we should consider documenting explicit use-cases and how they are supported by this API.
The following table shows for impression conversion/events occurring in various contexts, what APIs are responsible for registering the reports. Rows indicate where the impression occurred, columns indicate where the conversion occurred, and table cells indicate which API is used to register.
In this table, all reports are handled by Android.
"Web" is the web API which registers with the underlying operating system described in app_to_web.md, and "OS" refers to the native API proposed by Android.
"Browser" includes various interfaces for the browser app, for example CCT in the case of Google Chrome as discussed in #239.
"WebView (rendered ad)" refers to ads where the content was rendered using a Webview, but the ad was served by the app.
A flow which doesn't fall into these categories would be:
In this case, the source event (user clicking the ad) occurred in a native app which would require the app to register the event directly with the OS. Whereas the browser is responsible for doing so today.
If there are any other flows which don't fall into these categories, we should document them as well.
The text was updated successfully, but these errors were encountered: