Best practices on managing Ids?

[F B]

Are there any good blogs or guides or best practices to managing the representation of the Google Ads Objects locally.

I.e. assuming I am creating 150 campaigns, all of them have adgroups, ads and keywords. Now if I want to manage them based on our available inventory, this means I will need some sort of "local" representation of my google Ads objects. Such that I can use the API to enable or disable a particular adgroup for example.

I somehow feel like I am reinventing the wheel here.

Cheers

[Zweitze]

So the question is, how to store those IDs and other intermediate results, so you can use them later?

Sorry, no hints for blogs or guides... your question is a general programming topic.

What to do? Basically you have "storage", which enable to store information, and retrieve that later.

For instance, you can write to a file, then save it. Later your program (or a different program) can open that file again and look for your information. This is easy to realize, you only have to make sure you have read and write access to the file.

When get a lot of things to store, say over 10,000, you should look into databases. At that point speed becomes an issue, you may want backups of the information, etc.etc. With databases you can have billions and billions of items. On the downside, it's a complicated topic - many libraries are filled with books on databases.

When you're in the cloud, you can't really have a local file to read from and write to. You may want to look at the solution seen in many AdWords scripts: information, settings etc. are stored in Google sheets.

[F B]

I guess I had that one coming for providing so few details.

I am totally in the clear about needing a "local" (which means running on a server) database.

Consider the following scenario:

I have items (~100k), of which each will be represented by an adgroup, they will be clustered within campaigns. For every item there will be roughly 5, later 10 languages.

Now when thinking about setting up a project of managing them all programatically, I am considering having a local representation of most objects. 

However, this makes for a plethora of objects and dependencies between them. It almost feels like I am building a light version of the Ads Ecosystem.

I am wondering if there are some established systems/best practices for this.

Does this make more sense?

Cheers

Fabian

[googleadsapi...@google.com]

Hello Fabian, 

I think you may already be aware of this. If not, the hierarchy of the objects in Google ads are shown in this guide. I will let other users on th forum share their experience on this topic

Thanks,

Bharani, Google Ads API Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
    http://googleadsdeveloper.blogspot.com/search/label/adwords_api
    https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Was your question answered? Please rate your experience with us by taking a short survey.
If not -- reply to this email and tell us what else we can do to help.

Take Survey

Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/

[F B]

Thank you for the reply. Jupp I am very much aware of this. Have been reading the documentation right to left and top to bottom.

Curious to hear what others here think, how much of the objects in an account should be mirrored into a database.

[Zweitze]

So, my two cents - coding AdWords API for well over ten years.

Whatever you do, be prepared for change. The Google Ads eco system is very alive, every month features come and go. Some changes are big, some small. Once you implemented a feature (say Shopping campaigns or Education ad extensions or Campaign experiments or Shared budgets or MCC linking or Campaign groups or ...) you run the risk that Google changes it, leaving you a little time to drop whatever you're doing, and deal with that change.

So, to be prepared for future changes, I suggest to be conservative on implementing features of Google Ads.