Circle.so connector

Use your Circle data for reporting, automation and AI.

Data Panda brings your Circle community together with the data from the rest of your business. From one place, we turn the spaces, members, events and paywall transactions side of your product into dashboards, automations, AI workflows and custom apps your community, marketing and finance teams use every day.

About Circle.so

The branded home for creator and brand communities.

Circle launched publicly on August 10, 2020 after an eight-month private beta, and is headquartered in Brooklyn, New York. The three co-founders, Sid Yadav (CEO), Andrew Guttormsen and Rudy Santino, met at Teachable, where Yadav was VP of Product and Guttormsen ran growth and marketing.

Where Discord is the open community your fans drift into and Slack is the workspace your employees log in to, Circle is the paid, branded home a creator or brand puts up on their own domain. Spaces carry the discussions, members hold the profiles and roles, events run inside the platform, and paywalls turn the whole thing into a recurring-revenue product. Live streams and payments landed in 2021 and native courses arrived in 2023, which is when Circle stopped being a forum tool and started being the operating system for a paid community business. Customers include Pat Flynn, Ali Abdaal, Tim Ferriss, Brendon Burchard, Jay Shetty and Mel Robbins on the creator side, and SpaceX and Oprah Daily on the brand side. By the end of 2023 the platform reported 4.1 million active members across more than 10,000 communities. Our connector pulls spaces, members, events, courses and transaction data into your warehouse, so the same questions a SaaS company asks about its product (who pays, who stays, who shows up) become answerable for the community business too.

What your Circle.so data is for

What you get once Circle.so is connected.

Space, member and revenue reporting

Spaces, members, events, courses and paywall transactions in one place, instead of three exports at month-end.

Active versus dormant spaces per category, with the cut-off you choose
Paid-member growth, churn and MRR by tier and cohort
Course enrolment, completion and drop-off per lesson

Member-lifecycle automation

Let Circle data trigger the housekeeping a small community team would otherwise do by hand.

Auto-flag paid members who never posted in their first 30 days for a personal nudge
Tag-based hand-off when a member upgrades, downgrades or churns
Welcome and event-reminder flows triggered by space-join and RSVP timing

AI workflows

Put your community topology behind AI that helps members and the host team find each other faster.

Space-topic classification for cleaner directory and search
Question-routing model that points new members at the right space or course module
Member-health score that combines login frequency, post activity and paywall status

Custom apps on your data

Small internal tools on your community data for community, marketing and finance teams.

Power-member view for the host with rank, tenure and contribution score
Paywall cohort dashboard with MRR, churn and lifetime value per tier
Course-completion app the curriculum lead can act on every week

Use cases

Use cases we deliver with Circle.so data.

A list of concrete reports, automations and AI features we have built on Circle.so data. Pick the one that matches your situation.

Space activity overviewTotal spaces per category, active versus dormant, with the cut-off you choose.

Paid-member cohort retentionJoiners per tier per month, 30-, 60- and 90-day retention, MRR-weighted.

Power-member viewTop contributors per space with role, tenure and paywall tier.

Course completion funnelEnrolments, lesson-by-lesson drop-off and certificate issuance per cohort.

Event RSVP and show-upRSVPs versus actual attendance per event, with no-show patterns by cohort.

Paywall MRR and churnActive subscriptions, upgrades, downgrades and cancellations per pricing tier.

Onboarding to first contributionTime from signup to first post, first comment and first space-join, per cohort.

Member tag hygiene auditTags in use, tags assigned to nobody, members carrying conflicting tag combinations.

Real business questions

Answers you will finally get.

Which paid tiers are retaining?

Subscription, upgrade, downgrade and cancellation events per pricing tier, joined to member activity in the spaces. The host sees which tier delivers the engagement that justifies the price and which tier silently churns inside the renewal window, instead of judging the whole paywall on a single MRR number.

Are our courses being finished or just bought?

Enrolments per course, lesson-by-lesson drop-off and certificate issuance per cohort, alongside the paywall tier each enrolled member sits on. Curriculum decisions (which lesson to rewrite, which course to retire, which one to upsell) start from the actual completion shape, not from the launch-week sales chart.

