Is there a way to allow the Google Ads API token to perform only the following operation:

• adding IP addresses on all campains blacklist.

I'm trying to figure out if this works. Unfortunately I do not have a website to test this with. Though I've read the GA and GAds documentation I'm not sure if this is possible. So please bear with me.

Imagine a simple website that has Google Analytics (with a linked GAds account) deployed. I want to run a survey on this site users can answer if they like to. As the result of the survey the participants are assigned some ID. Lets say the result variable is called cluster and the values are A, B or C.

What I want to do now, is use this group of participants of the survey and try to target new visitors that are similar to the ones that have been assigned a C value via Google Ads.

As far as I understood the documentations this is how it could be done. Please correct me and point me in the right direction if I'm wrong.

1. I'm setting up a custom user dimension called Cluster in GA
2. I'm editing the GA code on the website to include the custom dimension that will be populated with the result of the mentioned survey
3. When the results come into GA, I'm creating a remarketing audience in GA called Cppl based on the custom dimension Cluster
4. I'm importing this Cppl remarketing audience into GAds
5. I'm creating a similar audience in GAds based on Cppl list
6. I'm publishing a campaign based on this similar audience

Does this process make sense and is it correct or am I making any mistakes?

I have this following code to fetch all list of ads clients comes under a Ads manager account, I am using manager credentials to get list of clients.

public Customer[] GetAllManagerClientsList(string currentUserEmail, string authorizationCode)     {         string baseURL = _configuration.GetValue<string>("URL:SiteURL");         var currentUser = _userRepository.GetIntegratedAppsDetailByEmail(currentUserEmail);         AdsOAuthProviderForApplications oAuth2Provider = (user.OAuthProvider as AdsOAuthProviderForApplications);         oAuth2Provider.Config.OAuth2RedirectUri = baseURL + "/google-auth-callback";         oAuth2Provider.FetchAccessAndRefreshTokens(authorizationCode);         //Get customerID         user.Config.OAuth2AccessToken = oAuth2Provider.Config.OAuth2AccessToken;         user.Config.OAuth2RefreshToken = oAuth2Provider.Config.OAuth2RefreshToken;         CustomerService customerService = (CustomerService)user.GetService(AdWordsService.v201809.CustomerService);         var customersList = customerService.getCustomers();         var ClientCustomers = customersList != null && customersList.Length > 0 ? customersList.Where(c => c.canManageClients == false).ToList() : null;         if (ClientCustomers.Count() > 0)         {             return ClientCustomers.ToArray();         }         else         {             return null;         }     } 

The application worked fine for half a year, I tried to upload an update, everything was as usual, but the console received "We have determined your app contains code to facilitate Ad Fraud", although I almost did not change anything. The only change that had at least some relation to the advertisement, after the splash, an advertisement appears, after it is closed, it shows the main screen of the application, it was decided to extend the display time of the splash screen, so a slight delay was added so that the advertisement had a little more time to load. After that, the update failed. We wrote in support, after almost 2 weeks, they replied:

"I’ve reviewed your appeal request and found that your app still violates Google Play Policy. I’ve included details below about the specific issue with your app and what you can do to get your app back on Google Play.

Step 1: Fix the policy violation with your app

During review, we found that your app violates the Ad fraud policy:

Your app is not compliant with the Ad Fraud policy. Ad fraud is strictly prohibited. Ad interactions generated for the purpose of tricking an ad network into believing traffic is from authentic user interest is ad fraud, which is a form of invalid traffic.

Ads should not be shown in a way that results in inadvertent clicks. Forcing a user to click an ad or submit personal information for advertising purposes before they can fully use an app is prohibited. Ads should not appear after the user has exited the app, or after the user has pressed the back button to exit the app. Ads associated with your app must not interfere with other apps, ads, or the operation of the device, including system or device buttons and ports.

This includes overlays, companion functionality, and widgetized ad units. Ads must only be displayed within the app serving them. You can refer the attached screenshot for additional information.

You can read through the Ad Fraud policy page for more details and examples of common violations.

Please update your app to fix this issue. You may also want to double check that your app complies with all other Developer Program Policies, as additional enforcement could occur if there are further policy violations.

Step 2: Submit an update to your app

To submit an updated app bundle or APK:

Prepare your updates. Create a new release using the compliant app bundle or APK. Be sure to create the new release on the same track(s) as the non-compliant app bundle or APK, increment the version number, and set the release to 100% rollout. Follow the on-screen instructions to add APKs or app bundles, then review and roll out your release. Please let me know if you have any other questions. Thanks for working with us to fix the policy issue and for your continued support of Google Play."

It seems like the application does not break anything, but I came across this answer Uncaught exception thrown by finalizer: All WebView methods must be called on the same thread. (Expected Looper ) th / 57308639 # 57308639 it is possible if the application is minimized and the advertisement is loaded and is shown not in the application. Or, due to problems with the connection, it does not show ads immediately after the splash, but passes it to the main screen and then it already shows that it also seems to be wrong, but then problems with the update appeared earlier. Could any of this be a problem? What else could be the problem? Maybe someone did something similar, please tell me what are the solutions?

During checking traffic source on e-commerce website i get confused.

I know that param gclid=.. means that user is tagged by GoogleAds, while fbclid works the same way but with facebook.

However, I dont understand what does it mean while they are both together in single url, like: www.example.com?gclid=CjwKCAiAyrXiBRAjEiwATI95mafT26kwak0CFBgICH0ZlLqafSBuyyoUBVZihf22pPdG9QK8DUmiZBoCh8YQAvD_BwE&gclsrc=aw.ds&fbclid=IwAR0oihEZbw0Q43GXiv4YW9n_G9odTEcpxzLtMxjYYqgrTt5EM-BcKqrJyuU

Is it possible that google ads is displaying ads on facebook and that is why gclid and fbclid are attached to url at the same time?