So we wrote a React app that lets call center admins create holidays, special events, meetings and emergency conditions for Amazon Connect. In version 2.0 I would like to be able to allow admins to use an uploaded pre-recorded prompt and select that for an announcement from my React app. I have searched the API and it has no endpoint for listing or creating prompt. Does anyone else know if this is possible?
There is currently no API for Prompt Management. Right now, you would have to manually reference the ARN value of the Prompt to dynamically play it via a lambda within a contact flow. Just looked into this myself for a similar feature, and confirmed w/ AWS team.
I'm trying to integrate my online Google Actions builder with Actions Console.
Now users have to manually create Actions JSON descriptor file and upload it to the project via gactions tool. But I would to let them upload their actions without these steps. As an example I saw that Gupshup service does this already - user has to authorise Gupshup once he would to upload his project, and all things perform behind the scene by Gupshup.
As I know I have to use some sort of Google API that allows to manage projects in Google Console with some specific OAuth scope - something like "Allow this service to manage Google Assistant dialogues and grammars".
Are there anybody who knows anything about such OAuth scopes and API?
You may be able to do something with the gactions tool, although there is no fully public API to manage Assistant console projects.
I am currently trying to get mobile app install attribution from Facebook ads. The goal here is something like this,
Create a Facebook ad that pings Google Analytics of the ad click.
(Example URL : https://click.google-analytics.com/redirect?tid=UA-324109-49&url=https%3A%2F%2Fitunes.apple.com%2Fnl%2Fapp%2Fdrogisterij.net-mobiel%2Fid506652686&aid=com.drogisterijnet.drogisterijnet&idfa=%{idfa})&cs=GAUC&cm=link&cn=Presentation
The ad is clicked and goes to Google Analytics and sends a hit for metrics in the URL params.
After sending the hit the user visits the destination in the App store where I can link the attribute the click of the ad to the installation through the IDFA (since IDFA is captured on install).
There is a Google Developer page that helps create this sort of redirect link here: https://developers.google.com/analytics/devguides/collection/ios/v3/campaigns#url-builder
My issue is I do not know the macro used to get IDFA from the Facebook App .
Is it the same macro as the above link idfa=%{idfa}? I can not find any information on this other than where Facebook says
"The Facebook SDK for iOS only accesses IDFAs in the following scenarios: 1) if your app serves ads within the app through Facebookâs Audience Network, or 2) if your app logs app installs or other mobile App Events in order to attribute those events to your ad campaigns."
Link to above quote.
https://developers.facebook.com/docs/ios/troubleshooting#IDFA
Am I going about this the wrong way or should I just be using a different macro?
In short, you cannot. This is not something supported in Facebook ads.
I'm trying to make an Autocomplete field which should fetch cities as the user types, by using the Google Places API as described in this tutorial:
https://developers.google.com/places/training/autocomplete-android
You've probably found this question around many times before as I did, but none of the answers helped me. Here are the things you should know:
The URL is
https://maps.googleapis.com/maps/api/place/autocomplete/json?sensor=false&key=myKey&components=country:ro&input=whatTheUserTypes
Please don't reply by saying you replaced the API key with your own and it worked - the API key which goes there must be Android specific and won't work from a browser.
So did I make the Android API key using the SHA1 fingerprint obtained from the keystore I signed the app with.
I turned on Maps and Places APIs from the console.
The quota isn't exceeded.
All those and it still gives me REQUEST_DENIED
What I didn't mention is that I have O2Auth activated - does that change anything? Shouldn't it be as simple as putting the API key in the app?
Thanks!
Although this has been answered, I think the community could do better.
I was tearing my hair out about this, it just didn't make sense to me.. I was making an iOS/Android App, so I made an iOS/Android Key...
Wrong.
With Google's Places API, your bundle identifier isn't even considered.
What you really want to do is this:
(I'm using the new User Interface)
1. Log into https://cloud.google.com/console#/project
Select your Project Name, then go into API's & Auth > APIs
Make sure you have Places API Turned on. This is the only thing that needs to be turned on for Places-API to work.
2. Go into Credentials
Click CREATE NEW KEY under Public API Access
3. Select BROWSER KEY
4. Click Create, Nothing Else
Leave the HTTP Refer box empty.
5. Use the Key Generated here
This key will allow ANY user from any device access to the API via your Developer login.
You can try it out here: (Be sure to replace YOUR_KEY_HERE with your generated Key)
https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Food%20Sh&sensor=false&radius=500&location=0,0&key=YOUR_KEY_HERE
6. Enjoy
Now you can use that URL above in your Android/iOS device.
The Google Places API does not currently support Android or iOS keys generated from the Google APIs Console. Only Server and Browser keys are currently supported.
If you would like to request this support, please file a Places API - Feature Request.
https://developers.google.com/places/training/autocomplete-android
Storing your API key
Although the above code demonstrates how to communicate directly
between an Android app and the Places Autocomplete service, you should
not store your Places API key with your app.
You should therefore build a web application that stores your API key
and proxies the Places API services. In order to secure communication
between your Android app and the proxy web service, you should require
user authentication to your proxy web service. Your Android app can
securely store user credentials and pass them to your web service, or
the user can log into your web app via an Android WebView.
For the latter approach, your web app should create and return a user
authentication token to your Android app, and your Android app should
subsequently pass this token to your proxy web service.
Go to google cloud platform console>Credentials click on edit by selected your YOUR_API_KEY>Application restrictions > select none option>save thats it.
If you select the android apps option from Application restrictions then google deny the place API with exception REQUEST_DENIED.
In Google dev console, you should be able to find both "Places API" and "Places API for Android"
Make sure to use "Places API for Android"
For some reason, "Places API for Android" is hidden in the API list, but can be accessed using search.
I had the same issue , I fix it by leaving
Accept requests from these HTTP referrers (web sites) (Optional)
in browser key Empty
I am still new, so I cannot comment, but to shed some light on Moe's answer, I resolved some similar Google Maps API issues regarding URL queries (for directions, using Volley) with the following steps:
Get Android API Key (including Google Maps Directions API in my case).
Get "Server" API Key (which seems to be created by using a key restriction of "HTTP referrers" these days - really, it's just used to issue URL queries through HTTP).
Store the Android API key as a meta-data tag in the application tag in AndroidManifest.xml with android:name="com.google.android.maps.v2.API_KEY" and android:value as your key. This is used for direct interaction with the Maps API (minus URL queries).
Use the server API key whenever issuing URL queries.
I am not sure if this also applies to URL queries for the Places API, if you only need the server API key, or if there is a better solution, but this worked for me.
I imagine that it works with just the first key - the one not restricted to Android.
Inside Google Cloud Console type Places and Activate it. Create an API Key and insert it onto your Android Studio App as you would do normally. That`s it.
I had the same problem. For me the key was to enable billing on project. I am still using "Applications for Android" restrictions. After setting up the payment method, Places Api started working.
Prior to using the Places SDK for Android, do the following:
Follow the Get an API Key guide to get, add, and restrict an API key.
Enable billing on each of your projects.
Enable the Places API for each of your projects.
See it there.
Be sure also to check out the billing plans for the Google Places API as it is not free!
Can someone please help me with that problem.
The question:
Using the API, How can I know if an AdGroup using remarketting or not ?
The reason:
I want to change the destination URL for the entire campaign with the API.
usually for normal ads which uses Keyword, I just update the keyword (using the Ad URL for keyword which don't have URL).
when having audience, since the Ads aren't triggered with a Keyword, I must change the Ads URL.
since changing A Ad URL require to delete and recreate an Ad I'm trying to avoid it when possible.
The real question:
When will Google for COL will allow us to update the Ad URLs.
And they can update the quality index if that's the problem for all I care.
Thanks for taking the time to read it,
R.g.
As an FYI, the official AdWords API forum is available here:
http://code.google.com/apis/adwords/community/
An ad group that is using remarketing will contain a BiddableAdGroupCriterion containing a CriterionUserList. There are no plans to allow for ad URLs to be modifiable.