As advertisers, we often think of the major ad platforms like Google as being black boxes with secretive, complex objectives, and it makes it hard to envision the future of advertising.
We can, however, find some clues by looking at the research they publish. Google has an extensive list of research papers, and they continually add to the vault. Reading these papers, we can start to get a peek inside the mind of Google’s decision makers, and use this insight to try to understand their priorities.
With that in mind, we took a look at two recent research papers to see what they can teach us about what ad platforms might be considering for the journey ahead.
Digital advertising provides comprehensive metrics on actions people take after seeing an ad. While this data is highly usable for low-funnel channels like search, it’s less useful on upper-funnel channels like display and video. This is because these upper-funnel channels aren’t designed to elicit immediate action; they’re designed to build emotional connections.
People don’t buy a new car simply because they saw a car brand’s display ad. The objective of advertising on these channels is to build an emotional connection with users over time. So eventually, when they need a new car, they consider that brand.
But this presents a challenge: It’s not possible to measure emotions in digital advertising. No ad platform can tell you how many people smiled while watching your ad, nor how many people felt bored by the end of it.
A joint 2019 paper from Google and Microsoft, AttentiveVideo: A Multimodal Approach to Quantify Emotional Responses to Mobile Advertisements looks into how to solve this problem.
In the paper, the authors describe AttentiveVideo, software that uses a user’s mobile device to measure the user’s emotions while watching an ad. The user is instructed to hold his finger over the rear-facing camera lens to play the ad, at which point:
The researchers conducted a study with real users to gauge emotional response to ads. The collected data showed they were able to determine a user’s emotional response to an ad with 83% accuracy.
Given how valuable emotional data could be to brand advertisers, it’s not unthinkable that we might see ad networks crop up in future that are built around this idea.
Of course, there is likely to be opposition from some users, who may not feel comfortable granting advertisers access to such personal data. Still, as we’ve seen with other channels of advertising, the financial incentives for publishers may be so great that they find ways to overcome these barriers.
Search advertisers have come to recognize that there is natural tension between paid and organic search. Both channels are competing for the same users, so there’s always a risk that paid search ads become pure cost, driving up prices for clicks that you could have otherwise acquired for free, organically.
The second Google paper we reviewed discusses this challenge in the context of organic search position. The paper, Impact Of Ranking Of Organic Search Results On The Incrementality Of Search Ads, explores how the position of a brand’s organic search results can affect the incrementality of their paid traffic on that results page.
The paper is in the form of a meta-analysis, through which the authors review 390 different Search Ads Pause studies — experiments where advertisers turn search ads off and measure the impact. The most interesting finding is that the proportion of a brand’s search ad clicks that are incremental — meaning they wouldn’t have occurred if there were no search ads — depends heavily on the position of the brand’s organic result.
If a brand is showing an ad on a particular term, and it has an organic result in position #1 for that term (immediately below the ad positions), then the authors estimate only 50% of the ad’s clicks will be incremental.
This means that the advertiser’s cost per incremental click — that is the cost of generating one more click than they would’ve otherwise gotten — is going to be twice their reported cost per conversion. The percentage of incremental clicks rises to 82% when the organic result is in positions #2 through #5, and to 96% when the organic result is below position #5.
In other words, the research suggests that when advertisers rank organically for a particular keyword, the higher the organic position, the more expensive it is to also use a paid ad for that keyword.
These findings have huge significance for brands that rank well organically. While they don’t suggest that these kinds of brands should completely turn off paid search for terms where they appear at or close to position #1, it does demonstrate that advertisers should think carefully about how they bid.
One consideration is to incorporate these results into attribution. By looking at rank data for all organic search terms, you can then determine how many clicks, and therefore conversions, were incremental for that keyword. Knowing this, you can then apply different budgets accordingly.
These are just two small glimpses into the questions platforms are actively answering and the challenges they’re trying to solve. In an environment where predicting platform changes is very difficult, this kind of insight can be very valuable to brands. These research papers offer us all a deeper understanding of the priorities these powerful platforms have, and allows us to consider what their mindset might be for the future.
If you want to discuss more about emotional responses, incrementality, or performance branding, WITHIN is here to help. Reach out any time.
Get industry insights and news directly to your inbox.
Thank you. Check your email for details on your request.
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
checkForPermission | 10 minutes | This cookie is set by Beeswax to determine whether the user has accepted the cookie consent box. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
__lotl | 5 months 27 days | This cookie is set by Lucky Orange to identify the traffic source URL of the visitor's orginal referrer, if any. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_lo_uid | 2 years | This cookie is set by Lucky Orange as a unique identifier for the visitor. |
_lo_v | 1 year | This cookie is set by Lucky Orange to show the total number of visitor's visits. |
_lorid | 10 minutes | This cookie is set by Lucky Orange to identify the ID of the visitors current recording. |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
IR_gbd | session | Impact Radius sets this cookie to store a unique ID which is used to identify the user's device, when they return to the websites that used the same network. |
Cookie | Duration | Description |
---|---|---|
__qca | 1 year 26 days | The __qca cookie is associated with Quantcast. This anonymous data helps us to better understand users' needs and customize the website accordingly. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_mkto_trk | 2 years | This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo. |
B | 1 year | This Cookie is used by Yahoo to anonymously store data related to user's visits, such as the number of visits, average time spent on the website and what pages have been loaded. This data helps to customize website content to enhance user experience. |
bito | 1 year 1 month | This cookie is set by Beeswax for advertisement purposes. |
bitoIsSecure | 1 year 1 month | Beeswax sets this cookie for targeting and advertising. The cookie is used to serve the user with relevant advertisements based on real time bidding. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
mc | 1 year 1 month | Quantserve sets the mc cookie to anonymously track user behaviour on the website. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
tuuid | 2 years | The tuuid cookie, set by BidSwitch, stores an unique ID to determine what adverts the users have seen if they have visited any of the advertiser's websites. The information is used to decide when and how often users will see a certain banner. |
tuuid_lu | 2 years | This cookie, set by BidSwitch, stores a unique ID to determine what adverts the users have seen while visiting an advertiser's website. This information is then used to understand when and how often users will see a certain banner. |
Cookie | Duration | Description |
---|---|---|
__pdst | 1 year | No description available. |
_an_uid | 7 days | No description available. |
_dc_gtm_UA-61749619-1 | 1 minute | No description |
_dlt | 1 day | No description |
_hjSession_1771567 | 30 minutes | No description |
_hjSessionUser_1771567 | 1 year | No description |
_nx-nocache | session | No description available. |
6suuid | 2 years | No description available. |
A3 | 1 year | No description |
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ | session | No description |
AnalyticsSyncHistory | 1 month | No description |
BIGipServerab44web-nginx-app_https | session | No description |
bounceClientVisit3783c | 30 minutes | No description |
bounceClientVisit3783v | 30 minutes | No description |
dgzsdl08v4 | 10 minutes | No description |
IR_11658 | session | No description |
li_gc | 2 years | No description |
tableau_locale | session | No description available. |
tableau_public_negotiated_locale | session | No description available. |
test | 1 year | No description available. |