crealytics.com
Open in
urlscan Pro
52.148.193.10
Public Scan
URL:
https://crealytics.com/resources/blog/consumer-privacy-and-retail-media-networks/
Submission: On November 03 via api from US — Scanned from NL
Submission: On November 03 via api from US — Scanned from NL
Form analysis
3 forms found in the DOMPOST /resources/blog/consumer-privacy-and-retail-media-networks/
<form method="post" enctype="multipart/form-data" id="gform_41" action="/resources/blog/consumer-privacy-and-retail-media-networks/">
<div class="gform_body gform-body">
<div id="gform_fields_41" class="gform_fields top_label form_sublabel_below description_below">
<div id="field_41_1" class="gfield gfield--width-half gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_41_1"><label class="gfield_label" for="input_41_1">First Name<span
class="gfield_required"><span class="gfield_required gfield_required_asterisk">*</span></span></label>
<div class="ginput_container ginput_container_text"><input name="input_1" id="input_41_1" type="text" value="" class="large" aria-required="true" aria-invalid="false"> </div>
</div>
<div id="field_41_3" class="gfield gfield--width-half gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_41_3"><label class="gfield_label" for="input_41_3">Last Name<span
class="gfield_required"><span class="gfield_required gfield_required_asterisk">*</span></span></label>
<div class="ginput_container ginput_container_text"><input name="input_3" id="input_41_3" type="text" value="" class="large" aria-required="true" aria-invalid="false"> </div>
</div>
<div id="field_41_5" class="gfield gfield--width-half gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_41_5"><label class="gfield_label" for="input_41_5">Work Email<span
class="gfield_required"><span class="gfield_required gfield_required_asterisk">*</span></span></label>
<div class="ginput_container ginput_container_email">
<input name="input_5" id="input_41_5" type="text" value="" class="large" aria-required="true" aria-invalid="false">
</div>
</div>
<div id="field_41_4" class="gfield gfield--width-half gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_41_4"><label class="gfield_label" for="input_41_4">Company Name<span
class="gfield_required"><span class="gfield_required gfield_required_asterisk">*</span></span></label>
<div class="ginput_container ginput_container_text"><input name="input_4" id="input_41_4" type="text" value="" class="large" aria-required="true" aria-invalid="false"> </div>
</div>
<div id="field_41_6" class="gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_41_6"><label class="gfield_label" for="input_41_6">Comments</label>
<div class="ginput_container"><input name="input_6" id="input_41_6" type="text" value=""></div>
<div class="gfield_description" id="gfield_description_41_6">This field is for validation purposes and should be left unchanged.</div>
</div>
</div>
</div>
<div class="gform_footer top_label"> <input type="submit" id="gform_submit_button_41" class="gform_button button" value="Submit" onclick="if(window["gf_submitting_41"]){return false;} window["gf_submitting_41"]=true; "
onkeypress="if( event.keyCode == 13 ){ if(window["gf_submitting_41"]){return false;} window["gf_submitting_41"]=true; jQuery("#gform_41").trigger("submit",[true]); }">
<input type="hidden" class="gform_hidden" name="is_submit_41" value="1">
<input type="hidden" class="gform_hidden" name="gform_submit" value="41">
<input type="hidden" class="gform_hidden" name="gform_unique_id" value="">
<input type="hidden" class="gform_hidden" name="state_41" value="WyJbXSIsIjljZDc3OTYwMDEzZWQxYWI3M2NjMjg4MTlhNTA1NDUyIl0=">
<input type="hidden" class="gform_hidden" name="gform_target_page_number_41" id="gform_target_page_number_41" value="0">
<input type="hidden" class="gform_hidden" name="gform_source_page_number_41" id="gform_source_page_number_41" value="1">
<input type="hidden" name="gform_field_values" value="">
</div>
<p style="display: none !important;"><label>Δ<textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100"></textarea></label><input type="hidden" id="ak_js_1" name="ak_js" value="1667496408029">
<script>
document.getElementById("ak_js_1").setAttribute("value", (new Date()).getTime());
</script>
</p>
</form>
POST https://crealytics.com/wp-comments-post.php
<form action="https://crealytics.com/wp-comments-post.php" method="post" id="ast-commentform" class="comment-form">
<p class="comment-notes"><span id="email-notes">Your email address will not be published.</span> <span class="required-field-message" aria-hidden="true">Required fields are marked <span class="required" aria-hidden="true">*</span></span></p>
<div class="ast-row comment-textarea">
<fieldset class="comment-form-comment">
<div class="comment-form-textarea ast-col-lg-12"><label for="comment" class="screen-reader-text">Type here..</label><textarea id="comment" name="comment" placeholder="Type here.." cols="45" rows="8" aria-required="true"></textarea></div>
</fieldset>
</div>
<div class="ast-comment-formwrap ast-row">
<p class="comment-form-author ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="author" class="screen-reader-text">Name*</label><input id="author" name="author" type="text" value="" placeholder="Name*" size="30"
aria-required="true"></p>
<p class="comment-form-email ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="email" class="screen-reader-text">Email*</label><input id="email" name="email" type="text" value="" placeholder="Email*" size="30"
aria-required="true"></p>
<p class="comment-form-url ast-col-xs-12 ast-col-sm-12 ast-col-md-4 ast-col-lg-4"><label for="url"><label for="url" class="screen-reader-text">Website</label><input id="url" name="url" type="text" value="" placeholder="Website" size="30"></label>
</p>
</div>
<p class="comment-form-cookies-consent"><input id="wp-comment-cookies-consent" name="wp-comment-cookies-consent" type="checkbox" value="yes"> <label for="wp-comment-cookies-consent">Save my name, email, and website in this browser for the next time
I comment.</label></p>
<p class="form-submit"><input name="submit" type="submit" id="submit" class="submit" value="Post Comment »"> <input type="hidden" name="comment_post_ID" value="28538" id="comment_post_ID">
<input type="hidden" name="comment_parent" id="comment_parent" value="0">
</p>
<p style="display: none;"><input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="20e53aebfc"></p>
<p style="display: none !important;"><label>Δ<textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100"></textarea></label><input type="hidden" id="ak_js_2" name="ak_js" value="1667496408029">
<script>
document.getElementById("ak_js_2").setAttribute("value", (new Date()).getTime());
</script>
</p>
</form>
POST /resources/blog/consumer-privacy-and-retail-media-networks/
<form method="post" enctype="multipart/form-data" id="gform_2" class="gf_simple_horizontal gform_legacy_markup" action="/resources/blog/consumer-privacy-and-retail-media-networks/">
<div class="gform_body gform-body">
<ul id="gform_fields_2" class="gform_fields top_label form_sublabel_below description_below">
<li id="field_2_2" class="gfield gf_inline field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_2_2"><label class="gfield_label" for="input_2_2">Email</label>
<div class="ginput_container ginput_container_email">
<input name="input_2" id="input_2_2" type="text" value="" class="medium" placeholder="Email" aria-invalid="false">
</div>
</li>
<li id="field_2_3" class="gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible" data-js-reload="field_2_3"><label class="gfield_label" for="input_2_3">Comments</label>
<div class="ginput_container"><input name="input_3" id="input_2_3" type="text" value=""></div>
<div class="gfield_description" id="gfield_description_2_3">This field is for validation purposes and should be left unchanged.</div>
</li>
</ul>
</div>
<div class="gform_footer top_label"> <input type="submit" id="gform_submit_button_2" class="gform_button button" value="Subscribe" onclick="if(window["gf_submitting_2"]){return false;} window["gf_submitting_2"]=true; "
onkeypress="if( event.keyCode == 13 ){ if(window["gf_submitting_2"]){return false;} window["gf_submitting_2"]=true; jQuery("#gform_2").trigger("submit",[true]); }">
<input type="hidden" class="gform_hidden" name="is_submit_2" value="1">
<input type="hidden" class="gform_hidden" name="gform_submit" value="2">
<input type="hidden" class="gform_hidden" name="gform_unique_id" value="">
<input type="hidden" class="gform_hidden" name="state_2" value="WyJbXSIsIjljZDc3OTYwMDEzZWQxYWI3M2NjMjg4MTlhNTA1NDUyIl0=">
<input type="hidden" class="gform_hidden" name="gform_target_page_number_2" id="gform_target_page_number_2" value="0">
<input type="hidden" class="gform_hidden" name="gform_source_page_number_2" id="gform_source_page_number_2" value="1">
<input type="hidden" name="gform_field_values" value="">
</div>
<p style="display: none !important;"><label>Δ<textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100"></textarea></label><input type="hidden" id="ak_js_3" name="ak_js" value="1667496408032">
<script>
document.getElementById("ak_js_3").setAttribute("value", (new Date()).getTime());
</script>
</p>
</form>
Text Content
Skip to content * Performance Advertising * Agency Services * Paid Search * Paid Social & Programmatic * Amazon & Marketplace Services * Measurement Solutions * CLV-Centric Advertising * Incrementality + Attribution * Technology Solutions * CLV Platform * Search Platform * Retail Media * Resources * Webinars * Careers * About Us Menu * Performance Advertising * Agency Services * Paid Search * Paid Social & Programmatic * Amazon & Marketplace Services * Measurement Solutions * CLV-Centric Advertising * Incrementality + Attribution * Technology Solutions * CLV Platform * Search Platform * Retail Media * Resources * Webinars * Careers * About Us Contact Us * Blog GUIDE TO NAVIGATING CONSUMER PRIVACY AND RETAIL MEDIA NETWORKS * Emily Hunt * October 28, 2022 Experts predict that the retail media industry will drive over $60 billion in revenue by the end of 2024 — nearly triple the amount at year-end 2020. With this accelerated growth, eCommerce brands are quickly adopting retail media platforms to monetize and deepen relationships with brand partners. Yet, the rush to introduce retail media partners leaves eCommerce professionals struggling with new questions related to data privacy and using first and third party data. With so many moving parts and little documentation to guide them, retailers face uncertainty in addressing both the legal and practical aspects of managing consumer data privacy. CONSUMER PRIVACY: UNCERTAIN LANDSCAPE With the deprecation of cookies on the horizon and growing privacy regulations, first party data has long been retailers’ most powerful asset. Yet, data security has become pressing particularly with the growth of retail media. Retailers have collected vast amounts of first party shopper data through loyalty programs and web purchase behaviors. The promise of retail media is to activate that very data throughout the funnel. Retailers, therefore, need to leverage advertising technology from many different third party vendors to achieve a rapid time-to-market. However, data shared with outside parties increases the chance of compromising shoppers’ privacy — a risk for even the largest eCommerce brands. Instacart, for instance, suffered a security incident after two employees working for a third party vendor viewed more shopper profiles than necessary. Regulations like GDPR (General Data Protection Regulation) and CPPA (California Consumer Privacy Act) have stemmed from such issues, as has Google’s announcement that it will sunset cookies on Chrome. Without third party data, brands must turn to retailers’ valuable consumer data to continue delivering targeted, personalized ads. Retailers seeking to monetize from this opportunity must build a retail media network, which few, aside from behemoths like Amazon and Walmart, can afford to build in-house. Instead, most need to team up with a retail media platform, which carries a new set of challenges related to consumer privacy and compliance. RETAIL MEDIA PRIVACY COMPLIANCE: 5 GUIDING PRINCIPLES 1. EACH COOKIE IS ONE TOO MANY Privacy advocates take aim at the cookie for two reasons: * Websites and servers can access data on shoppers’ personal devices. * Access allows tracking of an individual’s browsing history – not only on the same site but across the web. That’s why European laws require retailers to get user consent for all non-necessary cookies. Cookies used for marketing purposes (such as retargeting) are not considered essential, and thus need permissions, which many users reject. In the best case, regardless of geography, your adtech partners don’t introduce or use any cookies. If they come into play, make sure your partner documents every single cookie and its purpose. This way, your website is transparent about cookies and asks for user permission when required by law. Since incorporating the retailers’ own personalization and audience targeting criteria is a best practice for retail media platforms, additional third party data would bring you limited benefits. Users consent to third party cookies for personalized ads 2. SEEK SERVER-SIDE INTEGRATION Regulators and shoppers are increasingly suspicious when webpages access third-party servers, which may profile and collect personal behavior for future targeting. To minimize exposing your shoppers’ personal information, integrate third party technology on the server side as much as possible. When you integrate on the client-side using HTML tags, browsers will expose shopper data to third parties, such as their IP Address. This practice may fall victim to privacy regulation (as in Europe) or tracking prevention. In short: server-side integrations provide better protection of user data. Using backend APIs also helps as your partners receive less sensitive information to protect or treat with care. 3. APPLAUD ANONYMITY Make sure your retail media vendor does not expose data sets that can identify individuals. Reporting should only expose anonymous and highly aggregated data to advertisers, with no personally identifying information (PII). For example, technology may expose information related to a selected cohort of women in their mid 30’s. However, it should not have specifics on me, you, or other persons. 4. ENSURE ENCRYPTION With your enviable ability to collect and access many data points, you want to ensure that it’s safe. To prevent leakage of PII, get confirmation that your retail media vendor processes personal data with the highest security standards. Look for encrypted data with hashed values. This approach also minimizes the negative impact of data breaches such as that experienced by Instacart and other retail vendors. 5. DEDICATE TO DATENSPARSAMKEIT Literally: data thriftiness. This German term refers to how a business should approach capturing and storing data. Retailers should only handle the data that they need. In the past, there was a push to capture as much consumer data as possible, with the understanding that it may be useful for future marketing efforts. A more modern approach would be to economize data capture to only collect elements necessary for the sake of privacy compliance and consumer benefit. In the case of building a retail media network, your adtech partner should require just a minimum amount of data to work properly. NEXT STEPS Future-proofing your retail media technology will help you adhere to international compliance laws, address consumers’ data privacy concerns, and build trust. In evaluating a retail media solution that follows these principles, consider Crealytics Middleware retail media solution. The simple backend API integrates directly into your ad server, introducing zero third party cookies. All personally identifiable data is 100% hashed. The retailer fully controls shopper data, not the adtech solution. By introducing Crealytics Middleware to your technology platform now, you don’t need to worry about changing your technology later as data privacy laws heighten. Watch the video to see how Crealytics Middleware works READY TO BUILD YOUR RETAIL MEDIA BUSINESS? Contact our team at Crealytics. JUST GETTING INTO RETAIL MEDIA? Download our glossary for the latest industry lingo. "*" indicates required fields First Name* Last Name* Work Email* Company Name* Comments This field is for validation purposes and should be left unchanged. Δ LEAVE A COMMENT CANCEL REPLY Your email address will not be published. Required fields are marked * Type here.. Name* Email* Website Save my name, email, and website in this browser for the next time I comment. Δ READ MORE ARTICLES Blog GUIDE TO NAVIGATING CONSUMER PRIVACY AND RETAIL MEDIA NETWORKS Blog YOUR ULTIMATE RETAIL MEDIA GLOSSARY Blog HOW DATA ACTIVATION CAN HELP YOU CONQUER MODERN DIGITAL MARKETING GIVE YOUR INBOX A PEP TALK. Bite-sized insights straight to your email, from measurement tips to marketplace strategies. * Email * Comments This field is for validation purposes and should be left unchanged. Δ PERFORMANCE ADVERTISING * Paid Search * Paid Social & Programmatic * Amazon & Marketplace Services * CLV-Centric Advertising * Incrementality + Attribution * Search Platform RETAIL MEDIA * Retail Media RESOURCES * Resources * Webinars COMPANY * About Us * Careers SUPPORT * Contact Us * Privacy Policy * Imprint Privacy Policy (Search Platform) Notifications