Marketing insights: all your tools in one place
See GA4, Search Console, Google Ads, Meta Ads, Clarity and more inside Customer360: next to what Customer360 measured on your site.
Intelligence → Marketing insights shows the numbers from every tool you connect, refreshed every 6 hours, so you don't have to open each dashboard. Customer360 only asks for read-only access and never changes your accounts.
- Paid ads: Meta Ads and Google Ads spend, clicks, leads and campaigns. Customer360 adds what it measured on your site from the same channel, so you see the real cost per lead and return on ad spend.
- Search: Google Search Console and Bing: clicks, impressions, position, top queries and pages.
- Website analytics: GA4 (next to Customer360's own users and sessions), Microsoft Clarity rage and dead clicks, Cloudflare visits and PageSpeed scores.
- Social: YouTube and Telegram.
- Lead sources and Tags & pixels: where leads came from, and which pixels receive Customer360's leads and purchases.
Connect a tool
- 1Open Setup → Integrations (or click Connect on a card here).
- 2GA4, Search Console and Google Ads: click Connect with Google and sign in with the Google account that has access. Meta Ads: Connect with Facebook.
- 3Pick the property or ad account to read.
- 4The first sync runs straight away; after that every 6 hours. Use Sync now any time.
Tip: Clarity and Cloudflare need an API token in their integration settings (Clarity: Settings → Data Export; Cloudflare: an Account Analytics read token).
Tags already on your website
If your site's code already has GTM, GA4, Meta Pixel, Clarity or another tag, Customer360 finds it and never loads it a second time, so page views and events aren't counted twice. It still sends Customer360's leads and purchases to it. Integrations lists tags it found that aren't connected yet, and warns you about tags that start before visitors give consent.
Good to know: Meta Pixel, Clarity, TikTok, LinkedIn and Microsoft Ads don't follow Google Consent Mode. If they're in your site's code they may run before consent: add them in Customer360 instead so they load only after the visitor agrees.