A Simple Analytics source plugin for CloudQuery that loads raw page view and event data from Simple Analytics to any database, data warehouse or data lake supported by CloudQuery, such as PostgreSQL, BigQuery, Athena, and many more.
Loading plugin documentation
CloudQuery's use of cookies
We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
mywebsite.com to a PostgreSQL database. See Quickstart for more information on how to configure the source and destination.kind: source
spec:
name: "simple-analytics"
path: "simple-analytics/simple-analytics"
registry: cloudquery
version: "v2.0.0"
# use this to enable incremental syncing
# backend_options:
# table_name: "cq_state_simpleanalytics
# connection: "@@plugins.postgresql.connection"
tables:
["*"]
destinations:
- "postgresql"
spec:
# plugin spec section
user_id: "${SA_USER_ID}"
api_key: "${SA_API_KEY}"
websites:
- hostname: mywebsite.com
metadata_fields:
- fieldname_text
- fieldname_int
# - ...
user_id (string) (required)sa_user_id...api_key (string) (required)sa_api_key...websites (list) (required)hostname (string) (required)metadata_fields ([]string) (optional)["path_text", "created_at_time"]. If not specified, no metadata fields will be synced.start_date (string) (optional)period, if set).end_date (string) (optional)period (string) (optional)start_date if it is not specified. If start_date is specified, duration is ignored. Examples:7d: last 7 days3m: last 3 months1y: last yearconcurrency (integer) (optional) (default: 1000`)backend_options must be set in the spec (as shown in the example config above). By default, incremental syncing is turned off. Also note that this will introduce duplicates, unless the destination is using overwrite-delete-stale mode. Care should be taken to remove these duplicates after loading them. For more information, see Managing Incremental Tables.select
path,
count(*)
from
simple_analytics_page_views
where
hostname = 'mywebsite.com'
and is_robot is false
and added_iso between '2023-01-01'
and '2023-02-01'
group by
path
order by
count desc
limit
10
+----------------------------------+---------+
| path | count |
|----------------------------------+---------|
| / | 100333 |
| /page | 91234 |
| /another-page | 84567 |
| /blog/introduction | 74342 |
| /index | 69333 |
| /another/page | 64935 |
| /deeply/nested/page | 50404 |
| /yet/another | 42309 |
| /some/page | 34433 |
| /about-us | 20334 |
+----------------------------------+---------+
select
added_iso,
datapoint,
path,
browser_name
from
simple_analytics_events
order by
added_iso desc
limit
5
+-------------------------+-----------+-----------------------------------------------+---------------+
| added_iso | datapoint | path | browser_name |
|-------------------------+-----------+-----------------------------------------------+---------------|
| 2023-01-23 19:32:25.68 | 404 | /security | Google Chrome |
| 2023-01-22 20:23:23.379 | 404 | /blog/running-cloudquery-in-gcp | Google Chrome |
| 2023-01-19 12:04:57.095 | 404 | /docs/plugins/sources/vercel/configuration.md | Brave |
| 2023-01-19 12:04:36.567 | 404 | /docsss | Firefox |
| 2023-01-19 01:50:19.259 | 404 | /imgs/gcp-cross-project-service-account | Google Chrome |
+-------------------------+-----------+-----------------------------------------------+---------------+
make test
make lint
make gen-docs
git tag v1.0.0 to create a new tag for the release (replace v1.0.0 with the new version number)git push origin v1.0.0 to push the tag to GitHubv1.0.0 with the new version number.# -m parameter adds release notes message, output is created in dist/ directory
go run main.go package -m "Release v1.0.0" v1.0.0 .
# Login to cloudquery hub and publish the new version
cloudquery login -t simple-analytics
cloudquery plugin publish --finalize