Google Cloud SQL

Datafly Signal delivers events to Google Cloud SQL for fully managed relational database storage on Google Cloud, supporting MySQL, PostgreSQL, and SQL Server engines.

Prerequisites

Before configuring Google Cloud SQL in Signal, you need a GCP project with a Cloud SQL instance, a database and table, and a database user.

Create a GCP Account and Project

Sign up at cloud.google.com if you don’t already have an account.
Create a new project or select an existing one in the GCP Console.
Note the Project ID.

Enable the Cloud SQL Admin API

Go to APIs & Services > Library.
Search for Cloud SQL Admin API.
Click Enable.

Create a Cloud SQL Instance

Go to the Cloud SQL console.
Click Create Instance.
Choose a database engine: MySQL, PostgreSQL, or SQL Server.
Enter an Instance ID (e.g. datafly-events).
Set the Root password (or default user password).
Select a Region and Zone.
Choose a Machine type based on your expected workload.
Under Connections, configure:
- Public IP — enable if Signal connects from outside GCP. Add authorised networks (Signal’s IP addresses).
- Private IP — enable if Signal runs within the same VPC.
Click Create Instance.
Note the Instance connection name from the instance overview (format: project:region:instance).

The instance connection name (e.g. datafly-analytics:us-central1:datafly-events) is used by the Cloud SQL Auth Proxy and is the primary identifier for Signal’s connection.

Configure Authorised Networks

If using public IP:

Open the Cloud SQL instance details.
Go to Connections > Networking > Authorised networks.
Click Add a network.
Enter the IP addresses of your Signal deployment.
Click Save.

Create a Database and Table

Connect to the instance and create the target database and table. For PostgreSQL:

CREATE DATABASE datafly_events;
 
\c datafly_events
 
CREATE TABLE events (
  event_id VARCHAR(64) PRIMARY KEY,
  type VARCHAR(20),
  event VARCHAR(256),
  anonymous_id VARCHAR(64),
  user_id VARCHAR(256),
  timestamp TIMESTAMPTZ,
  received_at TIMESTAMPTZ,
  context JSONB,
  properties JSONB,
  traits JSONB,
  source_id VARCHAR(64),
  integration_id VARCHAR(64)
);
 
CREATE INDEX idx_events_timestamp ON events (timestamp DESC);

Create a Database User for Signal

CREATE USER datafly_signal WITH PASSWORD 'your_secure_password';
GRANT INSERT ON TABLE events TO datafly_signal;

Configuration

Field	Type	Required	Description
`connection_name`	string	Yes	The instance connection name (e.g. `project:region:instance`).
`database`	string	Yes	The target database name.
`table_name`	string	Yes	The target table name to insert rows into.
`username`	string	Yes	The database username for authentication.
`password`	secret	Yes	The database password for authentication.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Google Cloud SQL or filter by Cloud Storage.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/google_cloud_sql/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Google Cloud SQL",
    "variant": "default",
    "config": {
      "connection_name": "datafly-analytics:us-central1:datafly-events",
      "database": "datafly_events",
      "table_name": "events",
      "username": "datafly_signal",
      "password": "your_secure_password"
    },
    "delivery_mode": "server_side"
  }'

Testing

Enable the integration in Signal and trigger a test event on your website.
Connect to the Cloud SQL instance and query the target table:

SELECT * FROM events ORDER BY timestamp DESC LIMIT 10;

Verify that event rows are appearing with correct data.
In Signal, check the Live Events view to confirm delivery status shows as successful.

Troubleshooting

Problem	Solution
Events not appearing in the table	Verify the connection name, database, and table name are correct.
Connection refused / timeout	Check that Signal’s IP is in the authorised networks list. If using private IP, verify VPC connectivity.
`Authentication failed`	The username or password is incorrect. Verify the credentials.
`INSERT permission denied`	The database user lacks INSERT permission. Run `GRANT INSERT ON TABLE events TO datafly_signal;`.
`Relation does not exist`	The table does not exist. Verify the table name and that it was created in the correct database.
Connection name format error	The connection name must be in the format `project:region:instance`. Check the Cloud SQL instance overview page.
SSL/TLS errors	Cloud SQL connections use SSL by default. Ensure your Signal deployment supports the required TLS version.

Visit Google Cloud SQL documentation for full API reference, connection methods, and backup configuration.

Google Bigtable Google Firestore