eComm and D2C will be acutely impaired by the ATT opt-in mechanic coming to iOS (rumored made mandatory in March). ATT doesnt exclusively impact app advertisers, & in fact may disproportionately damage eComm and D2C. Some thoughts on how those advertisers should prepare (1/X)

2/ In the @MobileDevMemo 2020 mobile advertising predictions post, I posit that D2C ad spend may drop by as much as 50% in Q2 2020. FB revealed in December that app-to-web campaigns will be governed by ATT opt in, severely limiting campaign efficiency https://t.co/0llZjphmHN
3/ FB had only previously discussed ATT in terms of app campaign relevance. This new revelation likely stemmed from further instructions from Apple following FB's initial guidance https://t.co/ijoaFyXml6
4/ FB affirmed in Dec that app-to-web campaigns will be: conversion event limited, aggregated at campaign level, and limited wrt attribution windows (default: 7-day click). This effectively replicates the privacy treatment of app campaigns on app-to-web campaigns
5/ Adam Lovallo from https://t.co/baV6VrUW7E describes 28-day click / 1-day view the "gold standard" for D2C. Why would FB change the default to 7-day? Because it is aggregating conversions at the campaign level -- universally, with what it is calling Aggregated Event Measurement
6/ This means that the intel that many D2C / ecomm consultants and agencies are dispensing around the conversions API (CAPI) being a panacea here for conversions collection / targeting is invalid unless the user opts in. Conversions are being aggregated at the campaign level
7/ Why is this important? Few reasons. First -- just as with for apps -- the user-centric monetization behavior data that drives campaign performance through personalization will be severely diminished. How much is that worth? FB says 50% of CPM https://t.co/IXxISE3bwh
8/ Second: 7-day click will simply drop a lot of conversions. So not only is targeting losing a substantial amount of precision (bc FB will lose visibility into who spends money on D2C ads & thus should be targeted) but measurement will suffer from loss of data
9/ How should D2C and ecomm advertisers prepare? There are no "quick tips" or clever tricks here: this is a tectonic shift in digital advertising. Sure, implement CAPI -- why not. But pivoting through this requires making fundamental changes to advertising strategy
10/ Understanding the impact of these changes requires acknowledging that the D2C category really only rose to prominence as a result of directly-attributable campaigns on FB & other channels that provided for user-centric monetization profiles / targeting https://t.co/DTRShHDpJ4
11/ When that evaporates w campaign-level aggregation, so does much of the opportunity. eComm & D2C advertisers must wrap their arms around as much first party data as possible to preserve the link. This article from Common Thread provides helpful guidance https://t.co/u9mfbtny58

More from Marketing

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
@franciscodeasis https://t.co/OuQaBRFPu7
Unfortunately the "This work includes the identification of viral sequences in bat samples, and has resulted in the isolation of three bat SARS-related coronaviruses that are now used as reagents to test therapeutics and vaccines." were BEFORE the


chimeric infectious clone grants were there.https://t.co/DAArwFkz6v is in 2017, Rs4231.
https://t.co/UgXygDjYbW is in 2016, RsSHC014 and RsWIV16.
https://t.co/krO69CsJ94 is in 2013, RsWIV1. notice that this is before the beginning of the project

starting in 2016. Also remember that they told about only 3 isolates/live viruses. RsSHC014 is a live infectious clone that is just as alive as those other "Isolates".

P.D. somehow is able to use funds that he have yet recieved yet, and send results and sequences from late 2019 back in time into 2015,2013 and 2016!

https://t.co/4wC7k1Lh54 Ref 3: Why ALL your pangolin samples were PCR negative? to avoid deep sequencing and accidentally reveal Paguma Larvata and Oryctolagus Cuniculus?