Meta Ads

What it does in ClientPulse: Will read each client's Meta (Facebook / Instagram) ad account and flag underperforming campaigns, ROAS drops, creative fatigue, and spend-pace problems — early signals that a paid-media 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 Meta account that has access to your clients' ad accounts.

Before you start (prerequisites)

• Account requirement: A Meta Business account with access to the ad accounts you manage for clients.
• You'll need a role (Admin or Analyst) on the Meta ad accounts you want ClientPulse to read.
• Cost: Free on ClientPulse's side. ClientPulse handles the Meta app registration — you don't need to create one.

Step-by-step setup

1. In ClientPulse

1. Open https://clientpulse.helloaurora.ai/dashboard/integrations/sources.
2. Find the Meta Ads card and click Connect Meta Ads.

2. On Meta's consent screen

1. You're redirected to Facebook's login + permissions screen. Sign in.
2. Review the requested access — read-only access to ad-account insights (ads_read). ClientPulse cannot create, pause, or edit campaigns or spend.
3. Click Continue.
4. Meta redirects you back to the Sources page with the connection saved.

3. Verify it's working

• The Meta 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" and "ROAS dropped" signals per client.
• Catch creative fatigue and spend-pace problems before the client notices.
• Fold paid-media health into the overall churn score for marketing clients.

Common pitfalls

• Pitfall: "I connected but no signals are showing." Fix: Expected today. Meta 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: Picking the wrong Meta Business account during consent. Fix: Use the account that actually has access to your clients' ad accounts. You can disconnect and reconnect from the source card if you pick the wrong one.

Restrictions

• Read-only. ClientPulse does not create, pause, or edit campaigns, budgets, or creatives.
• 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 Meta Ads matters to you so we prioritise the pipeline.