Where is the conversation happening?

Active versus dormant spaces per category, with the cut-off you pick (30, 60 or 90 days of no post). The community team sees which spaces still pull engagement and which ones are quietly waiting to be archived, so the next directory clean-up starts with a list rather than a feeling.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Community revenue and cost in the same view. MRR per tier, churn per tier and refund rate become numbers you can compare against the platform fee, the moderation hours and the content production cost behind each tier.

For sales leaders

Member-to-pipeline mapping when the community sits next to a B2B product. The team sees which Circle members map to paying accounts elsewhere, which paid members are quietly the strongest advocates, and which prospects are already active in a free space before sales ever calls.

For operations

Space, course and event lifecycle work on data that refreshes with the rest of the warehouse. Dormant spaces, half-finished courses and low-RSVP events come up as a list the host can act on, not as a quarterly clean-up scramble.

Ideas

What you can automate with Circle.so.

Pair with Stripe

Reconcile Circle paywall transactions with Stripe

Circle paywall events (subscription start, upgrade, downgrade, cancellation, refund) are joined to the underlying Stripe charges and invoices in the warehouse, so the finance team sees true MRR per tier, refund rate per cohort and the gap between Circle's reported revenue and Stripe's actual cash. Reconciliation stops being a manual export-and-VLOOKUP exercise at month-end.

Pair with HubSpot

Match HubSpot contacts to Circle members

Circle member emails and tags in the warehouse get joined to HubSpot contact records, so the customer-success and marketing teams see which paying contacts are quietly active in the community, which never joined a single space, and which power members have no contact record at all. The CRM stops being blind to the community and the community stops being a separate planet.

Pair with Mailchimp

Sync Circle member tags into Mailchimp segments

Circle member tags, paywall tier and engagement score in the warehouse are pushed into Mailchimp as segment fields, so newsletter and lifecycle campaigns target real cohorts (free members who never posted, paid members in their first 30 days, churned members from the last 90) instead of one undifferentiated list. The host stops sending the same email to the entire base every week.

Pair with Klaviyo

Trigger Klaviyo flows on Circle paywall events

Paywall events from Circle (cancellation, downgrade, course-purchase without enrolment) are streamed into Klaviyo as triggers for win-back, recovery and onboarding flows. The marketing team gets the same lifecycle automation playbook that an ecommerce store has, applied to a paid-community business, without the host having to wire it up by hand in a Zap.

Pair with Slack

Bridge Circle community signals into a Slack channel

High-signal Circle events (a power member posting a sensitive question, a wave of cancellations on one tier, a course cohort stalling at the same lesson) post into the right Slack channel for your community or success team, with member handle, space and post context attached. The team works inside Slack where the rest of the company sits, while members keep living in Circle where they pay to be.

Pair with Calendly

Match Calendly bookings to Circle members

Calendly bookings (1-on-1 coaching, office hours, onboarding calls) are joined to Circle member records in the warehouse, so the host sees which paid members never book a session, which low-tier members are quietly heavy bookers (and could upsell), and which calls correlate with retention beyond 90 days. The coaching side of the business gets reported alongside the community side, not on a separate spreadsheet.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Circle.so data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Circle.so to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Circle.so connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Does the connector pull post content or just structure?

The default Peliqan Circle pull covers the structural and transactional surface: spaces, members, events, courses, paywall transactions and high-level activity counts. Post and comment content is a separate scope conversation, because community conversation is sensitive data and most of the reporting questions our customers raise (paid retention, course completion, space-level engagement, member-to-revenue health) are answered without it. We recommend starting on structure and only widening scope if a specific use case needs it.

How is this different from the Discord connector?

Discord is the open community your fans drift into; Circle is the paid, branded home a creator or brand puts up on their own domain. The Discord connector is built around servers, channels, members and roles, with the question of mod load and channel sprawl. The Circle connector is built around spaces, members, events, courses and paywall transactions, with the question of paid retention and course completion. Same warehouse, very different shape.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Circle.so setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors