Skip to content
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

CPC/CPA pricing for /units-for-slot #126

Open
Ivshti opened this issue Jun 3, 2020 · 0 comments
Open

CPC/CPA pricing for /units-for-slot #126

Ivshti opened this issue Jun 3, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Ivshti
Copy link
Member

Ivshti commented Jun 3, 2020

Problem

It's currently possible to set CLICK pricing for a campaign with zero IMPRESSION pricing, essentially implementing a CPC campaign.

However, the price returned from /units-for-slot (see AIP31) is respected by the AdView as the final price, and it's used to sort the available bids.

Research

https://support.google.com/google-ads/thread/1452036?hl=en - using historic CTR
https://blog.rontar.com/behind-the-scenes-how-advertising-auctions-and-cost-per-click-work - same

Solution

Use the slot average CTR to calculate a per-impression price to shim the price value.

For example, if price.CLICK is 100 and the CTR is 0.01, the returned price will be 1

It's important to use a default value in case the slot average is not available, or there's not enough data to gather it (e.g. less than 2000 impressions).

Same can be applied for custom aquisition events in the future, except it will require the rate between that event and impressions.

*The challenge is that the Market doesn't know the CTR. We can store an expectedCtr in the targetingRules by using { set: ['expectedCtr', 0.002] } and update it via a script on the validator

@Ivshti Ivshti added the enhancement New feature or request label Jun 3, 2020
@Ivshti Ivshti self-assigned this Jun 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant