Data Overview

Kit exposes a broad set of entities through its API, covering your audience, campaigns, automations, and commerce data. Here's what each entity contains and how you can use it.

Entities summary

Entity	What it contains
Subscribers	Subscriber profiles, status, tags, and signup dates
Broadcasts	Campaign metadata, send dates, and subject lines
Sequences	Sequence names, IDs, and creation dates
Forms	Form names, types, embed codes, and creation dates
Tags	Tag names and IDs
Form subscribers	Subscriber-to-form associations
Sequence subscribers	Subscriber-to-sequence associations
Tag subscribers	Subscriber-to-tag associations
Purchases	Transaction IDs, product names, amounts, and subscriber IDs
Segments	Segment names, IDs, and creation dates
Custom fields	Field keys, labels, and creation dates
Email templates	Template names, IDs, and creation dates
Current account	Account name, plan, and primary email

Subscribers

Subscriber fields

Field	Description
id	Unique subscriber ID
first_name	Subscriber's first name
email_address	Email address
state	Subscription status (active, inactive, etc.)
created_at	Date the subscriber was added
fields	Custom field values for this subscriber
tags	Tags assigned to the subscriber

Broadcasts

Broadcast fields

Field	Description
id	Unique broadcast ID
created_at	Date the broadcast was created
subject	Email subject line
description	Internal description or label
content	Email body content
public	Whether the broadcast is publicly accessible
published_at	Date the broadcast was sent

Purchases

Purchase fields

Field	Description
id	Unique purchase ID
subscriber_id	ID of the purchasing subscriber
product_id	ID of the purchased product
product_name	Name of the product
purchase_total	Total transaction amount
currency	Transaction currency
status	Purchase status (paid, refunded, etc.)
created_at	Date of the transaction

Forms

Form fields

Field	Description
id	Unique form ID
name	Form name
type	Form type (embed, landing page, etc.)
format	Visual format of the form
embed_js	JavaScript embed code
created_at	Date the form was created

Tags and segments

Tag fields

Field	Description
id	Unique tag ID
name	Tag name
created_at	Date the tag was created

Segment fields

Field	Description
id	Unique segment ID
name	Segment name
created_at	Date the segment was created

Common data combinations

• Subscribers + Tag subscribers — Join these to see which tags each subscriber holds, useful for segmentation audits
• Subscribers + Purchases — Join on subscriber ID to build a revenue-per-subscriber view
• Form subscribers + Forms — Join to analyze which forms drive the most signups
• Broadcasts + Subscribers — Combine to track campaign reach over time

Use cases by role

Content creators

• Track subscriber growth over time by exporting the Subscribers entity regularly
• Monitor which opt-in forms convert best by combining Forms and Form subscribers
• Review broadcast history to see which subject lines you've used and when campaigns went out

Finance teams

• Export Purchases data to Google Sheets or BigQuery to track product revenue and refund rates
• Join Purchases with Subscribers to identify your highest-value audience segments
• Use Aggregate transformations to sum purchase totals by product or time period

Marketing analysts

• Combine Tag subscribers with Subscribers to analyze segment sizes and overlap
• Export Sequences data to map out automation coverage across your audience
• Feed subscriber and broadcast data into AI tools like ChatGPT or Claude for audience insights

Platform-specific notes

• The start_date parameter controls how far back Coupler.io fetches data — use the date picker to avoid pulling years of historical records unnecessarily
• The Form subscribers, Sequence subscribers, and Tag subscribers entities return association records, not full subscriber profiles — join them with the Subscribers entity for enriched data
• Custom fields returns field definitions (keys and labels), not the values — subscriber-level custom field values appear inside the Subscribers entity under the fields object
• Kit's API does not return per-broadcast engagement metrics (opens, clicks) — those must be viewed inside the Kit dashboard