I'm trying to use the Google Ads API to create and update audiences but I'm unsure which credential I should use.

My scripts starts like this:

require 'xxxxx/vendor/autoload.php'; use Google\Ads\GoogleAds\Lib\V14\GoogleAdsClientBuilder; use Google\Ads\GoogleAds\V14\Resources\OfflineUserDataJob; use Google\Ads\GoogleAds\V14\Services\OfflineUserDataJobOperation; use Google\Ads\GoogleAds\V14\Services\AddOfflineUserDataJobOperationsResponse; use Google\Ads\GoogleAds\V14\Enums\OfflineUserDataJobTypeEnum\OfflineUserDataJobType; use Google\Ads\GoogleAds\V14\Services\UserIdentifier; use Google\Ads\GoogleAds\V14\Services\TransactionAttribute; use Google\Ads\GoogleAds\Util\V14\ResourceNames; $developerToken = 'wwwwwww'; $clientCustomerId = 'wwwwwww'; $loginCustomerId = 'wwwwwww'; 

I get the developer token from my Google Ads API so I guess, this one is the easiest to find.

I have a Google Ads account that has a XXX-XXX-XXXX format and I used it for $clientCustomerId.

=> is this correct?

I also have another ID XXX-XXX-XXXX displayed on the top left corner of my screen, I suppose it is the MCC number and I used it for $loginCustomerId. I'm not sure I have to use this one if I have the client ID.

=> Should I use the MCC id or something else?

I also have credentials for the API in my cloud console but I don't know if I have to use them here.

Thanks Laurent

I am implementing Facebook OAuth for user sign-in following facebook-login/guides/advanced/manual-flow. When the user clicks "Sign in with Facebook," a popup window opens at https://my-domain/login, which redirects to Facebook's OAuth URL (e.g., https://www.facebook.com/v21.0/dialog/oauth?...). Initially, window.opener correctly points to the parent window that opened the popup.

However, after the user completes the login (e.g., clicks "Continue as [Username]") and is redirected back to https://my-domain/login, window.opener unexpectedly becomes null. Since window.opener shouldn't become null during this process, this behavior is breaking my implementation, as I rely on window.opener.postMessage() to send the redirect URI back to the main window.

This issue occurs in all Android browsers (e.g., Chrome, Firefox, Opera) but works correctly on desktop browsers. Other OAuth providers like Google, Github, etc. works fine on both Android and Desktop browsers. Facebook works on Desktop browser, but window.opener becomes null in Android browser. In the network tab, I noticed that desktop browsers make requests to www.facebook.com, while Android browsers make calls to m.facebook.com. Why does window.opener become null on Android browsers, and how can I resolve this?

Additional Reproduction Steps:

  1. Enable remote debugging on an Android browser using Chrome DevTools.

  2. Open a new tab and run the following in the Console tab: window.open(LOGIN_PAGE_URL);

    Replace LOGIN_PAGE_URL with a site supporting Facebook login (e.g., https://leetcode.com/accounts/login/).

  3. In the popup window, run: window.opener;

    It correctly returns the parent window reference.

  4. Click "Sign in with Facebook." On the Facebook login page, window.opener still returns the correct reference.

  5. Complete the login. After redirecting back to the original page, window.opener unexpectedly becomes null. Because window.opener becomes null, I am unable to send redirect_uri by doing window.opener.postMessage() from popup window to my opener window.

    Example code to reproduce the same error:

    <!-- Parent window --> <html>   <body>     <button id="login-btn">Sign in with Facebook</button>     <script>       document.getElementById("login-btn").onclick = () => {         const popup = window.open("https://my-domain/login", "_blank", "width=600,height=600");         window.addEventListener("message", (event) => {           if (event.origin === "https://my-domain") {             console.log("Received message from popup:", event.data);           }         });       };     </script>   </body> </html> <!-- Popup window --> <html>   <body>     <script>       // Redirects to Facebook login       window.location.href = "https://www.facebook.com/v21.0/dialog/oauth?response_type=code%2Cgranted_scopes&client_id=CLIENT_ID&state=STATE_STRING&scope=public_profile%2Cemail%2Cuser_likes&redirect_uri=https://my-domain/login";       // After redirect back from Facebook       window.onload = () => {         if (window.opener) {           window.opener.postMessage({ redirect_uri: window.location.href }, "https://my-domain");         } else {           console.error("window.opener is null");         }       };     </script>   </body> </html> 

    Client ID can be retrieved by registering a web-app in https://developers.facebook.com/.

We're experiencing a critical issue with the WhatsApp Business Platform Cloud API where customers using the latest iOS version of WhatsApp are unable to select shipping addresses during checkout. This issue is specifically affecting our order completion process.
Key Points: - The shipping address selection interface is completely unresponsive on iOS devices - The same functionality works correctly on Android devices and older WhatsApp versions - This is blocking our customers from completing their orders - Order ID Reference: skygoal-402953 - Business Phone Number: +91 91***1 910
Technical Environment: - Integration: WhatsApp Cloud API - Platform: iOS WhatsApp (Latest Version) - Implementation: Standard shipping address selection flow - Issue Occurrence: 100% reproduction rate on latest iOS devices
Business Impact: This issue is preventing iOS users from completing their purchases, directly affecting our business operations and customer experience.
We request urgent investigation and resolution of this issue as it's affecting our business operations.

Hello Team,
We have a Shopify website. We have implemented an advanced matching pixel and custom conversion setup. However, when testing events in the Meta Pixel dashboard, no events are being triggered. We have cross-checked the setup thoroughly, but the issue persists.
Could you please suggest possible reasons for this issue and how to resolve it?