Difference between revisions of "Conversion Measurement API"
Jump to navigation
Jump to search
(Created page with "Google's Conversion Measurement API is designed to provide marketers lack-click attribution. == Impact == While Google's Conversion Measurement API does have access to granu...") |
m |
||
| Line 1: | Line 1: | ||
| − | Google's Conversion Measurement API is designed to provide marketers lack-click attribution. | + | Google's Conversion Measurement API is designed to provide marketers lack-click attribution.<ref.https://github.com/csharrison/conversion-measurement-api</ref> |
== Impact == | == Impact == | ||
Revision as of 15:23, 12 January 2021
Google's Conversion Measurement API is designed to provide marketers lack-click attribution.<ref.https://github.com/csharrison/conversion-measurement-api</ref>
Impact
While Google's Conversion Measurement API does have access to granular cross-site event information to properly match conversions on a marketer property to a prior click event, given the lack of access to other events available via Google's Aggregate Reporting API, it cannot support multi-touch or view-through attribution. By eliminating the view-through attribution, marketers will reduce the value they currently associate publishers on which they run upper funnel branding campaigns.
Open Questions
- What is the time-delay in providing the data necessary for publishers to optimize their revenue?
- What is the time-delay in providing the data necessary for marketers to optimize their media spend?
- How can marketer algorithms receive non-click and non-conversion training data?