In our March 3 panel discussion, iOS 14, IDFA, & What It All Means for the Digital Marketing Landscape, WITHIN’s CEO Joe Yakuel was joined by Wunderkind Director of Strategy Jon Humphrey, Rockerbox Co-Founder Ron Jacobson, and WITHIN’s Integrated Media Director Michael Choi for a deep dive into what marketers can expect with the new changes launching this spring.
The privacy-first approach, while ostensibly a win for consumers who want control over their data sharing, will mean a shift in tactics for marketers who want to continue to deliver customized, tailored experiences for users. The panel’s goal was to give attendees some actionable takeaways for how to prepare for the changes.
WITHIN asked attendees to complete a short poll before the discussion began to gauge just how much awareness the audience had of the upcoming changes and their level of preparedness.
The good news is that over 56% said they are “sort of prepared” for the iOS 14 changes and the bad news is that more than a third of attendees had no plan in place at all. Let’s get into it!
Apple intends to give its users control over whether to opt in to data tracking on every app. Up until now, users had the ability to opt out of targeted ads, but this change will mean they must actively opt in via a popup screen for every app. This will cripple advertisers’ access to the IDFA, which is historically how they precisely target and track users within iOS apps.
Choi notes a deeper fallout, however. “This is not just about IDFA or about app tracking,” he says. “Even website-based conversion tracking will be impacted because Apple’s changes make it so that everyone has to play by the same rules.”
There’s a lot to digest about the upcoming changes, so we suggest you carve out some time to view the discussion in its entirety, but here are a few of the highlights and insights from the panel.
Here are some of the anticipated roadblocks the panel called out.
Expect a limited volume of metrics. “You’ll be limited in what you can report,” says Choi. “You’re going to be limited to 8 conversions and you’ll only see one of those. Really it’s not about what sort of metrics, it’s about the volume of metrics we’re going to lose.”
Modeling conversions are not created equal. Google seems to be ahead of Facebook in countering Apple’s changes with modeling data. Facebook is “building the plane as they’re flying it,” says Choi.
If you have apps, saddle up. “It’s pretty obvious that if you have apps, this is going to impact you a lot more,” according to Ron Jacobson. “If you haven’t been planning at all, you should definitely get on that. For mobile web, it’s a bit more nuanced,”
Anticipate some backtracking. “A lot of channels that have been effective won’t perform as well as they have…Campaign creation will have to change a lot as well. You have to start learning to use some of the old techniques that you have in the past … ironic that we’re getting back there,” says Jacobson.
Changes on the horizon will include a shift in established norms. Companies large and small have relied on generating large lookalike audiences in a way that will no longer be possible. “That presents a huge challenge,” says Jonathan Humphrey. “Your source audience has to be larger than it was previously to return the same efficacy.” So, what are some of the panel’s recommendations?
Rediscover your love of first-party data. “You definitely, no matter what, have to keep focusing on capturing first party data,” says Jacobson, who believes that securing audience information while they’re active on your website is a best-case scenario. “There’s some low-hanging fruit that’s worth starting off with. Simple things. That could mean promo codes, post-purchase surveys, email surveys, all these classic things that have been used for a long time are going to become more important.”
He also points to refer-a-friend campaigns and email forwarding campaigns as a way to use your existing audience to help capture more first-party data. Another tip is to make sure that users are getting value in exchange for their info. This can be a place to employ some creativity. Jacobson was surprised and impressed by a vacuum cleaner company’s persuasive offering in exchange for his phone number: an extended warranty on his purchase.
Be fast and adaptable. “We won’t know exactly how these changes impact our performance until the day it happens,” says Choi.
Humphrey notes that the absence of lookalike audiences will present a hurdle, prompting some digital soul-searching. “Are there other means for me to diversify my investments from a retargeting perspective? Now, if maybe Facebook is less attributable than it was before, am I more comfortable investing in less attributable channels over all?”
Keeping an open mind as the data rolls in and being ready and willing to make adjustments will be key.
Test, test, and test some more. “Plan to report on different events,” says Choi. “Right now if you’re able to optimize to purchase event, that’s great but the reality is that we might not have enough signals to optimize there anymore.”
He suggests gathering intel at higher levels, like awareness, traffic, add-to-cart, and website exits. It will be important to have this baseline data as a comparison after the changes occur. “Right now,” Choi emphasizes, “do that testing.”
Jacobson notes that there is no magic bullet. “Nothing is perfect. Attribution isn’t perfect, and measurement isn’t perfect. Never has been.” Needless to say, it’s important to glean what you can from all available sources. “The whole world is coming in a circle. Everything is becoming aggregate.” Ideally, Jacobson says, you will want to collect “enough different signals that you can triangulate in one location to make smart decisions.”
Yakuel related what we know about iOS 14 to what we knew about COVID-19 at this time last year and the continuous rollout of new recommendations. “We don’t know everything about iOS 14 to make all the right decisions, but I think it’s all about making improvements to what you’re doing now and making improvements as you start to see data.”
In short, as Jacobson put it, “You’re going to mess up, you’re going to screw up. Just learn from that as fast as you possibly can.”
To hear more advice from the panel and the audience Q&A session, watch the recorded event. A follow-up to this forum is in the works, so please ask any lingering questions you’d like us to cover in the next round.
Sue Cahaly is WITHIN’s Content Marketing Manager. She and her husband live outside of Boston in a house full of kids, dogs and music.
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. |