Make your trial count. Start with a quick win. (3/3)

Three easy ways to move forward today

Product: Customer.io
Sent from: customer.io
Sent: 2 September 2026
Notes: Notes on this email ↓

Activation Nudge

No dark-mode styles — this email renders the same in a dark client.

Three easy ways to move forward today  

Customer IO logo ( https://customer.io/ )

image: person on laptop ( https://fly.customer.io/workspaces/last/journeys/home )

***********************
Let’s get you sending
***********************

Hey Emre,

Let's help TinyAnalytics start sending messages. If you’re wondering what to focus on next, here are three common paths teams take at this stage. Pick what feels most useful right now.

Explore Customer.io ( https://fly.customer.io/workspaces/last/journeys/home )

 

------------------------------
I need to send something, fast
------------------------------

 

icon: pen ( https://fly.customer.io/workspaces/last/design-studio/dashboard )



Create your first email in Design Studio. Build responsive, on-brand emails using our in-house editor. Or, connect our MCP server ( https://docs.customer.io/ai/mcp-server/ )to Claude Cowork and have Claude do it. 

Design an email  ➔ ( https://fly.customer.io/workspaces/last/design-studio/dashboard )

--------------------------
I want to connect our data
--------------------------

 

icon: wrench ( https://fly.customer.io/?ai-message=I%20want%20to%20connect%20my%20data%20to%20Customer.io%2C%20but%20I%20don%27t%20want%20to%20over-engineer%20it%20%E2%80%94%20I%20just%20need%20enough%20to%20prove%20the%20tool%20is%20right%20for%20me.%20Here%27s%20my%20situation%3A%20%5BI%27m%20a%20SaaS%20app%20%2F%20ecommerce%20store%20%2F%20service%20business%20%2F%20etc.%5D%2C%20my%20data%20lives%20in%20%5Bour%20database%20%2F%20Shopify%20%2F%20Segment%20%2F%20our%20app%20%2F%20etc.%5D%2C%20and%20the%20first%20thing%20I%20want%20to%20send%20is%20%5Ban%20onboarding%20email%20%2F%20abandoned%20cart%20reminder%20%2F%20appointment%20reminder%20%2F%20purchase%20confirmation%5D.%20What%27s%20the%20minimum%20set%20of%20attributes%20and%20events%20I%20need%20to%20send%20to%20Customer.io%20to%20get%20that%20working%2C%20and%20how%20do%20I%20actually%20send%20them%20given%20my%20tech%20stack%3F%20Thanks! )



You only need a small set of events and attributes to get started. Use our planning worksheet ( https://docs.google.com/spreadsheets/d/1OmSSkX6aW-8-E4PGAwOlZ6uvUDieO3-Qr5_sKBa83ig/edit?usp=sharing ) to bring in a few folks via CSV if you're not ready for a full-on API data integration. 

Set up your data  ➔ ( https://fly.customer.io/?ai-message=I%20want%20to%20connect%20my%20data%20to%20Customer.io%2C%20but%20I%20don%27t%20want%20to%20over-engineer%20it%20%E2%80%94%20I%20just%20need%20enough%20to%20prove%20the%20tool%20is%20right%20for%20me.%20Here%27s%20my%20situation%3A%20%5BI%27m%20a%20SaaS%20app%20%2F%20ecommerce%20store%20%2F%20service%20business%20%2F%20etc.%5D%2C%20my%20data%20lives%20in%20%5Bour%20database%20%2F%20Shopify%20%2F%20Segment%20%2F%20our%20app%20%2F%20etc.%5D%2C%20and%20the%20first%20thing%20I%20want%20to%20send%20is%20%5Ban%20onboarding%20email%20%2F%20abandoned%20cart%20reminder%20%2F%20appointment%20reminder%20%2F%20purchase%20confirmation%5D.%20What%27s%20the%20minimum%20set%20of%20attributes%20and%20events%20I%20need%20to%20send%20to%20Customer.io%20to%20get%20that%20working%2C%20and%20how%20do%20I%20actually%20send%20them%20given%20my%20tech%20stack%3F%20Thanks! )

-----------------------
I want to explore first
-----------------------

 

icon: compass ( https://academy.customer.io/catalog )



Not a fan of docs? Academy does it differently: real scenarios, real workflows, zero jargon. See how teams automate journeys and build segments that convert.

Explore Academy  ➔ ( https://academy.customer.io/catalog )

No more losing sleep over your email strategy. You've got the tools. Send the thing.

Any questions along the way? Just reply to this email.

Best,
Gabby at Customer.io

Customer IO logomark ( https://customer.io/ )

LinkedIn ( https://www.linkedin.com/company/customer-io/ )  |  X ( https://x.com/customerio )  |  YouTube ( https://www.youtube.com/@customerio )  |  Instagram ( https://www.instagram.com/customer.io/ )

Don't want to receive onboarding and product news updates? Review your email preferences ( https://track.customer.io/manage_subscription_preferences/dgT6twgBAKqZOqmZOgGgYxBQBNQdl3KoP5vySWQ= ). Or, you can unsubscribe from everything ( https://track.customer.io/unsubscribe/dgT6twgBAKqZOqmZOgGgYxBQBNQdl3KoP5vySWQ= ).
View in your browser ( https://track.customer.io/deliveries/dgT6twgBAKqZOqmZOgGgYxBQBNQdl3KoP5vySWQ= )

Built with Design Studio ( https://customer.io/design-studio ), sent with Customer.‌io

© 2026 Peaberry Software, Inc., 9450 SW Gemini Dr., Suite 43920, Beaverton, Oregon 97008

Accession: nse/customerio/2026-09-02/315
From: Gabby at Customer.io · welcome@customer.io
Sent: 2 September 2026 · 17:00 UTC

This email by the numbers

Counted from the email itself. Medians are across the whole archive.

Length: 272 words; median 167 words across the archive
Links: 13; median 8 links across the archive
Images: 6; 30 KB · 6 with alt text
Width: 600 px; with mobile styles
Arrived: day 3; median day 14 across the archive

Notes on this email

The subject line is 52 characters, considerably longer than the archive median of 35.

What works

Copy
The average sentence length is 6.8 words, shorter than the archive median of 8.1.
Design & layout
The email includes 6 images, fewer than the archive median of 8.
Design & layout
The total image weight is 30 KB, far below the archive median of 137 KB.
Design & layout
The copy uses 4 headings, more than the archive median of 2.

Where it is weaker

Subject & preheader
The subject line is 52 characters, longer than the archive median of 35.
Copy
The email body contains 272 words, higher than the archive median of 170.
Copy
The reading grade is 5.1, lower than the archive median of 5.8.

Trim the subject line to be closer to the archive median length.

Drafted from counted facts by a language model, for Mert Özeren, who is responsible for it. Written 2 September 2026. It describes only what this archive counted, and has no access to how the email performed.

Something wrong with these notes?