Tag: Privacy

  • Google Clarifies Age Estimation Ads Policy for Advertisers

    Google Clarifies Age Estimation Ads Policy for Advertisers

    I’m watching Google update its advertising policy to make clearer how certain ads are limited while the company estimates a user’s age. The change gives advertisers more transparency as Google expands its age assurance technology worldwide.

    What I’m seeing: Google has renamed its Default Ads Treatment policy to “Categories restricted while Google is estimating a user’s age.” To me, that wording matters because it makes the policy sound less like a permanent restriction and more like a temporary safeguard while Google’s systems work out whether a user is old enough to see certain types of ads.

    What’s changing: I see three main updates here: the policy has a clearer name, the language now emphasizes that these protections are interim measures during the age estimation process, and enforcement remains unchanged.

    What’s different: Google has also narrowed the list of ad categories restricted while a user’s age is being estimated. Previously, the restricted categories included adult content and pornography, alcohol, gambling, and shocking content.

    Under the updated policy, I now see only three restricted categories: adult content and pornography, alcohol, and gambling. Shocking content no longer appears on that restricted list.

    Why I care: This update does not introduce new advertising restrictions, but it does make the policy easier to understand. For advertisers in affected verticals, the key takeaway is that these limits are tied to Google’s age estimation process, not a broader or permanent policy shift.

    The bottom line: I do not see any operational change for advertisers, but Google’s updated policy makes it much clearer that restrictions on adult, alcohol, and gambling ads are temporary safeguards while a user’s age is being estimated.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • Enhance Your Data Strategy with Server-Side Tagging Solutions

    Enhance Your Data Strategy with Server-Side Tagging Solutions

    I’ve been noticing the rapid transformation in how brands are tracking user behavior online. With privacy laws tightening and browser extensions increasingly blocking data, the demand for cleaner data from ad platforms is higher than ever. This change urged me to explore server-side tagging as a solution.

    By implementing server-side tagging, I’ve managed to reduce data loss while collecting cleaner, privacy-compliant data. This approach is invaluable, especially considering the experiences I’ve had with providers like Elevar and Littledata.

    So, what exactly is server-side tagging, and in which situations does it really shine? Let’s dive into the details!

    What is server-side tagging?

    Traditionally, tracking scripts ran directly in the browser. However, with server-side tagging, these scripts operate on a server I control, giving me more control over data processing.

    Here’s how it works: instead of sending data straight to multiple third parties from the browser, events are sent to a first-party server endpoint, often using a Google Tag Manager server-side container. The server then processes, enriches, and forwards this data to tools like Meta and Google Analytics.

    This setup provides benefits such as more data control, a cleaner page performance, and better compliance with privacy laws.

    Moreover, server-side tagging grants me the flexibility to enrich and transform data before it reaches ad platforms, standardizing event names, filtering out low-quality events, and adding custom parameters for better audience segmentation.

    Is server-side tagging right for you?

    While server-side tagging isn’t a one-size-fits-all solution, many brands find it essential, particularly if you:

    You need to meet strict privacy or compliance requirements

    Server-side setups allow for greater control over how data is processed and shared, supporting compliance with regulations like GDPR and CCPA.

    ```json
{
  "alt": "The CapmatchOne logo with a gradient circle and bold text.",
  "caption": "Discover innovation with the CapmatchOne logo, featuring sleek typography and a modern gradient circle.",
  "description": "The CapmatchOne logo features bold, modern typography coupled with a gradient circle, symbolizing connection and innovation. The sleek design conveys a sense of progress and creativity. This image can be used for branding or promotional purposes, appealing to audiences interested in innovative solutions and forward-thinking designs."
}
```

    You want faster website performance

    In my experience, client-side tracking can slow your page down, but server-side tagging shifts data processing to the server, resulting in faster websites.

    You want more accurate tracking (despite ad blockers)

    Ad blockers can hinder client-side scripts, but server-side tagging circumvents many of these restrictions, making your data collection more reliable.

    You’re investing heavily in paid media

    For those heavily invested in platforms like Meta and Google Ads, achieving better data accuracy can significantly impact return on ad spend.

    How to implement server-side tagging

    When it comes to implementing server-side tagging, you have two main options: building it internally or using a service provider.

    Option 1: Internal setup

    Choosing an internal setup gives me complete control but requires technical expertise and ongoing maintenance. This involves setting up a GTM server-side container and adding logic for data processing.

    Option 2: Use a server-side tagging service

    Platforms like Elevar and Littledata offer turnkey solutions that integrate seamlessly with existing tools, allowing me to focus on strategy rather than technicalities.

    Our direct experience: Littledata vs. Elevar

    In my experience with Littledata and Elevar, each caters to different needs. Littledata is ideal for emerging brands with simpler tech stacks, while Elevar is suitable for those outgrowing entry-level solutions.

    Investing in server-side tagging has transformed how I handle data, ensuring that I remain compliant with privacy laws while boosting site performance and data reliability across all my platforms.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • OpenAI Enhances Privacy with New ChatGPT Ad Features

    OpenAI Enhances Privacy with New ChatGPT Ad Features

    I’ve been following the latest updates from OpenAI, and they recently made some significant changes to their privacy policy, especially with the introduction of ads in ChatGPT. These updates are designed to allow advertisers to run personalized ads while ensuring that our chats remain private and secure.

    OpenAI shared these updates with ChatGPT users, detailing how ads will function within the platform and clarifying what data is accessible to advertisers. It’s a refreshing assurance that our personal interactions remain confidential.

    Why this matters to me. Privacy is paramount, and OpenAI emphasizes that personal chats and histories remain shielded from advertisers. They utilize anonymized engagement signals for ad personalization, ensuring advertisers can target relevant users without accessing sensitive information.

    This method allows advertisers to evaluate the performance of their ads within a privacy-first framework, fostering user trust.

    Ads in ChatGPT For users like me on Free and Go plans, ads might start appearing, but if you opt for paid tiers like Plus, Pro, Enterprise, Business, and Education, you can enjoy an ad-free experience. OpenAI promises clear labeling and separation of ads from chatbot responses.

    Importantly, the content generated by ChatGPT remains unbiased and unaffected by these advertisements.

    How ad targeting is handled. OpenAI uses in-platform signals such as ad interactions to personalize ads, but advertisers do not get access to our conversations, chat histories, or personal information.

    ```json
{
  "alt": "OpenAI updates its privacy policy, outlining contact syncing options and ad placements.",
  "caption": "Stay informed: OpenAI's updated privacy policy introduces new ad placements and contact syncing features, enhancing user experience and transparency.",
  "description": "This image contains a document titled 'Updates to OpenAI's Privacy Policy'. It details changes such as the option to sync contacts on OpenAI services and the introduction of ads for Free and Go plans. The update reassures users that ads won't affect ChatGPT's answers and clarifies policies on ad personalization and data privacy. Additional details cover age-appropriate safeguards for teens, and transparency about data usage and features like Atlas and Sora 2."
}
```

    Advertisers receive only aggregated metrics like total views or clicks, ensuring our personal data stays protected.

    Additional privacy updates A new feature allows for optional contact syncing, helping us connect with friends who also use OpenAI services. It’s up to us whether to enable this feature.

    They also provided more transparency on data storage durations, processing methods, and user control options, helping us understand our data management better.

    Safety and product enhancements. The update encompasses new safety tools and age prediction systems aimed at ensuring a safer environment for teenagers. Documentation for new features like Atlas, Sora 2, and parental controls for teen accounts has also been included.

    The bottom line. With the expansion of advertising in ChatGPT, OpenAI is committed to maintaining strict boundaries concerning user privacy, offering advertisers valuable insights without infringing on personal conversations or data.

    This update was first spotted by Paid Media expert Arpan Banerjee, who shared insights on LinkedIn. It’s a promising move towards privacy-centric advertising in AI-powered platforms.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot