I'm try to create new conversion action that the value in UI will be "Use different values for each conversion"

I'm using add_conversion_action.py from example. In the value_settings I set:

value_settings.default_value = 0.0 value_settings.always_use_default_value = True 

But in the UI I got "Don't use a value for this conversion action (not recommended)"

I try to look for answer on developers.google but all looks fine.

Thanks!

The code from example:

# [START add_conversion_action] def main(client, customer_id):     conversion_action_service = client.get_service("ConversionActionService")     # Create the operation.     conversion_action_operation = client.get_type("ConversionActionOperation")     # Create conversion action.     conversion_action = conversion_action_operation.create     conversion_action.name = f"Earth to Mars Cruises Conversion {uuid.uuid4()}"     conversion_action.type_ = (         client.enums.ConversionActionTypeEnum.UPLOAD_CLICKS     )     conversion_action.category = (         client.enums.ConversionActionCategoryEnum.DEFAULT     )     conversion_action.status = client.enums.ConversionActionStatusEnum.ENABLED     conversion_action.view_through_lookback_window_days = 15     # Create a value settings object.     value_settings = conversion_action.value_settings     value_settings.default_value = 0.0     value_settings.always_use_default_value = True     # Add the conversion action.     conversion_action_response = (         conversion_action_service.mutate_conversion_actions(             customer_id=customer_id,             operations=[conversion_action_operation],         )     )     print(         "Created conversion action "         f'"{conversion_action_response.results[0].resource_name}".'     )     # [END add_conversion_action] 

I'm trying to find a way to check if a phone number is on whatsapp or not. We're using the Twilio API and have a verified Whatsapp business account.

This was not possible in 2019, but maybe something's changed?

Thank you

customer_service = client.get_service("CustomerService") app_list = customer_service.list_accessible_customers().resource_names def customer_query(client, customer_id):     ga_service = client.get_service("GoogleAdsService")     query = """         SELECT             customer.descriptive_name,             customer.currency_code         FROM customer         LIMIT 1"""     request = client.get_type("SearchGoogleAdsRequest")     request.customer_id = customer_id     request.query = query     response = ga_service.search(request=request)     customer = list(response)[0].customer     return customer for entry in app_list:     customer_id = entry.split('/')[1]     entry = customer_query(client, customer_id)     formatted_entry = {'customer_id': customer_id, 'name': entry.descriptive_name, 'currency': entry.currency_code}     apps.append(formatted_entry) return apps 

This seems really convoluted and I'm having to pass around a lot more data than I'd like. Surely there should be a way to just request the details.

I've been using 2 REST API calls to batch upload google offline click conversions. One generates the Access Token. The other is the API call to upload the offline click conversions.

All was well for a few weeks until suddenly we started getting invalid_grant messages in the JSON when trying to generate the Access Token. No clue why -- and we received no email or anything from Google on this. It just stopped working and the invalid_grant error was cryptic and the online help didn't explain much.

I resolved this issue by following this video to generate a new Refresh Token in the Google oAuth Playground:

https://youtu.be/KFICa7Ngzng

So, my question is -- can we automate this somehow? I can trap the invalid_grant JSON response and then would like to do some series of REST API calls to generate a new Refresh Token. Or, would I need to switch from a Web Application Type to a Service Account Type on the oAuth?

I also researched what might have caused the Refresh Token to expire. I looked at the following page and none of those bullet items applied to my situation:

https://developers.google.com/identity/protocols/oauth2#expiration

I am planning to use whatsapp cloud API but I see each country has different rate cards: https://developers.facebook.com/docs/whatsapp/pricing/ If I have application in which registered user can be in USA or UK or India etc and can send messages to users belonging to different countries in that case how to handle pricing implementation on backend?

Is it ok if I calculate the cost based on analytics endpoint: https://developers.facebook.com/docs/whatsapp/business-management-api/analytics this endpoint includes cost as well for each registered phone number. In that case I can easily calculate monthly cost occurring with start and end date in query params. Is there any other solution or can this be improved?