Getting access to the Reporting Database – StoreFeeder

Getting access

The Reporting Database is available as part of Insights Pro. To have it enabled for your account, contact our sales team at sales@storefeeder.com — they'll confirm pricing and arrange setup.

We will need to whitelist your IP addressess that you wish to use to access the reporting DB so please provide these at this point to ensure you'll be able to access smoothly.

Note: If your IP address changes later, you'll need to send Sales or the Support team the new one before you can reconnect.

Warning: Any tool that's able to access a postgres database is absolutely fine to use, use whatever you feel most comfortable using. However please note this guide specifically explains how to connect using pgAdmin4.

Before you start

You'll need the following before you begin:

Field	What it is
Reporting Database subscription	Arranged with your StoreFeeder Sales representative, including payment.
IP address(es) to whitelist	The public IP address(es) you'll connect from. Give these to Sales before you try to connect — the database will refuse connections from any address that isn't whitelisted.
pgAdmin 4	The client StoreFeeder recommends for connecting. Download it from pgadmin.org if you don't already have it installed.
Connection string	A single PostgreSQL connection string for your Reporting Database, sent to you by Sales once your IP address has been whitelisted.

Step 1: Register a new server in pgAdmin

Open pgAdmin 4. In the left-hand tree, right-click Servers and choose Register > Server…

Step 2: Name the connection

On the General tab, enter a name you'll recognise, for example StoreFeeder Reporting. This name is only shown in your own pgAdmin — it doesn't need to match anything Sales sent you.

Step 3: Enter your connection details

pgAdmin's Connection tab takes your connection string as separate fields rather than as one pasted string, so you'll need to split it into its parts. The connection string Sales sends you follows this pattern:

postgresql://username:password@host:port/database

Switch to the Connection tab and enter each part in the matching field:

Host name/address: the part between @ and the port
Port: the number after the host, before the /
Maintenance database: the part after the final /
Username: the part between postgresql:// and the :
Password: the part between that : and the @

Warning: Copy each part across carefully. A trailing space or a missed character in the host, username or password is a common cause of a failed connection.

Step 4: Save and connect

Click Save. pgAdmin connects immediately — once it has, your Reporting Database appears under Servers in the left-hand tree, and you can expand it to browse its schema.

Troubleshooting

"Unable to connect to server: could not connect to server: Connection timed out"
Your IP address isn't whitelisted yet, or has changed since you gave it to Sales. Confirm your current public IP address and check it with Sales.

"password authentication failed for user"
The username or password doesn't match what Sales sent. Check for extra spaces or characters missed when copying, or contact Sales to have your details resent.

"server closed the connection unexpectedly"
This is usually a temporary network issue. Try connecting again — if it keeps happening, contact StoreFeeder support.

Still stuck? Contact StoreFeeder support with your account name and the exact error message pgAdmin shows. If the problem is with your connection details themselves (a forgotten password, or a new IP address to whitelist), contact your Sales representative instead.