Best practices for testing datapipelines using Python Ads API

[Reddy (Jay) Bujala]

Hi Team,

Could you please help share a guide on the best practices to set up E2E tests on datapipelines that update Asset-based page feeds using Python? Is a test/dummy account the way to go?

One of our datapipeline unlinks outdated assets from the AssetSet and adds a bunch of new ones and links them to the AssetSet to update the traffic to the correct ads based on our latest inventory of products.

Thanks

Jay

[Google Ads API Forum Advisor]

Hi Reddy,

Thank you for reaching out to us.

Please note that test accounts won't affect your live ads or charge your account, hence, they're a useful way to experiment with the API. If you want an account that serves real, live Google ads (test accounts do not serve ads) then I would suggest you apply for basic access, you may check this documentation as it has the application form for its access.

On the other hand, you may check and use the AssetService for updating your Asset . However, I’m afraid that we do not have a guide on the best practices to set up E2E tests on data pipelines that update Asset-based page feeds using Python. That being said, I would suggest you implement a local feature on your end to check and test this pipeline and trigger the Google Ads API services to update the Asset-based page feeds.

Since you are also mentioning AssetSet, kindly note that in the Release notes, there is added support for linking customers and ad groups with asset sets for test accounts only.

• CustomerAssetSetService for adding/updating/removing CustomerAssetSet , which represents a link between a Customer and an AssetSet.
• AdGroupAssetSetService for adding/updating/removing AdGroupAssetSet, which represents a link between an AdGroup and an AssetSet.

You may check this release notes for more information.

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2gP74a:ref