Routy

Add channel

Pick the vendor you want to pull spend and delivery numbers from. Choosing a tile opens a panel that walks you through connecting it — you stay on this screen the whole time, and nothing is saved until the vendor confirms who you are.

Reading a tile

Each tile is one vendor: its logo, its name and a line about what it does.

A tile marked Coming soon — or with a note like a quarter or a date in place of it — isn't connectable yet. It's shown so you know it's on the way; clicking it does nothing.

Everything else is available. Use the search box to filter the tiles by vendor name.

You can connect the same vendor more than once. One connection is one of your accounts at that vendor, so if you run several ad accounts there, connect each of them.

Credentials

The first step of the panel depends on how the vendor lets you prove who you are. There are two shapes, and the vendor decides which one you get.

Vendors that use a key or token

You get a short form. The fields come from the vendor itself — an API key, sometimes a key plus an account or workspace ID — and each one carries a hint about where to find that value in the vendor's own settings. There's usually a documentation link at the bottom of the step. Required fields must be filled before Connect does anything.

When you submit, Routy checks the credentials with the vendor, live, before saving anything. While it does, the panel says "Checking your credentials with {vendor}…", and then:

What you see What it means
You move to the next step The vendor accepted them.
"{vendor} rejected these credentials. Check them and try again." The vendor said no. Nothing was saved.
"These credentials work but are missing a permission at {vendor}." The key is valid but isn't allowed to read the reporting data. Grant that permission at the vendor, then submit again.
"These credentials do not reach any accounts." Valid, but not attached to any account we can pull from.
A message about the vendor being unavailable The vendor is down or rate-limiting us. Try again in a few minutes; it isn't your credentials.

Nothing is stored until the vendor says yes. A rejected attempt leaves nothing half-finished behind, so retrying is always safe.

Common causes of a rejection: a truncated key (they're long — copy the whole thing), a key from a different account than you meant, a key that was rotated or revoked at the vendor, or one created without reporting permission.

Vendors you sign in to

Some vendors — Google, Meta, Microsoft among them — don't hand out keys to paste. For those there is no form at all. The panel explains what's about to happen and gives you one button: Continue to {vendor}.

"You'll sign in at {vendor} and approve the access Routy needs. Nothing is typed here." The vendor's sign-in opens in this tab and sends you straight back when you're done — you'll see a short "Finishing up" screen and then land back on the account step.

Two things worth knowing:

  • Approve everything the vendor asks you to. If you approve only part of it, the connection can't be finished and you'll be asked to start again.
  • One sign-in can cover several products. A single Google account can back Google Ads, Analytics and Search Console. If that's the case, after signing in you'll be asked which product to connect, because your sign-in genuinely doesn't say.

Choose an account

Your credentials — typed or signed in — may reach more than one account at that vendor. This step lists everything they reach so you can pick one.

Each entry shows:

  • The account name and its ID at the vendor.
  • Its currency — the currency the vendor reports money in, shown exactly as the vendor states it.
  • Its timezone — the timezone that account's daily numbers are counted in. This one matters: every date you'll later see on the connection is expressed in it, and it's often not your own. Routy never converts these dates, because converting them would move spend from one day into another.

Entries already connected are greyed out and marked Already connected — a vendor account can only be connected once.

If your credentials reach exactly one account and it's free to connect, Routy skips this step and connects it for you.

Once the connection is created you're taken straight to it.

Common questions

"Nothing happens when I click a tile"

It's marked Coming soon — the vendor is in the catalog but isn't connectable yet.

"Connect stays greyed out"

A required field is still empty. Every field marked required needs a value.

"It says that account is already connected"

That exact vendor account is already connected on your account. Find it in your connections list — you can't connect it twice.

"It says I've used all my connections"

Your plan includes a fixed number of channel connections and you're at the limit: "You have used {X} of {Y} channel connections on your plan." Disconnect one you no longer need, or change your plan. It counts vendor accounts, not vendors.

"My credentials reach no accounts"

The key is valid but isn't attached to an account we can read. That usually means it was created at an organisation or agency level rather than inside the account you want to pull from.

"I closed the panel by accident"

Nothing is lost unless the connection had already been created. Pick the tile again and start over.

When to escalate

  • A vendor you were told is available shows Coming soon.
  • Credentials that work on the vendor's own dashboard are rejected here.
  • The account list is empty even though the key clearly belongs to an account with campaigns.
  • The quota message doesn't match the number of connections you can actually see.
  • A vendor's form asks for something that doesn't exist at that vendor, or its documentation link is wrong.