Docs › Settings

Integrations

The one screen where you connect your analytics, your website and your publishing tools — and the map of which guide to open for each.

#In 10 seconds

• Two groups: what EOMA reads from, and where it can publish for you.
• Each row is one connection with one button. Connecting is always the same shape; only the credentials differ.
• Every row works on every plan except Google Search Console, which starts at Starter.

#Before you start

• You must be the brand owner. Everyone else sees "Owner only" instead of a button, on every row that does something — that lock is how the page tells you, and it appears on each row rather than once at the top.
• Have the account you are connecting open in another tab. Several of these ask you to copy a token out of the other product.
• Your plan matters for one row only. Google Analytics and the five publishing connections (WordPress, GitHub, Vercel, HubSpot, Wix) work on every plan, Free included. Google Search Console starts at Starter: on Free its card shows a lock and Upgrade your plan instead of Connect.
• Nothing else. Connections can be made on your first day or your hundredth.

#Steps

#1 — Open Settings, then Integrations

┌─ Settings ───────────────┬────────────────────────┐
│  WORKSPACE               │  Analytics & Search    │
│    Plan & Usage          │  Google Analytics 4    │
│    Brand Profile         │            [ Connect ] │
│  ● Integrations   ← here │  Google Search Console │
└──────────────────────────┴────────────────────────┘

#2 — Find the row you want and press its button

The button tells you which kind of connection it is. Connect starts a Google or GitHub sign-in in a new window. Connect on WordPress or Vercel opens a short panel that walks you through creating a token in that product first.

#3 — Finish the second step where there is one

Some connections are not done when the sign-in is. Google Analytics returns and asks you to pick properties. Search Console asks you to pick one or more properties. GitHub asks you to pick a repository and branch. Vercel asks you to pick a project. Until you do, the row keeps showing that request instead of a connected label.

Google Analytics, Search Console and GitHub also let you change that choice later: the connected row carries an Edit button beside Disconnect, and it reopens the same picker with your current selection already ticked.

#4 — Open the guide for the one you are connecting

Each connection has its own page with the exact clicks, the permissions it asks for, and what EOMA does with the access. They are listed under Related and in the table below.

#What you'll see

#The line at the top

"Connect your site and accounts; drafts you approve go live from here on their own." Below it the page goes straight into the groups — there is no introductory card.

If your site is already connected, one panel sits above the groups: "Your site is connected", confirming that approved fixes publish themselves. If nothing is connected yet, that space is empty.

#"Analytics & Search"

"Connect your data sources so EOMA can read your traffic, your search results and how your content performs." Two rows: Google Analytics · Google Search Console. A third row, Google Drive, appears only if your brand connected Drive before; it keeps its Disconnect button there. See Google Analytics, Search Console, Google Drive.

#"Publishing · CMS & sites"

"Where EOMA can publish pages, posts and site files for you once you approve them." Five rows: WordPress · GitHub · Vercel · HubSpot · Wix. See WordPress, GitHub, Vercel.

There is no social accounts group: EOMA does not publish to social profiles. It reads public social posts for Social Listening, which needs no account of yours, and it writes to your own site through the publishing rows above.

#The right-hand side of every row

This is the whole state of the connection, in one place:

#Reading the numbers

Only one number appears on this screen.

"Connected · 3 properties" on Google Analytics. Three GA4 properties are attached to this brand, and the traffic figures on Web analytics are the sum across all three. That matters more than it looks: attaching a property you do not own the traffic of will quietly inflate every number downstream, and attaching none means Web analytics has nothing to show even though the row says connected. Press Edit and check the list matches the sites this brand actually is.

Everything else here is a state, not a measurement. The useful reading is the negative one: a row that shows "Select properties", "Select Site", "Select repo" or "Select project" is not connected in any way that does work. The sign-in succeeded and the choice never got made, so EOMA holds an access token pointing at nothing. It looks half-green and behaves like off.

#When it goes wrong

#Related

• Google Analytics — the most common first connection
• What EOMA does and what you do — what access buys you