Newsletter sends create the cleanest humps in indie analytics, if you pin the right week. Pin too short and you call a winner before Sunday purchases land. Pin too long and you blend three issues into one fake “email channel” story.
Related reading: marketing pulse guides. Start from the guide on detecting spikes if pins are new.
Why email deserves its own pin shape
Email is push: you choose the minute it leaves. Traffic should rise within hours on tagged links, then decay over days as stragglers open the inbox on mobile during the commute.
Unlike always-on SEO, email humps have a known t0. That lets you pin with intent:
- Traffic pin: capture click behavior (often day 0 through day 2).
- Revenue pin: often day 0 through day 7 or day 10 for SaaS trials and courses.
Using one 7-day pin for both is usually fine for founder review; split only when you argue about lag with a co-founder.
Default send-week pin (7 days)
For a Thursday send:
| Day | Pin includes? | Why |
|---|---|---|
| Wed (send−1) | Optional | Catches early leaks, test clicks, timezone bleed |
| Thu (send) | Yes | Primary click day |
| Fri–Sun | Yes | Weekend opens, mobile catch-up |
| Mon–Wed (+3 to +6) | Yes | B2B buyers who “will read it Monday” |
Label: 2026-02-newsletter-07 matching utm_campaign.
Baseline pin: the 7 days immediately before, with no other major send if possible. If you mail weekly, compare issue 07 to issue 06 pins, not to a quiet month from August.
When to start the pin on send day only
Skip send−1 when:
- You never send tests to production links.
- Your provider schedules strictly at one timestamp.
- You are measuring this issue only and Wednesday was a product launch (launch pins overlap).
Starting on send day makes the hump steeper in the chart, good for talks, bad if you need to explain Wednesday test traffic. Pick one rule per publication and keep it.
Revenue lag inside the pin
Digital products with instant checkout often show sales clustered in hour 1–6 after send. SaaS with trial or demo booking shows revenue days 3–7.
Inside the 7-day pin, compare:
- Visitors with
utm_medium=email(or your dictionary value). - Webhook revenue total in the same dates.
- Visits per sale vs baseline pin.
If visitors up 60% and revenue flat, the issue drove curiosity, subject line worked, offer or landing did not. If revenue up without visitor spike, check sales without same-day pageview, direct return buyers are common on small lists.
UTMs and pins must agree
Broken newsletter UTMs after redirects make the pin hump real while attribution says (direct). The pin still proves the send moved traffic; fix tags before comparing channel RPV.
Campaign slug in the pin label should match utm_campaign on the primary CTA. Secondary links (utm_content=footer-ps) roll up under the same campaign inside the pin window.
Multiple CTAs in one issue
One send, three links:
- Pin once for the whole issue.
- Use
utm_contentto compare button vs inline inside the pin. - Do not create three pins for the same send unless you sent three separate campaigns (rare).
Weekly vs biweekly cadence
Weekly mail means rolling pins touch. Overlap is OK if you compare issue to issue:
- Pin
newsletter-06vsnewsletter-07with equal 7-day length. - Note in the label if issue 07 had a product launch cross-promo, otherwise you attribute launch traffic to email.
Biweekly sends get cleaner baselines between humps. Use 10-day pins if your decay tail is long.
Timezone and “which day is send day”
Beehiiv, ConvertKit, and Buttondown schedule in account timezone. Analytics daily buckets often use UTC or site timezone in settings.
A 9 a.m. Eastern send can split:
- Half the clicks in UTC “Thursday”
- Half in UTC “Friday”
For daily charts, expect a two-day plateau instead of one needle peak. That is not failure, it is bucket boundaries. Hourly pulse (when available) clarifies; otherwise extend pin one day and stop overfitting.
Social posts about the same issue share timing pain, see Twitter post time vs hump lag.
Segments beyond the pin
Inside the send pin, slice if you have data:
- New vs returning visitors (session-based, not perfect identity).
- Landing path, did you link to homepage or
/pricing? - Mobile vs desktop mail clients (rough proxy via user-agent).
One-person teams skip slices until the pin vs baseline story is clear.
Apple Mail Privacy and opens
Low open rates do not invalidate click pins. MPP hides opens; clicks still hit your site. Do not shorten the pin because opens looked bad in the ESP.
Re-send and “bonus email”
If you re-send to unopens 48 hours later, either:
- Extend the same pin through the re-send decay, label
newsletter-07+resend, or - Create a second pin
newsletter-07-resendand compare to a quiet week.
Merging re-send into a unrelated baseline pin creates fake lift.
Cross-post: web archive of the issue
Publishing the newsletter as a blog post adds untagged traffic inside the pin. Tag archive links with utm_medium=web-archive or accept blended humps.
Pairing with Stripe and Gumroad webhooks
Marketing pulse overlays webhook revenue on visitor dates. For email:
- Confirm webhook fires on production sales.
- Pin send week on the chart.
- Read revenue line for plateau after click day.
Stripe checkout attribution adds landing-page cuts; pins still anchor when the initiative ran.
Worked example
List: 4,200 subscribers, 38% click rate on main CTA (high, B2B tool list).
Baseline pin (7d): 890 visitors, $420 revenue, RPV ~$0.47.
Send pin (7d): 1,340 visitors (+51%), $680 revenue (+62%), RPV ~$0.51.
Interpretation: Email efficient; repeat angle next issue. If visitors +51% but revenue +10%, rewrite offer block not subject line.
Failure modes
Pin ends Sunday; Monday purchases ignored. Extend to 10 days for high-ticket or invoice billing.
Two sends in one pin. Split issues; weekly cadence needs weekly labels.
Attribution broken week pinned as success. Mark pin note utm-broken; see UTM guide.
Compare to Product Hunt week. PH is a different beast, use PH baseline comparison, not email baseline.
Integration with RPV guides
Email often wins RPV for micro-SaaS. Pins prove which send moved RPV, not just “email is good.”
Where KiboData fits (no oversell)
KiboData stores first-touch UTMs, draws marketing pulse with optional webhook revenue, and lets you save pinned date ranges with labels on the site dashboard. It is not an ESP, it does not send mail or track opens. It does not fix broken redirect UTMs; you still test links monthly.
Badge on free tier; lifetime removes badge. If you only need send-week pins on a traffic line, that is enough; revenue overlay needs a connected webhook.
Checklist before closing the send-week review
- Pin length covers click + purchase lag for your product type
- Baseline pin same length, noted if overlapping sends
- Label matches
utm_campaignon primary CTA - UTMs tested from mobile mail this month
- One-sentence verdict: visitors vs revenue vs baseline
- Action item logged (subject, CTA, offer, or list hygiene)
Hub links
Main guide: spikes without screenshots · Post time vs lag · Marketing pulse topic
Email sends are repeatable experiments. Pin the week, compare to the last pin or baseline, and ship the next issue with memory intact.