We are a digital media company. Lately for some of our clients whom we do dynamic display ads we have noticed a discrepancy in the tablet clicks and sessions.
I have analyzed our sessions, with our clicks and the clicks we get from adwords and there seems to be loads of discrepancy.
Can anyone help me in figuring why this could have happened? Could there be some issue in the url we are passing in the displays that have an issue on tablets.
I have seen this case many times and it varies greatly from client to client, campaign to campaign. See if there is some redirect of the campaign to another url, or if the bounce rate is too high, in line with the duration of the sessions, because if the user clicks on the ad and leaves the site quickly, the session is not counted.
Have you checked this guide?
https://support.google.com/analytics/answer/1034383?hl=en
Related
I have a website where people can interact with different objects to view specific content. I would like to know which objects get the most interactions by real people. For example there are thumbnails of images and I would like to know when a user clicks on a thumbnail to view an image.
To do this I thought I would create a psql table with thumbnail_id and an IP address, where every single view is stored (to ensure every combination of thumbnail and ip is only counted once and people can't just spam click it).
And so every time a click happens, a post request on a /views endpoint with the thumbnail id attached is made in the background.
The proplem is, some people may be incentivized to create bots to auto click certain images with many different IPs.
So I was wondering if I could use recaptcha v3 to identify real users as opposed to bots which would include a token with every view request.
But I was wondering, would is this too much for my backend to handle (since it would have to talk to googles servers every time anybody views an image, which might be every few seconds for each user and I would be billed while the server waits for a response) or be too expensive, since I have to pay google on every request? Or is there some other obvious problem with this?
I'm asking since I have only ever found recaptcha used for single form validation and never for traffic measurements, even though that seems like a pretty obvious use case.
I use Firebase for user authentication, I just resubmitted my app and got the following rejection:
Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing
We noticed you do not use App Tracking Transparency to request the
user's permission before tracking their activity across apps and
websites. The app privacy information you provided in App Store
Connect indicates you collect data in order to track the user,
including Other Diagnostic Data, Audio Data, Performance Data, Crash
Data, Product Interaction, Phone Number, User ID, Emails or Text
Messages, Photos or Videos, and Search History.
Starting with iOS 14.5, apps on the App Store need to receive the
user’s permission through the AppTrackingTransparency framework before
collecting data used to track them. This requirement protects the
privacy of App Store users.
Next Steps
Here are two ways to resolve this issue:
You can remove the tracking functionality from your app and update your app privacy information in App Store Connect.
If you decide to continue tracking users, you must implement App Tracking Transparency and request permission before collecting data
used to track the user or device.
My app has no ads but I have to track users throughout the app using their userID so that I know what post belongs to which user etc etc.
If the user declines the prompt AppTrackingTransparency isn't that basically saying that I can no longer track them? I have no idea what to do here.
Here are the Privacy checkboxes that I filled out. Apparently i can change something but I don't know what to change.
I resubmitted my app and it got approved. Seems the key is to make sure it is only Used for App Functionality.
To make that happen I made these changes to the App Policy page in App Store Connect.
I clicked the blue Edit button next to each policy. Of the 10 policies, here are 4 red arrows next to 4 of the Edit buttons. Click each one for the same results for steps two, three, and four.
After clicking the Edit button, you will be presented with a screen with a bunch of selections, for that screen all I did was check App Functionality:
For the 2nd screen, I selected No, user IDs collected from this app are not linked to the user's identity.
For the 3rd screen I selected No, we do not use phone numbers for tracking purposes. Notice on the 3rd screen, under Definitions and Examples, it says:
Tracking does not apply in the following situations:
• When the data broker uses the data shared with them solely for fraud
detection or prevention or security purposes
Here is a screen shot with it in purple underline:
Here are how all of my Privacy Policies look now:
Here is the email approval:
I'm making a custom tab app of MS Teams with ASP.NET, however, the tab doesn't seem to pass a same cookie between requests on MS Teams. So the ASP.NET app behind the tab generates a new Session.SessionID on every request.
I've checked the following question, and tried some settings according to that page, but nothing helped me. Actually my web site works nicely if I navigate it via Chrome or Edge.
ASP.NET: Session.SessionID changes between requests
How do I get a same cookie between requests on MS Teams?
I've not tested this specifically so haven't seen it, but basically the broad idea of session is to have to uniquely "remember" a user, and then restore State for them from a location (e.g. database). From your question, it seems like the out of box "Session" object is giving trouble, but at any rate you should probably avoid using it because it won't "remember" the user even across devices.
However, Teams provides you a way to achieve the same thing yourself quite easily. Remember that the Teams 'Context' object provides a userObjectId property that is unique and valid for the same user on all sessions on all devices (it's actually their Azure Active Directory id). You can simply store whatever you want in your own database, key'ed by this id, and request it on page load. It's also possible to get this from the querystring for a static (personal) tab if you want to handle the behaviour server-side (e.g. C#).
I was testing functionality on a website that I'm developing that allows the user to sign in using their Google account. I filled in the "OAuth consent screen" in the Google Developer's Console, including all of the URLs to allow Google to redirect a user back to my website with the necessary OpenID information. Everything works, but I used test URLs on the "OAuth consent screen". Afterwards, I made the very costly mistake of clicking the button at the bottom of the screen labeled Submit for verification. I should have clicked the button labeled Save. The URLs on my OAuth consent screen all have internal hostnames, so they're not accessible from the Internet. Is there any way that I can cancel the request to Google for verification? The page is currently frozen, and it won't let me change any of the URLs until I inevitably fail the verification process. There is also a message that states that verification may take up to 4-6 weeks, which is a long time to wait for something with a known outcome...
I know this may not be the right forum for this question. However, Google's own support page links to StackOverflow, and I'm sure web developers must encounter this problem quite frequently. I tried looking on Google's FAQ pages, but didn't see anything about canceling the verification process. It's quite possible that I missed something....
Edit I've received an e-mail from the Google Cloud Platform notifying me that my request to have my app verified has been denied. This makes sense, since I completed the Consent form with incorrect test URLs. However, the Save button on the OAuth consent screen is still disabled. The screen appears to be in the verification process. Perhaps this is the intended workflow for the screen. At any rate, the original request for verification was denied within a day or two, which was quite fast considering the 4-6 weeks that Google allows for the process. If anyone can confirm or deny that this is the intended behavior of the OAuth consent screen, I would be happy to mark their answer as correct...
At this point, I'm inclined to believe that this is the intended behavior of the OAuth consent screen. 3 days after the verification request has been declined, the message Your consent screen is being verified. This may take up to several weeks. Your last approved consent screen is still in use. is still being displayed. I now believe that further changes to the screen, such as updating the URLs, will require the verification process to be restarted, since the Save button remains disabled.
I have an incredibly simple application that simply fan gates and then offers a form to fill out (contest). I receive and parse the signed_request and display content based on the like_status. My average response time this week is 0.00495 on my index.php.
However, a number of page view requests NEVER reach me. A small percentage of users report seeing a white page. They do not see an error like a 404 or 501 etc., just a white page.
I can only find out about through disgruntled wall posts because I cannot calculate or diagnose requests that I never receive.
This has been happening MORE this week and it is causing immense issues with a client's contest. While I can offer the explanation that millions of people are hogging Facebook at certain times AND it's return to school week, it's not really helping.
So far an iframe app is like a black box and the wall is the only way to do customer care. If Facebook requests time out before reaching me then I may not be able to offer this service to clients even if it works for 99% of the time.
How have you dealt with these issues in the past because they affect ALL developers of iframe apps now that FBML has been deprecated.
Thanks.