@blotoutio/providers-google-ads-clicks-sdk 1.70.0 → 1.70.1

package/index.cjs.js

@@ -1012,7 +1012,7 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     var _a, _b;
     const result = {
         isFired: false,
-        sdkVersion: "1.70.0" ,
+        sdkVersion: "1.70.1" ,
     };
     const tagId = manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['tagId'];
     if (!eventName || !window.gtag || !tagId) {
@@ -1020,7 +1020,18 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     }
     const shouldLoadSDK = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1' ||
         (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['dynamicRemarketingEnabled']) === '1';
-    if (!shouldLoadSDK || !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId])) {
+    const isDataManager = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['apiVersion']) === '2';
+    /*
+     * v1 has to know gtag.js actually loaded. Google does no cross-source dedup
+     * there, so the hybrid flow sends each conversion from one side only: the edge
+     * skips its server conversion whenever isFired is true, and a queued event that
+     * never flushed would be lost on both paths. v2 removes that reason — both
+     * sides always send and Google dedups on transactionId — so we hand the event
+     * to the gtag queue and let it flush whenever gtag.js arrives, rather than
+     * dropping every conversion that lands while the script is still in flight.
+     */
+    if (!shouldLoadSDK ||
+        (!isDataManager && !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId]))) {
         return result;
     }
     const resolvedPageUrl = pageUrl || ((_b = window.location) === null || _b === void 0 ? void 0 : _b.href);
