Integrations
Integrations connect a project to the accounts it already has, so BoostUp can read real numbers instead of guessing. Each project has its own connections.
Providers and status
| Provider | What it covers today |
|---|---|
| Search Console and Google Analytics 4 for the project's site | |
| Meta | The Meta Pixel, with the ad account and Facebook Page it belongs to |
The Integrations page of a project shows each connection with its status:
| Status | Meaning |
|---|---|
| Connected | The connection works. The page shows when it was connected and when it last synced |
| Error | The last sync could not read anything. The error is shown so the BoostUp team can fix it |
| Disconnected | The connection was removed. Nothing is read |
Other accounts on the page (for example WordPress, Google Ads or email marketing) are not connected yet.
How a project is connected today
Self-serve connection (signing in to Google or Meta from the app) is coming. Until then the BoostUp team connects your project for you: we import an existing token for your account and attach it to your project. For Google we check that the token can read your Search Console site before we save it, then run a first sync.
To get connected, open a ticket in Support with your project and the accounts you want to connect. The step-by-step setup we follow is in the runbooks:
What we read
Google. The token is limited to two read-only scopes:
https://www.googleapis.com/auth/webmasters.readonly(Search Console)https://www.googleapis.com/auth/analytics.readonly(Google Analytics)
With them we read search performance (clicks, impressions, CTR, position by query, page, country and device) and GA4 reports (sessions, users and conversions by channel and landing page). See Analytics for the date windows and how often we sync.
Meta. The connection holds a system user token, plus the IDs of your pixel, ad account and Facebook Page. Today we read the pixel: its name and when it last received an event. Reading ads and pages is coming.
What we never do
- We never change anything in your Google or Meta accounts through these connections. The Google scopes are read-only.
- We never call Google when you open the Analytics page. Numbers come from the nightly sync.
- We never show a token in the app or in an API response. Only the non-secret IDs (site, property, pixel, ad account, page) are visible.
- We never give a token to your AI employee. The employee asks the BoostUp API to act, and the API checks your role, your budget and approvals first.
Where tokens live
Tokens are stored in the BoostUp database, encrypted at rest. They are decrypted only when BoostUp calls Google or Meta for that project. Each connection belongs to one project in one organization, and the database keeps other organizations from reading it.
Disconnecting
Ask Support to disconnect a project. A disconnected connection is no longer synced. You can also revoke BoostUp's access from your Google or Meta account at any time; the next sync then fails and the connection shows an error.
If you delete your account, the connections and their tokens are deleted with your organization. See Delete your account.