Integrations

Every integration uses OAuth, the same secure standard you see when an app asks to "Continue with Google". You click Connect, authorize on the provider's own screen, and CrunchJunky receives a scoped, revocable access token — never your password. Tokens are encrypted at rest, and you can revoke access from either CrunchJunky or the provider at any time. After authorizing, you choose which accounts, properties, or profiles to import. The first sync runs immediately; from then on, data refreshes automatically once a day. The Integrations page shows the health of every connection, so you always know your data is current.

For Google Ads, click Connect on the Google Ads card and authorize with the Google account that has access to the relevant ad accounts. If you manage clients through an MCC, you'll be able to select individual accounts under it — import only the ones you report on. GA4 works the same way: authorize with Google and pick the specific properties you need. Both integrations require that the Google user you authorize with has at least read access to the accounts or properties. If an account doesn't appear in the selection list, it's almost always a permissions issue on the Google side rather than a CrunchJunky one.

Meta Ads connects through Facebook Login. Authorize with a user who has a role on the relevant Business Manager and ad accounts, then select the ad accounts to import. Because Meta periodically requires re-authorization, CrunchJunky watches token validity and warns you before a connection lapses. LinkedIn Ads follows the same OAuth flow. Authorize with an account that has access to the Campaign Manager ad accounts you report on, and select them during setup. As with every integration, you grant read access only — CrunchJunky never makes changes to your campaigns.

Microsoft Ads (Bing), TikTok Ads, and Google Search Console each connect with a single OAuth click on their card in the Integrations page. For Microsoft Ads and TikTok, authorize with a user who has access to the ad accounts and choose which to import. Search Console connects via Google and lets you pick the verified properties whose organic search data you want in reports. All three refresh daily alongside your other sources, and all three appear in the same connection-health view so you can manage your entire stack from one screen.

Most issues come down to one of three causes. First, expired or revoked tokens: if a provider invalidates a token (often after a password change or a permissions update on their side), you'll see a "Reconnect" banner — click it and re-authorize to restore the connection. Second, missing permissions: if an account or property doesn't show up during setup, confirm the user you authorized with has at least read access to it on the provider's platform. Third, a stale sync: if numbers look out of date, check the last-sync time on the Integrations page; you can trigger a manual refresh rather than waiting for the daily cycle. If a connection still won't behave after reconnecting and confirming permissions, contact support at hello@crunchjunky.io with the workspace name and the affected integration, and a real person will help you sort it out.