@@ -1028,9 +1039,23 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     sendDynamicRemarketingEvent(eventName, manifestVariables, data, resolvedPageUrl);
     // Fire conversion event if loadSDK is enabled and conversion label exists
     if ((manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1') {
+        /*
+         * No label means the row is mapped to an import-for-clicks conversion
+         * action, which has no tag snippet and so nothing for gtag to send to. Those
+         * rows are server-only by design (they are how a v1 server-only mapping
+         * migrates to v2), so skip the browser conversion and leave the upload to
+         * the edge. Dynamic remarketing above is keyed to the tag id, not a label,
+         * and still fires.
+         */
         const conversionLabel = getConversionLabel(eventName, manifestVariables);
         if (conversionLabel) {
-            const isDataManager = manifestVariables['apiVersion'] === '2';
+            /*
+             * On v2 the browser is the primary source of user data: Google now accepts
+             * user-provided data from the tag, Data Manager and the API at once, so
+             * there is no adjustment upload to attach it server-side. Consent is
+             * handled by Consent Mode — `init` sets ad_user_data/ad_personalization
+             * from the user's consent, and gtag withholds user data when they're denied.
+             */
             // On unless a super admin turns it off for the channel — setting user data
             // here appears to cost the account's v1 conversion actions their enhanced
             // conversions coverage. v1 keeps following the customer's own EC setting.

package/index.js

@@ -1013,7 +1013,7 @@ var ProvidersGoogleAdsClicksSdk = (function () {
         var _a, _b;
         const result = {
             isFired: false,
-            sdkVersion: "1.70.0" ,
+            sdkVersion: "1.70.1" ,
         };
         const tagId = manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['tagId'];
         if (!eventName || !window.gtag || !tagId) {
@@ -1021,7 +1021,18 @@ var ProvidersGoogleAdsClicksSdk = (function () {
         }
         const shouldLoadSDK = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1' ||
             (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['dynamicRemarketingEnabled']) === '1';
-        if (!shouldLoadSDK || !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId])) {
+        const isDataManager = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['apiVersion']) === '2';
+        /*
+         * v1 has to know gtag.js actually loaded. Google does no cross-source dedup
+         * there, so the hybrid flow sends each conversion from one side only: the edge
+         * skips its server conversion whenever isFired is true, and a queued event that
+         * never flushed would be lost on both paths. v2 removes that reason — both
+         * sides always send and Google dedups on transactionId — so we hand the event
+         * to the gtag queue and let it flush whenever gtag.js arrives, rather than
+         * dropping every conversion that lands while the script is still in flight.
+         */
+        if (!shouldLoadSDK ||
+            (!isDataManager && !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId]))) {
             return result;
         }
         const resolvedPageUrl = pageUrl || ((_b = window.location) === null || _b === void 0 ? void 0 : _b.href);
@@ -1029,9 +1040,23 @@ var ProvidersGoogleAdsClicksSdk = (function () {
         sendDynamicRemarketingEvent(eventName, manifestVariables, data, resolvedPageUrl);
         // Fire conversion event if loadSDK is enabled and conversion label exists
         if ((manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1') {
+            /*
+             * No label means the row is mapped to an import-for-clicks conversion
+             * action, which has no tag snippet and so nothing for gtag to send to. Those
+             * rows are server-only by design (they are how a v1 server-only mapping
+             * migrates to v2), so skip the browser conversion and leave the upload to
+             * the edge. Dynamic remarketing above is keyed to the tag id, not a label,
+             * and still fires.
+             */
             const conversionLabel = getConversionLabel(eventName, manifestVariables);
             if (conversionLabel) {
-                const isDataManager = manifestVariables['apiVersion'] === '2';
+                /*
+                 * On v2 the browser is the primary source of user data: Google now accepts
+                 * user-provided data from the tag, Data Manager and the API at once, so
+                 * there is no adjustment upload to attach it server-side. Consent is
+                 * handled by Consent Mode — `init` sets ad_user_data/ad_personalization
+                 * from the user's consent, and gtag withholds user data when they're denied.
+                 */
                 // On unless a super admin turns it off for the channel — setting user data
                 // here appears to cost the account's v1 conversion actions their enhanced
                 // conversions coverage. v1 keeps following the customer's own EC setting.

package/index.mjs

@@ -1010,7 +1010,7 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     var _a, _b;
     const result = {
         isFired: false,
-        sdkVersion: "1.70.0" ,
+        sdkVersion: "1.70.1" ,
     };
     const tagId = manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['tagId'];
     if (!eventName || !window.gtag || !tagId) {
@@ -1018,7 +1018,18 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     }
     const shouldLoadSDK = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1' ||
         (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['dynamicRemarketingEnabled']) === '1';
-    if (!shouldLoadSDK || !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId])) {
+    const isDataManager = (manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['apiVersion']) === '2';
+    /*
+     * v1 has to know gtag.js actually loaded. Google does no cross-source dedup
+     * there, so the hybrid flow sends each conversion from one side only: the edge
+     * skips its server conversion whenever isFired is true, and a queued event that
+     * never flushed would be lost on both paths. v2 removes that reason — both
+     * sides always send and Google dedups on transactionId — so we hand the event
+     * to the gtag queue and let it flush whenever gtag.js arrives, rather than
+     * dropping every conversion that lands while the script is still in flight.
+     */
+    if (!shouldLoadSDK ||
+        (!isDataManager && !((_a = window.google_tag_manager) === null || _a === void 0 ? void 0 : _a[tagId]))) {
         return result;
     }
     const resolvedPageUrl = pageUrl || ((_b = window.location) === null || _b === void 0 ? void 0 : _b.href);
@@ -1026,9 +1037,23 @@ const tag = ({ data, eventName, eventId, manifestVariables, destination, pageUrl
     sendDynamicRemarketingEvent(eventName, manifestVariables, data, resolvedPageUrl);
     // Fire conversion event if loadSDK is enabled and conversion label exists
     if ((manifestVariables === null || manifestVariables === void 0 ? void 0 : manifestVariables['loadSDK']) === '1') {
+        /*
+         * No label means the row is mapped to an import-for-clicks conversion
+         * action, which has no tag snippet and so nothing for gtag to send to. Those
+         * rows are server-only by design (they are how a v1 server-only mapping
+         * migrates to v2), so skip the browser conversion and leave the upload to
+         * the edge. Dynamic remarketing above is keyed to the tag id, not a label,
+         * and still fires.
+         */
         const conversionLabel = getConversionLabel(eventName, manifestVariables);
         if (conversionLabel) {
-            const isDataManager = manifestVariables['apiVersion'] === '2';
+            /*
+             * On v2 the browser is the primary source of user data: Google now accepts
+             * user-provided data from the tag, Data Manager and the API at once, so
+             * there is no adjustment upload to attach it server-side. Consent is
+             * handled by Consent Mode — `init` sets ad_user_data/ad_personalization
+             * from the user's consent, and gtag withholds user data when they're denied.
+             */
             // On unless a super admin turns it off for the channel — setting user data
             // here appears to cost the account's v1 conversion actions their enhanced
             // conversions coverage. v1 keeps following the customer's own EC setting.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blotoutio/providers-google-ads-clicks-sdk",
-  "version": "1.70.0",
+  "version": "1.70.1",
   "description": "Google Ads Browser SDK for EdgeTag",
   "author": "Blotout",
   "license": "MIT",