Connecting Google or an AI key to your store looks like a two-minute formality. And it is — until it isn’t. Here are the mistakes that most often end in “the module stopped working and I don’t know why,” and how to nip them in the bud.
Mistake 1: pasting the key without testing it
The classic one. You copy the key, paste it, save, and since the form doesn’t validate anything, everything looks fine. The failure shows up days later, when the module tries to use it in the middle of a real task. A key should be tested the moment you add it — if the place you’re pasting it into doesn’t offer connection testing, add that validation to your manual checklist.
Mistake 2: the same key copied into three modules
It works… until you regenerate the key with the provider. Now you’ve got three stale copies scattered across the store, and three separate failures showing up at three different times. Simple rule: every credential should live in a single place that everything else reads from.
Mistake 3: connecting the wrong Google account
With several Google accounts logged into your browser, OAuth connects whichever one is active at that moment — and that’s not always the one with access to your store’s Search Console or Analytics property. If a module connects “fine” but doesn’t pull in any data, this is the first thing to suspect: which account did you authorize with?
Mistake 4: losing everything on uninstall
Many modules wipe their configuration on uninstall — connections and keys included. One accidental uninstall, one reinstall to tidy things up, and you’re reconnecting everything from scratch. Before uninstalling any module that holds credentials, check what happens to them.
Mistake 5: not knowing what’s connected
The silent mistake: without a connections inventory, you don’t discover something broke until a report comes back empty. A status panel — what’s connected, what isn’t — turns surprise breakages into early warnings.
- Test every key the moment you add it, not when it fails.
- One credential, one place — no copies scattered across modules.
- Check which Google account you’re authorizing the OAuth with.
- Before uninstalling, confirm what happens to tokens and keys.
- Keep a dashboard where you can see the status of every connection.
The shortcut: let the hub handle it for you
Zeyvro Connections — free — is built to counter this exact list: direct OAuth with Google (Search Console and Analytics), connected once and reused by every Zeyvro module; an AI key manager (Gemini, OpenAI, Claude) with built-in connection testing; its own status panel and a widget on the PrestaShop Dashboard to see what’s connected; and tokens and keys that survive an uninstall — reinstall it and everything’s right where you left it.
💡 The long version of why centralizing matters: connecting Google to PrestaShop once — what a connections hub is.
Frequently asked questions
How do I know if my AI key is still working?
By testing it actively, not waiting for it to fail. Zeyvro Connections includes built-in connection testing for Gemini, OpenAI, and Claude.
What happens to my connections if I uninstall Zeyvro Connections?
Nothing: tokens and keys are NOT deleted on uninstall. If you reinstall it, there’s no need to reconnect anything.
Does Zeyvro Connections change anything customers see in my store?
No. The front office doesn’t change at all — it’s infrastructure for other modules, not a customer-facing feature.
How much does it cost?
Nothing. It’s free, with no license and no sign-up required.
Five mistakes, one solution: connect once, test instantly, and keep the status in view.
Install Zeyvro Connections for free →Zeyvro builds PrestaShop 8 modules from a real store in production. Unobfuscated code.