Best Practices

Recommended setup

Use a focused start date

Set your start date to the beginning of your current growth period rather than your account creation date. This keeps syncs fast and your destination tidy — especially important for accounts with large subscriber histories.

Build a subscriber master view

Add Subscribers, Tag subscribers, and Form subscribers as separate sources in one data flow, then use Join transformations to create a single enriched subscriber record. This gives you segmentation and acquisition data in one place.

Separate purchase tracking

Keep Purchases in its own data flow with its own destination sheet or table. Purchase records have a different refresh cadence than subscriber data and benefit from clean, dedicated storage for revenue analysis.

Data refresh and scheduling

Daily refresh for active campaigns

If you're running active broadcast campaigns or growing your list quickly, a daily refresh gives you up-to-date subscriber counts and new purchase records without hammering the API.

Weekly refresh for evergreen data

Sequences, forms, tags, and email templates change infrequently. A weekly sync is sufficient for these entities and keeps your data flow runs lean.

Performance optimization

Don't pull all entities in one data flow

Large accounts can slow down significantly when syncing Subscribers and all association entities together. Split high-volume entities (Subscribers, Purchases) from metadata entities (Tags, Forms, Sequences) into separate flows.

Use Aggregate for revenue summaries

Rather than exporting every purchase record to a reporting sheet, use Coupler.io's Aggregate transformation to sum purchase totals by product or month. This keeps destination files readable and report-ready.

Common pitfalls

Don't confuse the Custom fields entity with actual custom field values. It only returns field definitions. Subscriber-level values live inside the Subscribers entity — missing this is a common source of confusion when building subscriber profiles.

Do

• Join Form subscribers with Subscribers to get full subscriber details per form
• Use the state field to filter for active subscribers in your reports
• Test with a manual run on a short date range before scheduling large syncs

Don't

• Expect open rates or click data from the Broadcasts entity — Kit's API doesn't provide engagement metrics
• Use the public API key instead of the API Secret — it won't authenticate correctly
• Pull the full subscriber history on every scheduled run if your list has grown significantly