Why Uploading Conversions to Google Ads in Parallel to Pixel Tracking Is a Bad Idea (and How Pixel Manager Already Solves the Problem)
Marketers have recently been bombarded with advice from some tracking code providers promoting a “conversion upload” solution - a feature meant to recover conversions supposedly lost due to Apple's iPhone privacy updates.
Their solution uses the simple idea to rename Google's gclid parameter and process it under a different name, thus bypassing Apple's Intelligent Tracking Prevention (ITP) restrictions, which filters out known tracking parameters.
At first, this sounds like a clever fix. But here's the catch that many overlook:
⚠️ These providers suggest uploading conversions in parallel to your normal, pixel-based Google Ads conversion tracking.
And that's exactly where things go wrong.
The Duplication Trap - How You End Up Counting Conversions Twice
The Google Ads conversion upload feature doesn't work the same way as Facebook CAPI or similar server-side tracking solutions.
When you upload conversions to Google Ads via the import feature:
- Google treats the upload as a separate conversion action.
- Even if the same transaction ID is sent, Google does not deduplicate across conversion actions.
- This means every sale recorded by your pixel gets counted again in your import data.
The result?
👉 Inflated conversion numbers, distorted return-on-ad-spend (ROAS), and misleading campaign optimization signals.
So instead of fixing lost conversions, these “parallel uploads” create artificial ones.
Google Already Has Built-In Solutions for Lost Tracking Cookies
Since Apple introduced Intelligent Tracking Prevention (ITP) in 2017, Google has been continuously improving how it models and attributes conversions from Apple devices - within privacy limits.
Here's what's already working for you:
- Enhanced Conversions: Uses hashed first-party data to securely connect conversions to ads. Learn more about Enhanced Conversions
gbraidandwbraidparameters: Help Google identify Apple-originating traffic and conversions more precisely. Learn more about gbraid/wbraid- Conversion modeling: Estimates conversions that cannot be directly observed because of privacy restrictions. Learn more about Google's conversion modeling
- Google Tag Gateway: A server-side tagging solution that enhances data accuracy and privacy compliance. Learn more about Google Tag Gateway
In short, Google Ads already models lost conversions automatically. There's no need to manually upload parallel conversions. Doing so just makes your data less accurate.
Scaremongering Marketing Tactics to Avoid
Some tracking providers exaggerate Apple's planned tracking restrictions in the upcoming iOS updates. There are planned and documented changes like "Browsing in Safari gets even more private with advanced fingerprinting protection extending to all browsing by default.". But none of these changes go as far as what some vendors claim.
These tactics often rely on scaremongering, creating fear around iPhone tracking limitations to sell a solution that isn't one.
Here are some quotes from industry experts debunking these myths:
Remember also that ad tech isn't sitting idly by waiting to see what Apple does. Many vendors have been optimizing for data degradation since ITP1 in 2017 (and some even further back to 2003 when Safari 1.0 was introduced with third-party cookie blocking enabled by the default cookie policy!).
So keep a level head. Don't make hasty decisions based on rumors about Safari traffic. Don't switch your marketing stack architecture just because you're promised you'll retain 5% more identifiers or conversions.
source: Simo Ahava
The safari update for iOS 26 went live 2 days ago and the stripping of the IDs were not included from what I can see. There is a setting now to enable 'Tracking & Fingerprint Protection' for all browsing. But I tested with this and the
gclidis not getting stripped and the cookie is still being set.
(source: anoymous, private forum)
I can confirm all.
gclidnot removed from URL
(source: anoymous, private forum)
Risk of Using Workarounds Like Cookie Renaming
Using cookie renaming to bypass ITP restrictions could turn out to be a risky strategy:
Apple continuously updates its privacy measures. A workaround that works today may be blocked in future updates. The even greater risk here is that it might block not only the renamed cookie but the tracking script entirely, leading to a complete loss of tracking capabilities.
We believe it is better to work within the privacy frameworks set by platform providers like Apple and Google, rather than trying to circumvent them.
How Pixel Manager for WooCommerce Solves This the Right Way
At SweetCode, we took a different path. We focused on integrating Google's official, privacy-safe tracking enhancements directly into Pixel Manager for WooCommerce. Our Pixel Manager for WooCommerce includes:
On top of that, Google's gtag.js library - which Pixel Manager uses for Google Ads tracking - automatically supports gbraid and wbraid parameters and conversion modeling.
These are official, privacy-safe technologies that keep conversion tracking highly accurate, without risking duplication or compliance issues.
That's why we deliberately did not add any “conversion upload recovery” feature. Accuracy matters more than marketing gimmicks.
The Bottom Line
The idea of “recovering” lost conversions through cookie renaming and parallel conversion uploads may sound attractive, but it's technically flawed. Google already does that job for you, safely and intelligently.
Parallel uploading = double counting.
Pixel Manager = accuracy.
When it comes to tracking conversions, less interference means better data.
Further Reading
For a great summary of the current state of Apple's privacy changes and what they really mean for marketers, check out this article: 👉 Simmer newsletter #82 Part 2
