django-allauth VS google-ads-python

If you don't want to use Pegasus or another paid product (presumably because of the cost), the packages I'd reach for are django-allauth for login/user stuff and dj-stripe for the Stripe integration. As for teams, there wasn't a library I was happy with so I rolled my own for Pegasus, but some people like django-tenants. It's too heavyweight for my taste as it requires a more complex dev/test/infrastructure setup with Postgres schemas, as opposed to having a single-database and handling multitenancy in the application layer. But there are pros and cons to both approaches.

View on GitHub

django-allauth - authorisation with email and social media accounts

Complete user authentication (Log-in/Log-out, ...) via Django Allauth

Usually when people talk about oauth with django, they mean letting users access a django app using oauth and django-allauth is often a good choice for that, but if you're accessing an API that doesn't sound like what you're after.

Although the answer given below solved my problem, I just want to share that I ended up using django-allauth instead of social-auth. And the latest version of django-allauth appears to be the best Django authentication app.

My understanding is that django-allauth is the ideal tool for this.

Has anyone used django-social-auth, django-registration and django-profiles together. Do they work well together? I have established social-auth but I read somewhere that django-allauth is better. Should I switch over to that?

But I still don't know exactly how to configure everything if I want to show the results of https://github.com/googleads/google-ads-python/blob/main/examples/basic_operations/get_campaigns.py on a Django page/view (or at least in the console for now).

Have you tried the officially supported library from google for the ads api?

You also need to install the Google Ads Python package - https://github.com/googleads/google-ads-python/