We are sending enhanced conversions to Google ADS API using the Upload Click Conversions method of the API client. This is the only data we send to API. No user identifier data about customers is sent to API before that via GTM. In Google Ads UI measurements, I see that Google only shows 5% of what actual conversions are. Does this mean we need to send Google Ads API some information through GTM before we send the conversions through the API client?
Yes, you need to provide a user identifier via GTM (before) as well.
See Instructions here:
https://support.google.com/google-ads/answer/11347292
Related
We received an email titled "[Action Required] Remove the addApi(Drive.API) code from your apps that initialize the Google Drive Android API" informing us that on February 1, 2023, the Google Drive Android API will be fully turned off and that we would need to respond by removing any reference to addApi(Drive.API). We do not appear to use this API, but we see usages of the Google Drive API in the Google Cloud dashboard for our Android app project. This could very well be REST Drive API calls, but we're not seeing a way to confirm where these API calls are coming from.
Following the documentation's instructions exactly as written, it would appear that the only action needed would be to remove any usages of addApi(Drive.API).
So, We're looking for a confirmation that this is truly the only usage that would cause issues to leave in our Android app once the Android Drive API shuts down. Does anyone know?
I'm new to API programming and I need some help.
I have a JAVA application that needs to use twitter API to send a request and get the response for specific data.
For example sending tweet ID and get video or image URL.
My question is that assuming the app will be used by 10,000 people daily with 1 Key for the API call, will there be any problem for my application to send and get the request from Twitter API?
I saw online that there are some limits for APIs calls, for example, your API key can't call more than 100 times daily, if so how it will work for my application if I have 1 key that will be used by 10,000 people from different location and countries.
Thanks in advance.
I want to track activity referrer information in my android application.
setReferrer in the Google Analytics API seems to be a suitable method (com.google.android.gms.analytics.Tracker.setReferrer)
But I can not find any documentation for it.
What can I pass to it? Only web links? Or android app URIs are supported too?
like: android-app://com.google.android.googlequicksearchbox/https/www.google.com
I get information about the referrer from:
android.app.Activity.getReferrer
android.content.Intent.EXTRA_REFERRER
android.content.Intent.EXTRA_REFERRER_NAME
Edit:
With additional research I found some more information about referrer in Google Analytics via it's Measurement Protocol Parameter dr:
developers.google.com/analytics/devguides/collection/protocol/v1/parameters#dr
Specifies which referral source brought traffic to a website. This value is also used to compute the traffic source. The format of this value is a URL.
But it also does not clarify whether or not android app URIs are supported.
It seems like Google Analytics for mobile apps does not support referrer information at all.
Only install referrer is shown. I can't find activity referrers anywhere even if I send this info.
I have an android app and I want to allow a user to login using a verification code. I want to send the verification code in an SMS to the user's phone. What is the best solution to verify if the verification code matchs on the server side?
Is the creation of new table that contains verification codes a good idea?
Here are a couple ways to implement user verification on Android:
Some apps build it themselves with SMS / Voice APIs
Others use a verification specific API
With SMS / Voice APIs
You'll need to generate a code (huge security threat)
Send it via the channel you use primarily
Set some kind of time delay job (queue,worker, whatever)
Send a fallback message should you get no response
from the user
Nexmo’s Verify API
Instead of paying different fees for each country, Nexmo allows you to go globally with a simple API call for a flat fee of 10 cents per verification, NOT per attempt (unsuccessful attempts will not be charged towards your account)
Verification code should arrive to your phone as an SMS. If you wait a while, you'll also get a phone call, and the code will be read to you. The timing and channels used depends on the type of number, the country, and the carrier.
You can also use Verify's Android SDK, which enables you to build Verify into your Android app by simplifying this integration. After importing this library into your app, you will only need the user's phone number, while the SDK will take care of the remaining steps required to verify your users.
Take a look at Nexmo's Verify Android SDK here
Full disclosure, I work at Nexmo.
I've been thinking about implementing of Google Play licence check on my Java server. Is that even possible? I haven't been able to find anything on this matter. I know Android LVL is written in Java, but I'm not sure if it can run outside of dalvik machine. Is there a posibillty of checking Google account name or some kind of device ID against Google Play to check whether an app has been bought in a Java server application?
The answer above is simply verifying response data (returned by google LVL on android device) on app server.
I think the question is asking if it's possible to call some google web API to do Google Play license check on its app server. But it seems like google doesn't open the web API interface to its licensing server, all LVL calls need to be done using its google play service framework on android device.
Yes it's possible, the java sources are out there and could be downloaded (and afaik, the jar is not dexed until you compile your application) - see some kind of manual over there at developers.android.com to read about how to get the sources
I've heard about a PHP project trying to attempt it, but using java should be no problem at all - you do the same things on the server, the manuals state for the client - and let the client sends the encrypted response from the market directly to the server via SSL (e.g. byte[] post)
You should get a UID from ResponseData.userId
Read some more in this blog post and more info and links in another SO answer