Can I use Google Ad Manager to place and manage my own ads on all of my sites? - google-ad-manager

I have 30 different websites and I want to place a single ad across all of the sites. Is it possible to use Google ad manager so in the future I can change the ad on google ad manager and have them change universally on all my sites?

Yes, it is the main role of an ad server to enables you to :
manage your inventory (create sites / placements...etc)
manage your deliveries (campaigns / line items / creatives...etc)
You need to check the online ressources to understang how it works, starting with this.

Related

D365FO import AAD users using API

I'm trying to find a way to import Azure AD users to Dynamics 365 Finance & Operations (D365FO).
It is possible to get all system users using this endpoint (like using Postman):
/data/SystemUsers
However, not sure how the new user could be imported from Azure AD. If I go to D365FO UI I can do this using System administration -> Users -> Import users and there is an option to add users from AAD. Is there a way to do the same using API? Looking through the web was not very helpful so far.
So here is the answer if someone is looking for the same - it is not possible.
If you work with SystemUsers using API - you can only select D365FO users.
At the same time there is 'AccountType' attribute which tells D365 F&O what account type is it.
It can be Claims User, Claims Group, AD User or AD Group. Types starting with 'Claims' are pointing to Azure objects while AD are pointing to AD.
So when you create a new user and selecr 'ClaimsUser' as account type - D365F&O would know that this is Azure user and would do mapping.
That sounds a bit 'magical', however this is how it works.

Making scheduled requests to Google APIs with service accounts

I have a flask website.
i would like the user to be able to schedule repeated requests for data from one of their Google accounts (let's say Gmail).
From within the website, the user would first authorize the application to access their private Gmail data. From then on, the application, would retrieve the user's Gmail data on a re-occurring basis, without needing to get authorization each time.
Is this possible? I know it would require a service account but can anyone point me in the direction of documentation that describes how this particular scenario might work.
Would such a scenario be allowed to persist long term? Or will their come a time when Google will require the user to reauthorize the application?
Correction, you should not use App Passwords. OAuth is the correct way to do it I believe:
https://www.oauth.com/oauth2-servers/signing-in-with-google/
Here's Google's docs on it, which is more specific to your need:
https://developers.google.com/identity/protocols/oauth2

Google groups API for non GSuite accounts? [duplicate]

I have found lots of information on the internet about adding Members to a Group in Googlegroups, but I cant manage to get any of it to work.
I am working in Python-DJango.
Using a bussiness account, I manage to add them using Provisioning API, but I could not do it with the new Directory API.
The problem is the group I want to add people to is not a business one, it's an ordinary googlegroups one:
group_name#googlegroups.com
From what I have found, and what I did for the business group I have the following code:
groupClient = gdata.apps.groups.client.GroupsProvisioningClient(domain=domain)
groupClient.ClientLogin(email="user#gmail.com", password="xxx", source='apps')
groupClient.AddMemberToGroup("group_name#googlegroups.com", "newUser#gmail.com")
I wanted to know what I have to put in the domain field. With the business account it was the business domain, but being a normal googlegroups one I am not sure. I have tried googlegroups.com and doesn't work, as I always get a invalid domain error.
Any help would be appreciated
Thanks!
The Provisioning API (deprecated) and the new Admin SDK are both designed to work with Google Apps for Business and EDU and only work against Google Groups for Business (groups with a custom #yourdomain.com address).
You cannot use these APIs with consumer Google Groups that have #googlegroups.com email addresses. For these groups, your only option is to manage membership via the web interface.

Admin SDK Customer Report API - how to specify a customer domain (as a reseller)

I read that the Admin SDK works for Google Apps resellers, but I'm having one specific problem.
I want to use the following request to get the number of user licenses in use on one of my customer's domains.
https://www.googleapis.com/admin/reports/v1/usage/dates/%s?parameters=accounts:num_users
But there's no way that I can find to specify the customer's domain name that I want to get the usage report for. Tried a few different ways.
There must be a way that is hiding from me because this was possible with the old deprecated API.
Thanks.
Using the Reports API for this is not advisable because it can be delayed by 48+ hours. It's also not possible for reseller users to run reports for customers at this time. Rather, you should use the Google Apps Reseller API to list subscription counts that should be fully up to date.
Looks like this API here will do the trick:
https://developers.google.com/admin-sdk/admin-settings/#retrieving_the_current_number_of_users_in_a_domain

Prevent users accessing certain apex applications

We have 50 apex applications which currently any user can access any of the 50 applications by using the website links on our intranet page.
How can you determine which users can access certain apex forms - I'm assuming lots of different apex groups will need to be made and people will need assigned to each group?
This is ok but i can see it getting out of hand trying to manage all the groups. I thought there must be a better way though of preventing users from accessing applications?
Any ideas on how to prevent users credentials working on some applications?
You can use authorization schemes, which can be applied at any level (e.g. the whole application, individual pages, regions, items, etc.).
http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/sec_authorization.htm