What it does in ClientPulse: Will read each client's Google Ads account and flag underperforming campaigns, ROAS drops, creative fatigue, spend-pace problems, and quality-score drops — early signals that a paid-search client is at risk.
Status: Connectable now — but the data pipeline ships in v1.1. You can complete the connection today; it does not yet feed the churn score. Connecting now simply lays the groundwork so the signal switches on the moment the poller lands.
Tier: Marketing-vertical module. Available on all plans for marketing agencies.
Per-agency: Connect once with a Google account that has access to your clients' Google Ads accounts.
Before you start (prerequisites)
- Account requirement: A Google account with access to the Google Ads accounts you manage for clients (a manager / MCC account works well).
- You'll need access to the Google Ads accounts you want ClientPulse to read.
- Cost: Free on ClientPulse's side. ClientPulse reuses the same Aurora Google OAuth app as Gmail, Calendar, and GA4 — you don't need a Google Cloud project.
Step-by-step setup
1. In ClientPulse
- Open https://clientpulse.helloaurora.ai/dashboard/integrations/sources.
- Find the Google Ads card and click Connect Google Ads.
2. On Google's consent screen
- You're redirected to https://accounts.google.com. Sign in with the Google account that can see your clients' Google Ads accounts.
- Review the requested permission — Google Ads read access (
adwords). ClientPulse cannot change campaigns, budgets, or bids. - Click Continue / Allow.
- Google redirects you back to the Sources page with the connection saved.
3. Verify it's working
- The Google Ads card flips to Connected · data pipeline v1.1.
- That label is intentional and honest: the OAuth handshake is complete, but no campaign data is being read yet — there is no scheduled poll until the v1.1 emitter ships.
- When the poller lands, your existing connection starts emitting signals automatically. No reconnect needed.
What you'll be able to do with it once the pipeline ships
- See "campaign underperforming", "ROAS dropped", and "quality score drop" signals per client.
- Catch spend-pace problems before they burn a client's budget.
- Fold paid-search health into the overall churn score for marketing clients.
Common pitfalls
- Pitfall: "I connected but no signals are showing." Fix: Expected today. Google Ads is connectable but its data pipeline is a v1.1 item — the connection is stored and ready; signals begin once the poller ships.
- Pitfall: Connecting an account that can't see your client accounts. Fix: Use the Google account (ideally a manager / MCC account) that has access to the client ad accounts you manage.
Restrictions
- Read-only. ClientPulse does not create, pause, or edit campaigns, budgets, or bids.
- No data is read until the v1.1 polling pipeline ships — connecting early only saves you a step later.
Need help?
Email support@helloaurora.ai — and let us know Google Ads matters to you so we prioritise the pipeline.