Connections

Connections is where you link your site to the outside services it uses, such as your email provider, Google and Instagram. Each service has its own card, with a badge that tells you at a glance whether it’s set up. Private keys and passwords you save here are sealed: nobody can read them back, not even you. A few keys are public by design, because visitors’ browsers need them; Saved keys and passwords explains the difference. Who can do this: Admins and Owners. Editors, Contributors and Viewers don’t see Connections.

Open Connections

• In the toolbar (the bar across the top of your site once you’re signed in; see The toolbar), choose Connections.
• Or open the command palette (⌘K, or Ctrl+K on Windows) and choose Connections. The shortcut is T then E (press T, let go, then press E, while you’re not typing in a box; see Keyboard shortcuts).

The window opens on Overview, with every card grouped by kind: Essentials, Google, Social and photos, Ads and conversions, Analytics and Fetchski services. The same list runs down the left side, with a colored dot for each card’s status.

Every card in Connections

The Fetchski services cards are covered below.

How a card works

Choose a card to open it. At the top you see the service’s name, what it does for your site and its badge. Below that are its settings, often with a Setup guide that walks you through the steps on the service’s own website. To go back, choose All connections.

The badges

Each badge describes what’s saved, not what you’re typing. It changes after you choose Save. To be sure a connection works, check the result on the service itself, or on your site: the guide for each card says how. While you have unsaved changes on a card, it shows Unsaved changes. If a card has a mistake that stops you saving, its badge reads Fix errors.

Advanced options

Settings most sites never change fold away under Advanced options, at the bottom of a card. Choose it to open them. Some advanced settings only appear once a switch above them is on.

Saved keys and passwords

Keys, tokens and passwords are sealed when you save. After that, the field shows dots and Saved and encrypted. Nobody can read the value again, so keep your own copy somewhere safe if you need it.

• Replace: type or paste a new value. The box shows “Enter a new value to replace the saved one”. Changed your mind? Choose Cancel.
• Remove: clears the value when you save. The field says “The saved value will be removed when you save.” Choose Undo to keep it.
• An empty field shows “Paste the value”, with the note “Encrypted when you save. It can’t be viewed again afterwards.”
• A value the CMS fills in for you, such as a token from signing in with Google, shows Saved and encrypted (set automatically), or “Not set yet.” before then.

Some values are meant to be public, such as the Google Maps key and the spam protection site key. Those show as plain text, and your site uses them in visitors’ browsers. Site settings has a read-only Integrations (public) tab that lists them.

Save your changes

Choose Save at the top right. Everything you changed, on every card, is saved together. Most changes work right away. To leave without saving, choose Cancel.

Fetchski services

These cards link your site to other Fetchski products. FetchskiAI: the account behind every FetchskiAI feature. Fetchski sets it up, so the card reads Managed by Fetchski and never shows the key. Its FetchskiAI budget shows how much of your site’s AI spending limit is used. Choose Read again to refresh it. If FetchskiAI isn’t set up yet, the card says so: contact Fetchski Support. If Fetchski lets your Owners manage the key, Owners also see a FetchskiAI key field here, sealed like any other key. Code Sandbox: where FetchskiAI can run small programs safely. Fetchski sets it up and manages it, and the card says Managed by Fetchski. If it isn’t set up, the card asks you to contact Fetchski Support. See Code Sandbox. GitHub: optional, and most sites never need it. FetchskiAI can install Skills (ready-made instructions) from GitHub, which allows only so many downloads an hour. Add a GitHub token for installing Skills (optional) only if installing a Skill says GitHub’s hourly limit is used up. To make the token, sign in to GitHub and open Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Give it a name, choose Public repositories for its access, add no permissions, and generate it. Copy the token, paste it into the field, and choose Save. The GitHub card waits until FetchskiAI is on: it says “Turn on FetchskiAI in FetchskiAI settings before setting this up.” and offers Open FetchskiAI settings. Fetchski Engage: only if your business uses Fetchski Engage. Linking takes two steps:

1. Paste the web address you open Fetchski Engage at (such as https://engage.example.com) into Fetchski Engage address, and choose Save. The badge reads Linked, and your Privacy Policy gains a short section about Fetchski Engage.
2. Create an API key for Engage, so it can read your site’s visit and conversion data. See API keys and webhooks. If you’re not sure where Engage takes that key, contact Fetchski Support.

Related screens

Three smaller screens hold settings that need no outside account. You open them from the command palette, or from More connections at the bottom of the list on the left of Connections. Moving between them keeps your unsaved changes, and Save saves them all.

Where to start

Most sites set up these first, in this order:

1. Email notifications, so your forms can reach you.
2. Google Business Profile and Google Reviews, to show your reviews.
3. Instagram, if you post there.

The Set up your site checklist links to the right card for each step. See Set up your site.

Good to know

• Connections stays private. Only people who can open Connections see it. Visitors only ever get the public keys listed on Integrations (public), never your private keys or passwords.
• Some cards come with a version line. You don’t need it day to day. If Fetchski Support asks which version a card uses, read it from that line.
• Lost a key? Create a new one on the service’s website, then use Replace.
• Who can change what. Admins and Owners can open and save Connections. See What each role can do.

Related