Pinterest says 12,000 impressions. Google says 41 clicks
The mid-morning dashboard check has become ritual: coffee cooling beside the trackpad, three browser tabs open, each platform reporting a different version of yesterday. Pinterest claims reach you can’t reconcile, GA4 shows traffic you can’t trace back, and somewhere between the two sits the truth you’re actually being paid to find.
Pinterest’s analytics dashboard inflates reach and hides where your clicks actually go
The platform counts impressions generously and clicks conservatively, leaving a gap most operators never reconcile.
Pinterest’s native analytics will tell you an image earned 8,400 impressions and 220 outbound clicks. Google Analytics will show 91 sessions from Pinterest that same day. The gap isn’t sampling error or a tracking delay—it’s definitional. Pinterest counts an impression any time your pin enters a feed, even if the user scrolls past in half a second. It counts a click only when someone taps through to the pin’s detail view, not when they click your outbound link. That second click—the one that actually sends traffic to your site—lives in a different metric entirely, and it’s often buried or missing.
The problem compounds when you’re trying to calculate cost per acquisition from Pinterest Ads or justify organic pinning time against other channels. If you’re using Pinterest’s “outbound clicks” to estimate traffic value, you’re working from a number that’s systematically higher than what your site will ever see. Meanwhile, GA4’s Pinterest referral count includes only users who successfully loaded your page with intact UTM parameters and accepted cookies—a smaller set than even Pinterest’s most conservative click measure. The only way to reconcile the two is to understand what each platform actually counts, where the breakage happens, and which number answers the question you’re trying to solve.
Most operators never dig past the dashboard’s top-line metrics. They see “12,000 impressions” and assume visibility, or “340 clicks” and assume traffic. Neither assumption holds under scrutiny, and the gap costs you either wasted ad spend or abandoned channels that actually work. The breakdown walks through every metric Pinterest surfaces, maps it to the GA4 equivalent, and shows you how to reconcile the two when the numbers refuse to align.
TOOL COMPARISON
ConvertKit versus MailerLite when your list is still under 5,000
Most small operators pick an ESP based on a feature list they won’t use for eighteen months. ConvertKit offers deeper automation and visual workflows; MailerLite costs half as much and ships a landing-page builder that doesn’t require a separate tool. The real decision hinges on whether you’ll grow into segmentation complexity or stay in broadcast mode for the next year. Pricing curves differently after 5,000 subscribers, and migration costs more than most operators budget for. If you’re choosing today, the comparison matters less for features than for where your list will be in twelve months and whether your workflow actually needs the automation ConvertKit sells.
TACTIC
Stripe payment links can expire—and sometimes that boosts conversions
Stripe lets you set an expiration date on any payment link: 30 minutes, 24 hours, or a custom window. Most operators never touch the setting, which means links stay live forever and early-bird pricing becomes permanent by accident. But expiration does two things well: it adds urgency to limited offers without requiring a countdown timer plugin, and it prevents billing confusion when a customer finds an old link with outdated pricing. The trade-off is operational—you need to track which links are live and replace expired ones quickly if a prospect asks. The decision comes down to whether your offer benefits from a hard deadline or whether evergreen links reduce more friction than urgency creates.
INFRASTRUCTURE
WordPress cron doesn’t work like server cron—and that’s why your site slows down
WordPress cron triggers scheduled tasks every time a visitor loads a page, not on a fixed clock. That means low-traffic sites delay critical jobs for hours, and high-traffic sites run the same cleanup task dozens of times in parallel. Scheduled post publishing, backup plugins, and transactional email queues all depend on wp-cron by default, which makes the system both unreliable and a performance liability. The fix is to disable wp-cron entirely and hand scheduling over to your server’s real cron daemon—but that requires SSH access and a one-line addition to your hosting control panel. Most managed WordPress hosts either handle this for you or make it impossible to change, which means the decision starts with knowing what your host actually allows.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.