<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TrackStack</title>
    <description>The latest articles on DEV Community by TrackStack (@trackstack).</description>
    <link>https://dev.to/trackstack</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3869261%2Fbb568a90-1a2c-4171-a96d-cde864e05263.png</url>
      <title>DEV Community: TrackStack</title>
      <link>https://dev.to/trackstack</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/trackstack"/>
    <language>en</language>
    <item>
      <title>How to Unify Google Ads, Meta and CRM Data</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Sun, 22 Nov 2026 12:58:48 +0000</pubDate>
      <link>https://dev.to/trackstack/how-to-unify-google-ads-meta-and-crm-data-1635</link>
      <guid>https://dev.to/trackstack/how-to-unify-google-ads-meta-and-crm-data-1635</guid>
      <description>&lt;p&gt;Google Ads says it drove 220 conversions, Meta claims 180, and your CRM shows 260 new customers in total. Each report is internally consistent, yet together they make budget decisions a guessing game. This guide is for marketers, founders and analysts running paid campaigns with a CRM behind them, and it shows how to connect the three data sources into one trustworthy report. You will learn which identifiers act as join keys, how to capture and store them, how to send CRM outcomes back to both ad platforms, which tooling fits which budget, and how to calculate blended CAC and ROAS without double-counting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick Answer
&lt;/h2&gt;

&lt;p&gt;To unify Google Ads, Meta and CRM data, capture click IDs (GCLID, fbclid) and UTMs on every lead form, store them on the CRM contact, then upload CRM outcomes back to each platform and export daily ad spend into one table. Join everything on the CRM record, and judge performance by CRM revenue.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the three reports never agree
&lt;/h2&gt;

&lt;p&gt;Each platform grades its own homework. Google Ads credits a conversion to the last Google click it can see. Meta credits the same person to its own ad, often through a different attribution window. The CRM knows who actually paid but usually has no idea which ad brought them in. Add the fact that a lead may click both ads before converting, and the same sale appears in two dashboards at once.&lt;/p&gt;

&lt;p&gt;The gap grew in 2026 as privacy rules and platform changes reduced visibility. Meta, for example, removed some view-through windows from its reporting in January 2026, and browsers keep limiting cookies. The &lt;a href="https://trackstack.tech/en/ga4-attribution-models-reports-2026/" rel="noopener noreferrer"&gt;GA4 attribution guide&lt;/a&gt; covers how Google's analytics layer handles this, but GA4 still cannot see what happens inside your sales pipeline.&lt;/p&gt;

&lt;p&gt;The fix is not another dashboard. It is a shared identifier that travels from the ad click to the CRM record and back, so that every conversion is counted once, against the revenue it really produced.&lt;/p&gt;

&lt;h2&gt;
  
  
  The join keys that make unification possible
&lt;/h2&gt;

&lt;p&gt;Two systems can only be merged when they share a value. In paid media, the useful values are click identifiers, anonymous browser identifiers, and hashed personal data. Think of them as a layered fallback: use the most precise key available, then the next.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Key&lt;/th&gt;
&lt;th&gt;Where it comes from&lt;/th&gt;
&lt;th&gt;Best used for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GCLID&lt;/td&gt;
&lt;td&gt;Google Ads auto-tagging (URL parameter)&lt;/td&gt;
&lt;td&gt;Offline conversion import to Google Ads&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GBRAID / WBRAID&lt;/td&gt;
&lt;td&gt;Google Ads on iOS app-to-web and web-to-app journeys&lt;/td&gt;
&lt;td&gt;Import for privacy-restricted traffic&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;fbclid / fbc&lt;/td&gt;
&lt;td&gt;Meta ad click; fbc is the cookie built from fbclid&lt;/td&gt;
&lt;td&gt;Conversions API matching&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;fbp&lt;/td&gt;
&lt;td&gt;Meta browser cookie&lt;/td&gt;
&lt;td&gt;Fallback matching for Meta&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hashed email / phone&lt;/td&gt;
&lt;td&gt;Form field, hashed with SHA-256&lt;/td&gt;
&lt;td&gt;Enhanced conversions, Meta matching&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;UTM parameters&lt;/td&gt;
&lt;td&gt;Your own link tagging&lt;/td&gt;
&lt;td&gt;Cross-channel grouping in CRM and BI&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two details cause most silent failures. GCLID values are case-sensitive, so lowercasing them in a form tool or spreadsheet breaks every later match. And auto-tagging must be switched on in Google Ads, otherwise no GCLID is appended at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Capture click IDs and UTMs at the form
&lt;/h2&gt;

&lt;p&gt;Everything downstream depends on this step. When a visitor lands from an ad, the URL carries parameters such as gclid, fbclid and your UTMs. A short script, or your tag manager, should read them on landing, store them in first-party storage, and copy them into hidden fields on every form the visitor submits.&lt;/p&gt;

&lt;p&gt;Without that, the lead arrives in the CRM with a name and an email but no origin. A walkthrough on &lt;a href="https://trackstack.tech/en/track-form-submissions-ga4-no-code/" rel="noopener noreferrer"&gt;tracking form submissions without code&lt;/a&gt; explains the form-event side, and the &lt;a href="https://trackstack.tech/en/ga4-custom-dimensions-setup-2026/" rel="noopener noreferrer"&gt;custom dimensions guide&lt;/a&gt; shows how to carry the same parameters into GA4 reports.&lt;/p&gt;

&lt;p&gt;A practical checklist for the form layer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add hidden fields for gclid, gbraid, wbraid, fbclid, fbc, fbp and the five UTM parameters.&lt;/li&gt;
&lt;li&gt;Persist values for at least the length of the sales cycle, not just the session, so a returning visitor keeps the original source.&lt;/li&gt;
&lt;li&gt;Keep first-touch and last-touch UTMs in separate fields instead of overwriting one with the other.&lt;/li&gt;
&lt;li&gt;Test with a real ad click in a private window, then open the CRM record and confirm every value arrived unchanged.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A common failure in setups like this is a landing page that works perfectly, while a form embedded from another domain never receives the parameters. Check that path explicitly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Store everything on the CRM contact
&lt;/h2&gt;

&lt;p&gt;Create dedicated custom properties for each identifier, plus fields for lead source, campaign, first-touch date and the lifecycle stage timestamps. Resist the temptation to reuse a generic notes field, because later automations need clean, filterable properties.&lt;/p&gt;

&lt;p&gt;Decide early what a conversion means in your business. A form fill is cheap. A qualified lead, a booked demo or a paid invoice is what the ad platforms should optimize for. Record a timestamp for each stage, since both Google and Meta ask for the time of the event when you upload it. Matching on hashed email or phone as a second key is worth planning now, because a share of leads will arrive without any click ID.&lt;/p&gt;

&lt;p&gt;Duplicates deserve attention too. One person often submits several forms, books a call, and later buys under a colleague's address. Choose a normalized email as the primary identity, merge duplicate contacts on a schedule, and keep the original click IDs from the first record when you merge. Otherwise the revenue lands on a contact that carries no source, and the channel that started the journey loses credit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Send CRM outcomes back to the platforms
&lt;/h2&gt;

&lt;p&gt;This is the step that turns reporting into optimization. Smart bidding and Meta's delivery system learn from the conversions you report. If they only see form fills, they will find more people who fill forms, not more people who buy.&lt;/p&gt;

&lt;p&gt;For Google Ads, upload offline conversions using the stored GCLID, or GBRAID and WBRAID where relevant. Where click IDs are missing, enhanced conversions for leads let you supply hashed email or phone instead. Google is also steering developers toward its Data Manager API for these uploads, so check which route your CRM connector uses. Conversions must be imported within the platform's allowed window after the click, so schedule the upload daily rather than monthly. The &lt;a href="https://trackstack.tech/en/google-ads-conversion-tracking-setup-2026/" rel="noopener noreferrer"&gt;Google Ads conversion tracking setup&lt;/a&gt; covers the conversion actions you need before importing.&lt;/p&gt;

&lt;p&gt;For Meta, use the Conversions API with CRM events. Send the event name, event time, fbc and fbp where you have them, and hashed email and phone. Include an event ID so Meta can deduplicate against any pixel event for the same action. Meta's Events Manager shows an Event Match Quality score, which is the quickest way to see whether your identifiers are doing their job. Low scores usually mean too few identifiers per event.&lt;/p&gt;

&lt;p&gt;After the first upload, verify it. Google Ads reports how many imported rows matched a click, and Meta's Events Manager lists received events with their diagnostics. A match rate far below the share of leads that carried a click ID points to a formatting or timing problem. Fix it before scaling the process, because bidding models learn from whatever you send, including mistakes.&lt;/p&gt;

&lt;p&gt;Many CRMs offer native integrations for one or both platforms. Use them if they pass the parameters you need. If not, an automation tool or a small script can read qualified leads daily and post them to each API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Pull ad spend into one place
&lt;/h2&gt;

&lt;p&gt;Click IDs connect leads to ads, but spend and impressions must still come from the platforms. The practical question is how to move those numbers into a single table, and the answer depends on volume and technical skill.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Cost model&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Limits&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Manual CSV or Sheets add-on&lt;/td&gt;
&lt;td&gt;Free to low&lt;/td&gt;
&lt;td&gt;One or two channels, weekly review&lt;/td&gt;
&lt;td&gt;Manual effort, error-prone&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Connector tools (Supermetrics, Coupler.io, Windsor.ai)&lt;/td&gt;
&lt;td&gt;Subscription by sources and usage&lt;/td&gt;
&lt;td&gt;Teams that report in Sheets or Looker Studio&lt;/td&gt;
&lt;td&gt;Cost grows with sources&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Automation platforms (Zapier, Make)&lt;/td&gt;
&lt;td&gt;Per-task or per-operation&lt;/td&gt;
&lt;td&gt;Event-level CRM syncing&lt;/td&gt;
&lt;td&gt;Not built for bulk spend history&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Warehouse (BigQuery)&lt;/td&gt;
&lt;td&gt;Storage and query usage&lt;/td&gt;
&lt;td&gt;Analysts who want full control&lt;/td&gt;
&lt;td&gt;Needs SQL; Meta has no native transfer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Marketing analytics platforms&lt;/td&gt;
&lt;td&gt;Custom or tiered pricing&lt;/td&gt;
&lt;td&gt;Larger budgets, many channels&lt;/td&gt;
&lt;td&gt;Higher cost, setup time&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For most small and mid-sized teams the sweet spot is a connector feeding a spreadsheet or BigQuery. BigQuery's Data Transfer Service has a Google Ads connector at no charge for the transfer itself, though it runs daily and you still pay for storage and queries. Meta data needs a connector or a custom pipeline. Pricing for these tools changes often, so check current plans before committing.&lt;/p&gt;

&lt;p&gt;If you only need a lightweight start, the guide to &lt;a href="https://trackstack.tech/en/connect-google-sheets-crm-2026/" rel="noopener noreferrer"&gt;connecting Google Sheets to your CRM&lt;/a&gt; is enough for a first version, and the &lt;a href="https://trackstack.tech/en/best-marketing-attribution-tools-2026/" rel="noopener noreferrer"&gt;attribution tools comparison&lt;/a&gt; helps when you outgrow it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Build the unified report
&lt;/h2&gt;

&lt;p&gt;Structure the final table with one row per CRM lead or deal, carrying source, campaign, click IDs, stage timestamps and revenue. Aggregate spend daily by platform and campaign. Then join the two on date, source and campaign using the UTMs you standardized in step 1.&lt;/p&gt;

&lt;p&gt;Three metrics belong at the top of the report. Blended CAC is total marketing spend divided by all new customers, which no platform can distort. Channel CAC divides each channel's spend by the customers the CRM attributes to it. ROAS compares CRM revenue, not platform-reported value, to spend. Pair them with the model you chose in the &lt;a href="https://trackstack.tech/en/marketing-attribution-models-explained-2026/" rel="noopener noreferrer"&gt;attribution models explainer&lt;/a&gt;, and state the model on the report so nobody compares unlike numbers.&lt;/p&gt;

&lt;p&gt;Add lifetime value once you have enough history. A channel with a higher CAC can still win if its customers renew or buy again, so compare CAC with revenue per customer over six or twelve months. Review the report on a fixed rhythm, weekly for budgets and monthly for strategy, and keep a short changelog of tracking changes so a sudden jump can be traced to its cause.&lt;/p&gt;

&lt;p&gt;Here is an illustrative example with assumed numbers: $6,000 on Google Ads, $4,000 on Meta, and $120 average first order.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Channel&lt;/th&gt;
&lt;th&gt;Platform-reported conversions&lt;/th&gt;
&lt;th&gt;CRM-matched customers&lt;/th&gt;
&lt;th&gt;Platform CAC&lt;/th&gt;
&lt;th&gt;CRM CAC&lt;/th&gt;
&lt;th&gt;CRM ROAS&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Google Ads&lt;/td&gt;
&lt;td&gt;220&lt;/td&gt;
&lt;td&gt;150&lt;/td&gt;
&lt;td&gt;$27.27&lt;/td&gt;
&lt;td&gt;$40.00&lt;/td&gt;
&lt;td&gt;3.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Meta&lt;/td&gt;
&lt;td&gt;180&lt;/td&gt;
&lt;td&gt;70&lt;/td&gt;
&lt;td&gt;$22.22&lt;/td&gt;
&lt;td&gt;$57.14&lt;/td&gt;
&lt;td&gt;2.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Unmatched / organic&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;td&gt;40&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total&lt;/td&gt;
&lt;td&gt;400&lt;/td&gt;
&lt;td&gt;260&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;td&gt;$38.46 blended&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In the platforms, Meta looks cheaper. In the CRM, it is the more expensive channel, and 180 platform-reported conversions never matched a CRM customer, because of overlap between the two platforms or leads that never bought. Without the join, the budget would likely have shifted in the wrong direction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes to avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lowercasing or truncating click IDs somewhere between the form and the CRM.&lt;/li&gt;
&lt;li&gt;Importing conversions weeks late, after the platform's window has closed.&lt;/li&gt;
&lt;li&gt;Uploading every lead as a conversion, which trains bidding on low-quality signals.&lt;/li&gt;
&lt;li&gt;Sending hashed data without normalizing it first: trim whitespace and lowercase emails before hashing.&lt;/li&gt;
&lt;li&gt;Skipping consent. Only send personal data you have a legal basis to share, and respect consent signals under GDPR and similar rules.&lt;/li&gt;
&lt;li&gt;Treating platform-reported ROAS and CRM ROAS as interchangeable.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Fix these in order. A clean capture layer solves more problems than any reporting tool can.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I unify the data without a developer?
&lt;/h3&gt;

&lt;p&gt;Often yes. Hidden form fields, a tag manager, native CRM integrations and a connector tool cover most small setups. You need a developer mainly for custom form embeds, server-side events or a warehouse pipeline.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if some leads have no click ID?
&lt;/h3&gt;

&lt;p&gt;Use hashed email or phone as the fallback key. Both Google's enhanced conversions for leads and Meta's Conversions API can match on them, though match rates are lower than with click IDs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need BigQuery?
&lt;/h3&gt;

&lt;p&gt;No. A connector feeding Sheets or Looker Studio is enough while volume is modest. BigQuery becomes useful when you have large datasets, need SQL joins, or want to keep long-term history.&lt;/p&gt;

&lt;h3&gt;
  
  
  How often should CRM conversions be uploaded?
&lt;/h3&gt;

&lt;p&gt;Daily is a sound default. Faster feedback helps bidding algorithms learn, and it keeps you inside each platform's allowed upload window after the click.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why do platform conversions exceed CRM customers?
&lt;/h3&gt;

&lt;p&gt;Platforms count conversions, not unique customers, and each takes credit under its own rules. One buyer who clicked both ads can appear in both reports, and some conversions never become paying customers.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is this compliant with privacy rules?
&lt;/h3&gt;

&lt;p&gt;It can be, if you collect consent where required, hash personal data before sending it, and share only what the platforms need. Confirm the details with a qualified legal advisor for your region.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Unification is mostly plumbing: capture identifiers once, store them on the CRM record, send outcomes back, and combine spend in one table. Start with step 1 this week, because every later improvement depends on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Google Ads, Meta and the CRM disagree because each platform credits conversions by its own rules, while the CRM knows revenue but not the source.&lt;/li&gt;
&lt;li&gt;The fix is a shared identifier: capture GCLID, fbclid and UTMs on every form, store them on the CRM contact, and use hashed email or phone as the fallback key.&lt;/li&gt;
&lt;li&gt;Send qualified-lead and paid outcomes back to Google Ads (offline conversions) and Meta (Conversions API), ideally daily, then verify match rates.&lt;/li&gt;
&lt;li&gt;Pull daily spend into one table with a connector, spreadsheet or BigQuery, join on the CRM record, and judge channels by blended CAC and CRM-based ROAS, not platform-reported numbers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://trackstack.tech/en/unify-google-ads-meta-crm-data-2026/" rel="noopener noreferrer"&gt;Trackstack Editorial&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>crm</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Best Marketing Attribution Tools 2026: 6 Compared</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Sat, 07 Nov 2026 14:17:31 +0000</pubDate>
      <link>https://dev.to/trackstack/best-marketing-attribution-tools-2026-6-compared-2om5</link>
      <guid>https://dev.to/trackstack/best-marketing-attribution-tools-2026-6-compared-2om5</guid>
      <description>&lt;p&gt;Picking a marketing attribution tool is harder than it looks, because the category mixes products built for very different businesses: a free analytics platform, a CRM add-on, ecommerce profit dashboards and B2B journey trackers all call themselves attribution software. This guide is for marketers, founders and growth teams who need to shortlist a tool without sitting through six sales demos first. It compares six real options, GA4, HubSpot, Triple Whale, Northbeam, Ruler Analytics and Dreamdata, on pricing, channel coverage, attribution method and fit, names the honest downsides of each, and shows what the first year actually costs. Prices were checked in October 2026 and, where a vendor quotes privately, are marked as such.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the Tools Were Compared
&lt;/h2&gt;

&lt;p&gt;Five questions decided the shortlist. What does it cost, and is the price public? Which channels does it actually see? How does it assign credit, and can that be inspected? Can it join sales outcomes from a CRM? And which kind of business is it built for? Pricing details come from vendor pages and third-party pricing guides in October 2026; several of those guides are published by competing vendors, so figures are treated as indicative and should be confirmed before signing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Marketing Attribution Tools Compared
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Starting price (reported, October 2026)&lt;/th&gt;
&lt;th&gt;What it sees&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Main catch&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GA4&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;Tagged site traffic, Google Ads cost; other cost data needs importing&lt;/td&gt;
&lt;td&gt;Anyone starting out&lt;/td&gt;
&lt;td&gt;Only data-driven and last-click models; digital touchpoints only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HubSpot&lt;/td&gt;
&lt;td&gt;Enterprise from $3,600/month plus a $7,000 one-time onboarding fee for revenue attribution&lt;/td&gt;
&lt;td&gt;Website, forms, email, calls and meetings tied to known contacts&lt;/td&gt;
&lt;td&gt;Teams whose CRM already lives in HubSpot&lt;/td&gt;
&lt;td&gt;Enterprise-only; depends on clean contact and deal records&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Triple Whale&lt;/td&gt;
&lt;td&gt;Free plan; paid plans quoted by annual GMV on 12-month terms&lt;/td&gt;
&lt;td&gt;Shopify and major ad platforms&lt;/td&gt;
&lt;td&gt;Ecommerce and DTC brands&lt;/td&gt;
&lt;td&gt;No public paid prices; weak fit for B2B&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Northbeam&lt;/td&gt;
&lt;td&gt;From $1,500/month (Starter); Professional from $3,500/month&lt;/td&gt;
&lt;td&gt;Ad platforms and Shopify&lt;/td&gt;
&lt;td&gt;DTC brands with real ad spend&lt;/td&gt;
&lt;td&gt;High floor price, no free trial, black-box model&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ruler Analytics&lt;/td&gt;
&lt;td&gt;From $400/month for up to 10,000 visits&lt;/td&gt;
&lt;td&gt;Forms, calls, chat and offline sales linked to CRM revenue&lt;/td&gt;
&lt;td&gt;Lead generation and call-driven businesses&lt;/td&gt;
&lt;td&gt;Tiers scale with traffic; no self-serve trial advertised&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dreamdata&lt;/td&gt;
&lt;td&gt;Free plan; paid tier by quote&lt;/td&gt;
&lt;td&gt;B2B account journeys across CRM and ads&lt;/td&gt;
&lt;td&gt;B2B SaaS with long deals&lt;/td&gt;
&lt;td&gt;Paid pricing unpublished; weaker for calls and offline&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What Separates These Tools Technically
&lt;/h2&gt;

&lt;p&gt;Under the marketing language, attribution tools differ in three technical ways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Collection:&lt;/strong&gt; a tracking script or pixel on the site, server-side delivery to ad platforms, or connectors that pull data from ad accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Joining:&lt;/strong&gt; whether sales outcomes arrive from a CRM, a store backend or a call-tracking system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Crediting:&lt;/strong&gt; rule-based models that can be inspected, or machine-learning credit that cannot.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A product strong in one area is usually thin in another, which is why a shortlist should start from the weakest link in the current setup: missing calls, missing CRM revenue or missing ad-platform spend. Naming that gap first usually cuts six candidates to two.&lt;/p&gt;

&lt;h2&gt;
  
  
  GA4: The Free Baseline
&lt;/h2&gt;

&lt;p&gt;GA4 costs nothing, runs on tags most sites already have and offers two usable models in reporting, data-driven and last click. For a business spending a few thousand dollars a month on ads, that is enough to answer the first questions. The limits are structural: it only sees tagged visits from consenting users, ignores impressions and offline conversions, and holds cost data only for Google. A deeper walkthrough of its models and reports is in the guide to &lt;a href="https://trackstack.tech/en/ga4-attribution-models-reports-2026/" rel="noopener noreferrer"&gt;GA4 attribution&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  HubSpot Attribution: Strong Only Inside HubSpot
&lt;/h2&gt;

&lt;p&gt;HubSpot's deal revenue attribution is the most CRM-native option here. It credits closed-won deals to the interactions that preceded them and supports first touch, last touch, linear, time decay and an empirical model. The catch is the price of entry: per third-party guides it requires Marketing Hub Enterprise, reported at $3,600 a month plus a $7,000 onboarding fee.&lt;/p&gt;

&lt;p&gt;It also needs discipline. A deal must be closed won, carry an amount and dates, and have contacts and sales activities associated with it, otherwise it drops out of the report. Anonymous visitors who never become contacts are invisible, and high-volume interactions such as page views can be sampled. It suits mid-market teams that already run sales and marketing in HubSpot; it is poor value for a team that only wants attribution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Triple Whale: Ecommerce Dashboards With a Free Tier
&lt;/h2&gt;

&lt;p&gt;Triple Whale targets Shopify brands. It offers a free plan with its tracking pixel and first- and last-click attribution, reportedly with multi-touch attribution from the Foundation tier and modeling features such as incrementality on Enterprise. Paid plans are now quoted by annual GMV, on 12-month terms, and a store moving into a higher revenue band can see its price jump, so budgeting needs a quote rather than a pricing page.&lt;/p&gt;

&lt;p&gt;Strengths are creative analysis, post-purchase survey data and broad store and ad integrations. Weaknesses are the lack of public paid prices and a product shaped around ecommerce: lead-generation and B2B teams with long sales cycles will find little to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Northbeam: Independent Attribution at a Higher Price
&lt;/h2&gt;

&lt;p&gt;Northbeam sells to DTC brands that want attribution independent of what the ad platforms report. It applies machine-learning fractional credit so attributed conversions reconcile with actual sales, and as of April 2026 bundles marketing mix modeling across tiers. Reported pricing starts at $1,500 a month for Starter and $3,500 for Professional, scaling with media spend, with no free trial.&lt;/p&gt;

&lt;p&gt;The honest trade-offs: Starter refreshes data four times a day, which may be slow for aggressive daily optimization, the model cannot be inspected, and its incrementality testing is reportedly limited to Meta in the US. It fits brands spending enough on ads that a few percent of waste outweighs the subscription; it is oversized for a small store.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ruler Analytics: For Calls, Forms and Offline Sales
&lt;/h2&gt;

&lt;p&gt;Ruler Analytics is the tool here that cares about phone calls. It tracks forms, dynamic call numbers, chat and offline conversions, then ties them to CRM revenue in Salesforce, HubSpot or Pipedrive. It offers first click, last click, time decay, linear and position-based models, with data-driven attribution on Medium and above, and marketing mix modeling on the top tier.&lt;/p&gt;

&lt;p&gt;Pricing follows monthly website visits: from $400 for up to 10,000 visits, $668 for 50,000, $1,326 for 100,000 and $2,000 above that, with roughly 10% off for annual billing. That makes it a natural match for lead-generation businesses, agencies and professional services. The downsides are the $400 entry point for very small sites, large jumps between tiers and no advertised self-serve trial. It is not built for product analytics or SaaS activation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dreamdata: B2B Journeys Across Accounts
&lt;/h2&gt;

&lt;p&gt;Dreamdata is built for B2B SaaS companies where several people at one account touch many channels over months. It offers a free plan, reportedly limited to a short history and a handful of seats, while paid tiers are quoted by sales. Its strength is account-level journeys rather than single-click credit.&lt;/p&gt;

&lt;p&gt;Its limits mirror its focus. Paid pricing is not public, phone and offline attribution are reportedly weaker than in call-oriented tools, and ecommerce brands will find no reason to use it. A B2B team with a CRM and a long sales cycle is the right buyer; a store with a Shopify checkout is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the First Year Actually Costs
&lt;/h2&gt;

&lt;p&gt;Every vendor charges on a different meter: GA4 is free, Ruler counts visits, Northbeam follows ad spend, Triple Whale follows GMV and HubSpot sells a platform tier. That decides which tool gets expensive first as a business grows. The table multiplies the published floor prices by twelve and adds known one-off fees. It is a lower bound, not a quote.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool and tier&lt;/th&gt;
&lt;th&gt;Monthly floor&lt;/th&gt;
&lt;th&gt;First-year floor&lt;/th&gt;
&lt;th&gt;Note&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GA4&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;Free, but staff time for setup and analysis&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ruler Analytics, Small&lt;/td&gt;
&lt;td&gt;$400&lt;/td&gt;
&lt;td&gt;$4,800&lt;/td&gt;
&lt;td&gt;About $4,320 on annual billing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Northbeam, Starter&lt;/td&gt;
&lt;td&gt;$1,500&lt;/td&gt;
&lt;td&gt;$18,000&lt;/td&gt;
&lt;td&gt;Professional from $3,500 is $42,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HubSpot, Marketing Hub Enterprise&lt;/td&gt;
&lt;td&gt;$3,600&lt;/td&gt;
&lt;td&gt;$50,200&lt;/td&gt;
&lt;td&gt;Includes the $7,000 onboarding fee&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Triple Whale and Dreamdata&lt;/td&gt;
&lt;td&gt;Free plan, then quote&lt;/td&gt;
&lt;td&gt;Quote required&lt;/td&gt;
&lt;td&gt;Start free, price paid tiers before committing&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The spread between the cheapest and most expensive paid tool is more than tenfold, and attribution is only part of what the expensive option does.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fourth Option: Cross-Channel Analytics Platforms
&lt;/h2&gt;

&lt;p&gt;Between a single-channel dashboard and a full CRM suite sits another category: cross-channel marketing analytics platforms. These connect Google Ads, Meta, TikTok, LinkedIn and a CRM into one dataset, then report ROAS, CAC and customer journeys across all of them. They suit teams whose budget is split across several platforms and whose sales happen outside a Shopify checkout.&lt;/p&gt;

&lt;p&gt;When evaluating any product in this category, four checks matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Does it have native connectors for the channels actually in use, including cost data?&lt;/li&gt;
&lt;li&gt;Can it join CRM outcomes such as qualified leads and closed revenue back to campaigns?&lt;/li&gt;
&lt;li&gt;Can several attribution models be viewed side by side?&lt;/li&gt;
&lt;li&gt;Do support and billing match the region and language of the team?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A tool that does all four can replace parts of the stack above, but only after a trial on real data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Tool Fits Which Business
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Business&lt;/th&gt;
&lt;th&gt;Shortlist&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Small store, under roughly $100K monthly sales&lt;/td&gt;
&lt;td&gt;GA4, Triple Whale free plan&lt;/td&gt;
&lt;td&gt;Cost matters more than depth&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Growing DTC brand with large ad spend&lt;/td&gt;
&lt;td&gt;Northbeam, Triple Whale paid&lt;/td&gt;
&lt;td&gt;Independent credit and creative analysis pay for themselves at scale&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lead generation, agency or services firm&lt;/td&gt;
&lt;td&gt;Ruler Analytics&lt;/td&gt;
&lt;td&gt;Calls, forms and offline sales tied to CRM revenue&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;B2B SaaS with long deals&lt;/td&gt;
&lt;td&gt;Dreamdata, HubSpot if already on it&lt;/td&gt;
&lt;td&gt;Account-level journeys and CRM depth&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Budget across Google, Meta, TikTok, LinkedIn plus a CRM&lt;/td&gt;
&lt;td&gt;A cross-channel analytics platform, GA4 as baseline&lt;/td&gt;
&lt;td&gt;One joined dataset and several models side by side&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A trial of at least one full sales cycle, with GA4 running alongside as a reference, shows whether a paid tool adds information or only a second set of numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions to Ask Before Signing
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What is the price at double today's traffic, spend or GMV, and is the tier locked for the contract term?&lt;/li&gt;
&lt;li&gt;Which models are available, and can the weighting be inspected or exported?&lt;/li&gt;
&lt;li&gt;How are calls, offline sales and CRM revenue connected, and by what integration?&lt;/li&gt;
&lt;li&gt;What happens to tracking under consent refusals and ad blockers, and how is missing data modeled?&lt;/li&gt;
&lt;li&gt;Can the data be exported to a warehouse or spreadsheet if the contract ends?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get Tracking Right Before Buying Anything
&lt;/h2&gt;

&lt;p&gt;No tool repairs missing or duplicated events. Before paying for software, check the foundations: the &lt;a href="https://trackstack.tech/en/google-ads-conversion-tracking-setup-2026/" rel="noopener noreferrer"&gt;Google Ads conversion tracking setup&lt;/a&gt; guide covers the common breakages, the &lt;a href="https://trackstack.tech/en/ga4-ecommerce-events-setup-guide/" rel="noopener noreferrer"&gt;GA4 ecommerce events setup guide&lt;/a&gt; covers revenue events for stores, and the guide to &lt;a href="https://trackstack.tech/en/track-form-submissions-ga4-no-code/" rel="noopener noreferrer"&gt;tracking form submissions in GA4&lt;/a&gt; covers leads. To bring sales results in cheaply, start by &lt;a href="https://trackstack.tech/en/connect-google-sheets-crm-2026/" rel="noopener noreferrer"&gt;connecting Google Sheets to the CRM&lt;/a&gt;. If the goal is understanding behavior after signup instead, compare &lt;a href="https://trackstack.tech/en/mixpanel-vs-amplitude-2026/" rel="noopener noreferrer"&gt;Mixpanel and Amplitude&lt;/a&gt;. And to understand what each model in these tools is doing, read the guide to &lt;a href="https://trackstack.tech/en/marketing-attribution-models-explained-2026/" rel="noopener noreferrer"&gt;marketing attribution models&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is the best marketing attribution tool?
&lt;/h3&gt;

&lt;p&gt;There is no single best tool. GA4 is the free baseline, Triple Whale and Northbeam fit ecommerce, Ruler Analytics fits call- and form-driven lead generation, HubSpot fits teams already on its CRM and Dreamdata fits B2B SaaS. Matching the tool to the type of sale comes before comparing features.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is GA4 enough for marketing attribution?
&lt;/h3&gt;

&lt;p&gt;For small budgets and a mostly Google-based mix, yes. GA4 is free and offers data-driven and last-click models. It stops being enough when spend spreads across Meta, TikTok and LinkedIn, when calls and offline sales matter, or when CRM revenue has to be tied back to campaigns.&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does marketing attribution software cost?
&lt;/h3&gt;

&lt;p&gt;From free (GA4, and free plans at Triple Whale and Dreamdata) to roughly $400 a month for Ruler Analytics, $1,500 for Northbeam Starter and $3,600 for HubSpot Enterprise plus onboarding. Several vendors quote privately, so published floors are lower bounds.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need a paid attribution tool for a small business?
&lt;/h3&gt;

&lt;p&gt;Often not. Clean tracking, GA4 and a simple spreadsheet join with CRM data answer most early questions. A paid tool starts paying for itself when ad spend is large enough that misallocating even a small share costs more than the subscription.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the difference between attribution tools and marketing mix modeling?
&lt;/h3&gt;

&lt;p&gt;Attribution tools assign credit to individual touchpoints in tracked journeys. Marketing mix modeling works from aggregate spend and sales and needs no user-level tracking. Some vendors now bundle both, and each answers a different question.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which attribution tool works best for B2B?
&lt;/h3&gt;

&lt;p&gt;For account-level journeys over long cycles, Dreamdata and HubSpot are built for it, with HubSpot making sense mainly if the CRM already runs there. For call-driven B2B lead generation, Ruler Analytics is the closer match.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GA4 is the free baseline; Triple Whale and Northbeam fit ecommerce, Ruler Analytics fits call- and form-driven lead generation, HubSpot fits teams already on its CRM, and Dreamdata fits B2B SaaS.&lt;/li&gt;
&lt;li&gt;Published floor prices run from $0 to roughly $50,200 in year one, and each vendor charges on a different meter: visits, ad spend, GMV or platform tier.&lt;/li&gt;
&lt;li&gt;Several vendors quote privately, so every price here is a lower bound to confirm before signing.&lt;/li&gt;
&lt;li&gt;Start from the weakest link in the current setup (calls, CRM revenue or ad spend), and trial any paid tool for a full sales cycle with GA4 alongside.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://trackstack.tech/en/best-marketing-attribution-tools-2026/" rel="noopener noreferrer"&gt;Trackstack Editorial&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>sass</category>
      <category>tools</category>
    </item>
    <item>
      <title>GA4 Attribution: Models &amp; Reports Explained (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Fri, 30 Oct 2026 06:46:40 +0000</pubDate>
      <link>https://dev.to/trackstack/ga4-attribution-models-reports-explained-2026-24bm</link>
      <guid>https://dev.to/trackstack/ga4-attribution-models-reports-explained-2026-24bm</guid>
      <description>&lt;p&gt;GA4 attribution decides which channel gets credit when someone clicks an ad, reads a post, opens an email and then buys, and it quietly shapes every report used to move budget. Google has also changed it repeatedly: models were removed in 2023, per-conversion settings arrived in beta in January 2026, and conversion windows became editable in August. This guide is for marketers, founders and growth teams who rely on GA4 and want to know exactly what it offers today. It covers which three models exist, where to change the settings, how lookback windows behave, which report answers which question, how to read Model comparison without fooling yourself, and where GA4 attribution stops being enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Attribution Means Inside GA4
&lt;/h2&gt;

&lt;p&gt;GA4 credits traffic in three different scopes, and mixing them up causes most "the numbers do not match" complaints.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;User-scoped&lt;/strong&gt; dimensions, such as First user source, credit the channel that first brought the person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Session-scoped&lt;/strong&gt; dimensions, such as Session source / medium in the Traffic acquisition report, credit the channel of that single visit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Event-scoped&lt;/strong&gt; credit assigns a key event (GA4's term for a conversion) to a channel using the reporting attribution model.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The model setting mainly affects that third kind: the Advertising workspace and event-scoped source reporting. Changing it will not rewrite what the user-acquisition and traffic-acquisition reports show, which is why one purchase can appear under different channels in different reports without anything being broken.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Three GA4 Attribution Models
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;How credit is assigned&lt;/th&gt;
&lt;th&gt;Good for&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Data-driven (default)&lt;/td&gt;
&lt;td&gt;An algorithm spreads credit across touchpoints, based on data specific to the property and each key event&lt;/td&gt;
&lt;td&gt;Journeys with several channels&lt;/td&gt;
&lt;td&gt;Opaque: the weights are not disclosed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid and organic last click&lt;/td&gt;
&lt;td&gt;100% to the last non-direct click, paid or organic&lt;/td&gt;
&lt;td&gt;A simple, auditable baseline&lt;/td&gt;
&lt;td&gt;Over-credits the final channel, often brand search or email&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google paid channels last click&lt;/td&gt;
&lt;td&gt;100% to the last Google Ads click&lt;/td&gt;
&lt;td&gt;Checking against Google Ads reporting&lt;/td&gt;
&lt;td&gt;Ignores every non-Google channel&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Everything else is gone. Google's own help page states that the first-click, linear, time-decay and position-based models have not been available since November 2023. A rule-based view now has to come from outside GA4: exported path data, a spreadsheet model or a dedicated attribution tool. The Trackstack breakdown of &lt;a href="https://trackstack.tech/en/marketing-attribution-models-explained-2026/" rel="noopener noreferrer"&gt;marketing attribution models&lt;/a&gt; explains what each of those retired models did and when it fit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data-Driven Attribution in GA4: What It Does and Does Not Tell You
&lt;/h2&gt;

&lt;p&gt;GA4 describes data-driven models as specific to each advertiser and each key event, built from the touchpoints that preceded conversions. In practice a purchase and a lead form on the same property can distribute credit differently. The model also reacts to the property's own mix: when a channel appears early in many converting paths, it gains credit that last click would have denied it.&lt;/p&gt;

&lt;p&gt;Two cautions matter in daily use. First, GA4 can reattribute conversions for up to seven days after they occur, so channel numbers for the last week are provisional. Judging yesterday's paid-social result against last week's is a common way to make a wrong call. Second, the algorithm is a black box. It can show that a channel assists, not why, and it only sees tagged visits that reach the site. An ad that was seen but never clicked is invisible to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lookback Windows: Matching the Window to Your Sales Cycle
&lt;/h2&gt;

&lt;p&gt;A lookback window is how far back GA4 searches for touchpoints before a key event. By default, acquisition events use 30 days and other key events use 90 days; at property level the longer choices are typically 30, 60 or 90 days. The right value follows the sales cycle. A $30 impulse product rarely needs 90 days, and a B2B demo request can easily span two months of research.&lt;/p&gt;

&lt;p&gt;Windows became more flexible on August 11, 2026. According to Google's release notes, click-through conversion windows can now be set to any whole number of days from 1 to 90, where earlier they were limited to preset values. Engaged-view conversion windows, previously fixed at three days, can be set from 1 to 30 days. These settings live in the Advertising workspace under conversion management.&lt;/p&gt;

&lt;p&gt;One practical rule: treat every window change as a break in the trend line and write the date down. A shorter window lowers reported conversions for slow channels without any change in real performance, and a report that straddles the change will show a decline or a jump that never happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Per-Key-Event Attribution Settings
&lt;/h2&gt;

&lt;p&gt;Since January 16, 2026, Google has been rolling out beta settings that let the attribution configuration be adjusted independently for every conversion, and since September 29, 2026 the same applies to app conversions. Google flags both as possibly unavailable for some properties, so conversion management in the Advertising workspace is the place to check before planning around them.&lt;/p&gt;

&lt;p&gt;The value is straightforward. A fast checkout purchase and a slow enterprise lead no longer have to share one window and one model. A short window fits the purchase, a long one fits the qualified-lead key event, and the property-wide setting stays as the fallback. The cost is complexity: once settings differ per event, comparing reports across key events needs a note on which setting each one uses.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Sensible Default Configuration
&lt;/h2&gt;

&lt;p&gt;For most small and mid-sized properties, a short list of defaults avoids nearly all the trouble:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keep data-driven as the reporting model, because it is the only option that credits earlier touches.&lt;/li&gt;
&lt;li&gt;Choose a lookback window that covers the typical gap between first visit and purchase, which Conversion paths shows as average days to conversion, rather than a number copied from a blog post.&lt;/li&gt;
&lt;li&gt;Keep paid and organic last click in view as the comparison baseline.&lt;/li&gt;
&lt;li&gt;Keep a simple change log with the date of every attribution, window or key-event edit, so that a jump in a chart can be traced to a setting instead of a campaign.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the property has only a few dozen conversions a month, the models will look alike, and simpler evidence works better, such as comparing periods with a channel on and off.&lt;/p&gt;

&lt;h2&gt;
  
  
  GA4 Attribution Reports: Where to Find What
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Report&lt;/th&gt;
&lt;th&gt;Question it answers&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Advertising snapshot&lt;/td&gt;
&lt;td&gt;How are conversions split across channels at a glance?&lt;/td&gt;
&lt;td&gt;High-level only; no path detail&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;All channels (Performance)&lt;/td&gt;
&lt;td&gt;Which channels get credit for each key event under the reporting model?&lt;/td&gt;
&lt;td&gt;Changes when the model setting changes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Conversion paths&lt;/td&gt;
&lt;td&gt;Which sequences of channels precede conversion, and how many days and touches do they span?&lt;/td&gt;
&lt;td&gt;Only as good as the source and medium tagging&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Model comparison&lt;/td&gt;
&lt;td&gt;Where do two models disagree about a channel?&lt;/td&gt;
&lt;td&gt;Identical results can mean thin data or single-touch journeys&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Conversion attribution analysis (beta)&lt;/td&gt;
&lt;td&gt;Which channels assisted, and at which stage of the funnel?&lt;/td&gt;
&lt;td&gt;Beta since January 16, 2026; may not be available for every property&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The newest of these reports has two views. Assisted conversions is based on last click and surfaces channels that appeared earlier in converting paths. Refined funnel analysis is based on data-driven attribution. Because the two views use different models, differences between them are expected, not a bug.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Read Model Comparison Without Fooling Yourself
&lt;/h2&gt;

&lt;p&gt;Model comparison is the one report that turns the model choice from a setting into evidence. The table below is an illustrative example for one key event with 200 conversions, built for this guide rather than taken from a real property.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Channel&lt;/th&gt;
&lt;th&gt;Data-driven&lt;/th&gt;
&lt;th&gt;Paid and organic last click&lt;/th&gt;
&lt;th&gt;Difference&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Paid Search&lt;/td&gt;
&lt;td&gt;61&lt;/td&gt;
&lt;td&gt;66&lt;/td&gt;
&lt;td&gt;−5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Organic Search&lt;/td&gt;
&lt;td&gt;48&lt;/td&gt;
&lt;td&gt;52&lt;/td&gt;
&lt;td&gt;−4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid Social&lt;/td&gt;
&lt;td&gt;33&lt;/td&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;+19&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email&lt;/td&gt;
&lt;td&gt;28&lt;/td&gt;
&lt;td&gt;31&lt;/td&gt;
&lt;td&gt;−3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Direct&lt;/td&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;−5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Referral&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;−2&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Four habits keep the reading honest:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Look for the outlier, not the total.&lt;/strong&gt; Both columns add up to 200. Only Paid Social moves materially, up from 14 to 33, which marks it as an assisting channel that last click starves.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat a big gap as a hypothesis.&lt;/strong&gt; It justifies protecting that budget while a holdout test confirms the effect; it does not justify scaling spend on its own.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Be suspicious of identical columns.&lt;/strong&gt; If data-driven and last click match for a key event, either most journeys are single-touch or the model has little to learn from. It does not mean the two models agree on a deep truth.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use enough time.&lt;/strong&gt; Compare full weeks, leave out the last seven days because of reattribution, and never compare ranges that straddle a settings change.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why GA4 Numbers Do Not Match Google Ads or Meta
&lt;/h2&gt;

&lt;p&gt;Mismatched totals are the most common attribution complaint, and they usually have ordinary causes rather than errors:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Different models and windows.&lt;/strong&gt; Each platform counts inside its own rules, so totals cannot be expected to agree.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Different dates.&lt;/strong&gt; GA4 reports a conversion on the day it happened, while Google Ads by default attaches it to the day of the ad interaction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Different definitions.&lt;/strong&gt; An imported key event and a native Google Ads conversion tag may not fire or count identically.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Consent and blockers.&lt;/strong&gt; Each tool models missing data in its own way.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reattribution.&lt;/strong&gt; GA4 can still move credit for up to seven days.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For Meta the gap is larger, because Meta credits view-through and engage-through interactions that never create a GA4 session. Platform numbers are best used to optimize inside that platform, with a neutral source such as the CRM or store backend judging the total.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where GA4 Attribution Stops
&lt;/h2&gt;

&lt;p&gt;GA4 is excellent at what it can see and silent about the rest. It sees visits that reach the site, with source and medium tags, from consenting users. It does not see ad impressions, offline conversions such as calls and demos, or touches that happened on another device without a login. It also ships with only Google's cost data, so spend from Meta, TikTok or LinkedIn needs importing before a true ROAS comparison is possible.&lt;/p&gt;

&lt;p&gt;Tagging discipline decides how much of that visible traffic is usable. Untagged campaign links land in Direct or Referral, where no model can rescue them, and inconsistent UTM spellings split one campaign into several rows. A short naming convention for source, medium and campaign, applied to every paid link and every email, does more for attribution quality than any switch in the settings. Auditing a month of Conversion paths for unexpected Direct or "(not set)" values is a fast way to find the leaks.&lt;/p&gt;

&lt;p&gt;That is the point at which many teams outgrow GA4 alone. Once a budget is split across Google Ads, Meta, TikTok, LinkedIn and a CRM, the question becomes how to join spend, clicks and sales outcomes into one dataset and compare several models side by side. Better tagging helps first; a cross-channel analytics layer is what comes after.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Setup Checklist Before Trusting Any Report
&lt;/h2&gt;

&lt;p&gt;Attribution can only distribute credit for events that are measured properly. The foundations come first:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fire conversions once and correctly, using the &lt;a href="https://trackstack.tech/en/google-ads-conversion-tracking-setup-2026/" rel="noopener noreferrer"&gt;Google Ads conversion tracking setup&lt;/a&gt; guide.&lt;/li&gt;
&lt;li&gt;For stores, send revenue-bearing events through the &lt;a href="https://trackstack.tech/en/ga4-ecommerce-events-setup-guide/" rel="noopener noreferrer"&gt;GA4 ecommerce events setup guide&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;For lead generation, &lt;a href="https://trackstack.tech/en/track-form-submissions-ga4-no-code/" rel="noopener noreferrer"&gt;track form submissions in GA4 without code&lt;/a&gt; and mark the result as a key event.&lt;/li&gt;
&lt;li&gt;Keep campaign context available with &lt;a href="https://trackstack.tech/en/ga4-custom-dimensions-setup-2026/" rel="noopener noreferrer"&gt;GA4 custom dimensions&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Compare short and long journeys using &lt;a href="https://trackstack.tech/en/ga4-audiences-build-useful-segments/" rel="noopener noreferrer"&gt;useful GA4 audiences&lt;/a&gt; and segments.&lt;/li&gt;
&lt;li&gt;Bring sales outcomes in by &lt;a href="https://trackstack.tech/en/connect-google-sheets-crm-2026/" rel="noopener noreferrer"&gt;connecting Google Sheets to the CRM&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What attribution models does GA4 have?
&lt;/h3&gt;

&lt;p&gt;Three: data-driven, paid and organic last click, and Google paid channels last click. First-click, linear, time-decay and position-based were removed in November 2023, so rule-based comparisons need an external tool or an exported dataset.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the default attribution model in GA4?
&lt;/h3&gt;

&lt;p&gt;Data-driven attribution is the default reporting attribution model. Paid and organic last click remains available as a simpler baseline, and it is worth keeping an eye on in Model comparison.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I change the attribution model in GA4?
&lt;/h3&gt;

&lt;p&gt;Open Admin, go to Data display, choose Events and then Attribution settings. There the reporting attribution model, the channels that can receive credit and the lookback window can be reviewed, then saved. The Marketer role or higher is required on the property.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the GA4 lookback window?
&lt;/h3&gt;

&lt;p&gt;It is how far back GA4 searches for touchpoints before a key event. The defaults are 30 days for acquisition events and 90 days for other key events. Since August 2026, click-through windows can be set from 1 to 90 days and engaged-view windows from 1 to 30 days in conversion management.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why do GA4 and Google Ads show different conversions?
&lt;/h3&gt;

&lt;p&gt;The two tools use different models, windows, counting dates and conversion definitions, and GA4 can still reattribute credit for up to seven days. Small differences are normal. A large persistent gap usually points to a tagging or import problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can GA4 attribute Meta and TikTok campaigns?
&lt;/h3&gt;

&lt;p&gt;Only partly. GA4 can credit visits that arrive with campaign tags, but it never sees impressions, and view-through conversions stay on the ad platform. For cross-channel decisions, platform data combined with a neutral source and several models gives a more honest picture.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GA4 offers three reporting attribution models in 2026: data-driven (default), paid and organic last click, and Google paid channels last click.&lt;/li&gt;
&lt;li&gt;First-click, linear, time-decay and position-based have been gone since November 2023.&lt;/li&gt;
&lt;li&gt;Conversion windows became editable on August 11, 2026, and per-conversion settings are in beta.&lt;/li&gt;
&lt;li&gt;Model comparison is the report that turns the model choice into evidence; look for outliers, not totals.&lt;/li&gt;
&lt;li&gt;GA4 only sees tagged visits from consenting users, so cross-channel budget decisions need data from outside GA4.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://trackstack.tech/en/ga4-attribution-models-reports-2026/" rel="noopener noreferrer"&gt;Trackstack Editorial&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ga4</category>
      <category>analytics</category>
      <category>marketing</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Marketing Attribution Models Explained: Last-Click vs Multi-Touch vs Data-Driven (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Sat, 17 Oct 2026 12:22:01 +0000</pubDate>
      <link>https://dev.to/trackstack/marketing-attribution-models-explained-last-click-vs-multi-touch-vs-data-driven-2026-3hfe</link>
      <guid>https://dev.to/trackstack/marketing-attribution-models-explained-last-click-vs-multi-touch-vs-data-driven-2026-3hfe</guid>
      <description>&lt;p&gt;Every marketing team eventually runs into the same argument: Google Ads says it drove the sale, Meta says it did, and the CRM says the lead came from a webinar. Attribution models are the rules (or algorithms) that decide who gets credit when a customer touches several channels before converting. This guide is for marketers, founders and growth teams at small and mid-sized companies who need to choose a model without a data-science department. It covers how the six standard models work, shows one conversion credited to different channels under five of them, offers a scenario-to-model matrix, and lays out what GA4, Google Ads and Meta support in 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Is a Marketing Attribution Model?
&lt;/h2&gt;

&lt;p&gt;A marketing attribution model splits credit for a conversion (a purchase, signup or qualified lead) across the touchpoints that preceded it: say a paid social ad, a blog visit, a newsletter click and a branded search. The model does not change what happened; it changes which channel your reports say deserves budget.&lt;/p&gt;

&lt;p&gt;There are three families:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Single-touch&lt;/strong&gt; models give all credit to one interaction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rule-based multi-touch&lt;/strong&gt; models split it by a fixed formula.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data-driven&lt;/strong&gt; models let an algorithm estimate each touch's contribution from converting and non-converting paths.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Six Models at a Glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;How credit is assigned&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Main weakness&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;First-click&lt;/td&gt;
&lt;td&gt;100% to the first touch&lt;/td&gt;
&lt;td&gt;Judging awareness channels&lt;/td&gt;
&lt;td&gt;Ignores everything after discovery&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Last-click&lt;/td&gt;
&lt;td&gt;100% to the final touch&lt;/td&gt;
&lt;td&gt;Short, impulse-driven purchases&lt;/td&gt;
&lt;td&gt;Over-credits brand search and retargeting&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Linear&lt;/td&gt;
&lt;td&gt;Equal share to every touch&lt;/td&gt;
&lt;td&gt;A neutral first look at a journey&lt;/td&gt;
&lt;td&gt;Treats weak and strong touches alike&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time-decay&lt;/td&gt;
&lt;td&gt;More credit the closer to the sale&lt;/td&gt;
&lt;td&gt;Promotions and short campaigns&lt;/td&gt;
&lt;td&gt;Undervalues early awareness work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Position-based&lt;/td&gt;
&lt;td&gt;Typically 40% first, 40% last, 20% split across the middle&lt;/td&gt;
&lt;td&gt;Lead generation with a clear first and last step&lt;/td&gt;
&lt;td&gt;The split is a convention, not evidence&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data-driven&lt;/td&gt;
&lt;td&gt;Algorithm estimates each touch's contribution&lt;/td&gt;
&lt;td&gt;Accounts with enough clean conversion data&lt;/td&gt;
&lt;td&gt;Opaque, and limited to the data it can see&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The Single-Touch Models
&lt;/h2&gt;

&lt;h3&gt;
  
  
  First-click attribution
&lt;/h3&gt;

&lt;p&gt;First-click gives 100% of the credit to the first recorded touchpoint. It answers a useful question, what introduces people to a brand, so it is a reasonable lens for paid social, podcasts or content. But it ignores everything between discovery and purchase, so a channel that merely starts journeys looks like it closes them. It also depends on how far back tracking can see: a first touch in another browser or beyond cookie lifetimes is invisible, so "first" often means "first that could be seen".&lt;/p&gt;

&lt;h3&gt;
  
  
  Last-click attribution
&lt;/h3&gt;

&lt;p&gt;Last-click gives 100% of the credit to the final touchpoint before conversion. It is simple, easy to audit and was the default in many tools for years. It also flatters branded search, retargeting and direct traffic, which usually appear at the end of a journey someone else started. It is not useless: for low-priced impulse purchases where the journey lasts hours, the last touch often is the main driver. Treat it as a baseline, not a verdict.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Rule-Based Multi-Touch Models
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Linear attribution
&lt;/h3&gt;

&lt;p&gt;Linear splits credit equally across every touchpoint: four touches, 25% each. It is a fair start when it is unclear which stage matters most, and no channel in the path scores zero. The cost is that a casual ad view counts the same as the click that closed the deal.&lt;/p&gt;

&lt;h3&gt;
  
  
  Time-decay attribution
&lt;/h3&gt;

&lt;p&gt;Time-decay gives more credit to touches closer to the conversion, using a half-life: a touch loses half its weight for every N days before the sale. It suits short promotions, seasonal campaigns and nurture flows. It undervalues slow awareness work, so if content and social sit early in a long cycle, it will keep suggesting they be cut.&lt;/p&gt;

&lt;h3&gt;
  
  
  Position-based (U-shaped) attribution
&lt;/h3&gt;

&lt;p&gt;Position-based gives the first and last touches the biggest share, commonly 40% each, and splits the remaining 20% across the middle. It fits lead generation and B2B journeys with a clear first contact and demo request. But 40/20/40 is a convention, not a law of nature, and it undervalues middle touches such as a comparison page or case-study email.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data-Driven Attribution
&lt;/h2&gt;

&lt;p&gt;Data-driven attribution (DDA) estimates how much each touchpoint changed the probability of conversion by comparing converting paths with non-converting ones. Instead of assuming a shape, it learns one from the data. Google made DDA the default for new Google Ads conversion actions in late 2021, dropping the minimum-data requirement, and it is the default reporting model in GA4.&lt;/p&gt;

&lt;p&gt;It adapts as behavior changes and avoids hand-picked weights. But it is a black box, since Google does not disclose how credit is assigned. It only models journeys it can see, so cross-device or consent gaps mean it works on broken data. And its view is one platform's: Google Ads DDA credits Google Ads interactions, and GA4 DDA sees site visits but not an impression of a Meta or TikTok ad.&lt;/p&gt;

&lt;h2&gt;
  
  
  One Conversion, Five Models: A Worked Example
&lt;/h2&gt;

&lt;p&gt;The journey below is an illustrative example, not client data. A customer buys a $1,200 annual plan after four touches:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;12 days before purchase: clicks a Meta ad (paid social).&lt;/li&gt;
&lt;li&gt;9 days before: reads a blog post found through organic search.&lt;/li&gt;
&lt;li&gt;4 days before: clicks a link in a newsletter email.&lt;/li&gt;
&lt;li&gt;1 day before: searches the brand name, clicks a Google Ads search ad, and buys.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Touchpoint&lt;/th&gt;
&lt;th&gt;First-click&lt;/th&gt;
&lt;th&gt;Last-click&lt;/th&gt;
&lt;th&gt;Linear&lt;/th&gt;
&lt;th&gt;Position-based (40/10/10/40)&lt;/th&gt;
&lt;th&gt;Time-decay (7-day half-life)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Meta ad&lt;/td&gt;
&lt;td&gt;$1,200&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$300&lt;/td&gt;
&lt;td&gt;$480&lt;/td&gt;
&lt;td&gt;$159&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Organic blog post&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$300&lt;/td&gt;
&lt;td&gt;$120&lt;/td&gt;
&lt;td&gt;$215&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Newsletter email&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$300&lt;/td&gt;
&lt;td&gt;$120&lt;/td&gt;
&lt;td&gt;$352&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google Ads brand search&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;$1,200&lt;/td&gt;
&lt;td&gt;$300&lt;/td&gt;
&lt;td&gt;$480&lt;/td&gt;
&lt;td&gt;$474&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Reading down the columns gives five stories. First-click says Meta is the best channel and brand search is worthless; last-click says the opposite. Linear calls every channel equal. Position-based splits credit between Meta and brand search. Time-decay crowns brand search but gives the newsletter more than the blog post or the Meta ad.&lt;/p&gt;

&lt;p&gt;Now the budget decision. A team on last-click sees $1,200 credited to branded search and may cut paid social. Yet the branded search happened because the Meta ad and blog post created awareness; remove them and branded searches shrink. Branded search and retargeting routinely collect credit for demand created elsewhere.&lt;/p&gt;

&lt;p&gt;The fix is not to crown a new winning model but to compare two or three and focus on where they disagree. Meta's credit ranges from $0 to $1,200 here, which is the honest answer: its contribution is uncertain, and a holdout test or controlled spend change resolves it. A data-driven model is absent because it learns weights from thousands of paths and cannot be computed by hand for one journey.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Single-Touch Models Mislead
&lt;/h2&gt;

&lt;p&gt;Single-touch models are incomplete, and the missing part is what budget decisions depend on. They reward position rather than contribution, so a channel earns credit for being first or last whatever it did for the customer. They create predictable budget drift: last-click pushes spend toward brand search and retargeting, first-click toward awareness channels that never close alone. And they hide interaction effects, such as email working only because an ad warmed the audience.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Attribution Model to Use: A Scenario Matrix
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scenario&lt;/th&gt;
&lt;th&gt;Typical journey&lt;/th&gt;
&lt;th&gt;Suggested model&lt;/th&gt;
&lt;th&gt;Caveat&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Impulse ecommerce, low price&lt;/td&gt;
&lt;td&gt;Hours to a few days&lt;/td&gt;
&lt;td&gt;Last-click or data-driven&lt;/td&gt;
&lt;td&gt;The last touch is close to the cause&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Considered purchase or SaaS trial&lt;/td&gt;
&lt;td&gt;One to four weeks&lt;/td&gt;
&lt;td&gt;Data-driven, checked against position-based&lt;/td&gt;
&lt;td&gt;Several research touches before buying&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;B2B lead generation with a CRM&lt;/td&gt;
&lt;td&gt;Weeks to months&lt;/td&gt;
&lt;td&gt;Position-based, then data-driven on qualified leads&lt;/td&gt;
&lt;td&gt;Form fills are not revenue; join CRM outcomes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Judging top-of-funnel channels&lt;/td&gt;
&lt;td&gt;Any&lt;/td&gt;
&lt;td&gt;First-click as a lens beside last-click&lt;/td&gt;
&lt;td&gt;Shows who starts journeys, not who finishes them&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Seasonal sale or time-boxed promo&lt;/td&gt;
&lt;td&gt;Days&lt;/td&gt;
&lt;td&gt;Time-decay&lt;/td&gt;
&lt;td&gt;Short half-life, or early touches vanish&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Very low conversion volume&lt;/td&gt;
&lt;td&gt;Any&lt;/td&gt;
&lt;td&gt;Linear or position-based plus holdout tests&lt;/td&gt;
&lt;td&gt;Algorithms have little to learn from&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Budget split across Google, Meta, TikTok, LinkedIn&lt;/td&gt;
&lt;td&gt;Cross-channel&lt;/td&gt;
&lt;td&gt;Several models side by side on joined data&lt;/td&gt;
&lt;td&gt;No single platform's report is neutral&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two habits matter more than the model. Decide the question first: "which channel gets the next $5,000?" differs from "where do customers first hear about us?". And never change models mid-quarter and compare across the change; a switch redistributes credit without one extra sale.&lt;/p&gt;

&lt;h2&gt;
  
  
  What GA4, Google Ads and Meta Support in 2026
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GA4 and Google Ads.&lt;/strong&gt; Google retired first-click, linear, time-decay and position-based from both products in 2023, citing low adoption (under 3% of conversions), leaving data-driven and last-click. GA4 reporting offers data-driven, paid and organic last click, and Google paid channels last click. For first-touch-style analysis, GA4's path exploration shows early touchpoints without changing the reporting model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Meta.&lt;/strong&gt; On January 12, 2026 Meta removed the 7-day view and 28-day view windows, so the longest view window is one day; 28-day click remains for comparison only. A March 2026 change limited click-through to actual link clicks and moved other interactions into a one-day engage-through category. The default is now 7-day click, 1-day engage-through, 1-day view. Reported conversions can drop without any real change in performance, so 2025 and 2026 Meta reports are not like-for-like.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The grading-their-own-homework problem.&lt;/strong&gt; Each platform counts conversions inside its own windows and logic, so what Google, Meta and an email tool claim usually adds up to more than real sales. Platform numbers are best used to optimize inside each platform, with a neutral source (CRM, store backend or joined dataset) judging the whole.&lt;/p&gt;

&lt;h2&gt;
  
  
  What No Attribution Model Can Fix
&lt;/h2&gt;

&lt;p&gt;Models only redistribute the data they are given. Four gaps sit upstream of any model:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cross-device and consent gaps, where one person looks like several visitors, or like none.&lt;/li&gt;
&lt;li&gt;Offline conversions such as phone calls, demos and in-store purchases that never reach analytics.&lt;/li&gt;
&lt;li&gt;View-through influence inside walled gardens.&lt;/li&gt;
&lt;li&gt;Double counting across platforms that each claim the same sale.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two methods complement attribution. Incrementality testing (a geo holdout or conversion-lift study) measures what happens when a channel is reduced, the closest thing to a causal answer. Marketing mix modeling works from aggregate spend and sales, needs no user-level tracking and suits budget questions across many channels.&lt;/p&gt;

&lt;p&gt;Once journeys span Google Ads, Meta, TikTok, LinkedIn and a CRM, one joined dataset becomes necessary: spend, clicks and CRM outcomes keyed to the same campaign and customer. That is usually where teams outgrow single-platform reports and look at cross-channel analytics tooling for ROAS, CAC and journey views.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get the Data Right Before Choosing a Model
&lt;/h2&gt;

&lt;p&gt;A sophisticated model on poor tracking produces confident nonsense. The foundations come first:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Conversion firing: the &lt;a href="https://trackstack.tech/en/google-ads-conversion-tracking-setup-2026/" rel="noopener noreferrer"&gt;Google Ads conversion tracking setup&lt;/a&gt; guide covers the common breakages.&lt;/li&gt;
&lt;li&gt;Stores: send revenue events via the &lt;a href="https://trackstack.tech/en/ga4-ecommerce-events-setup-guide/" rel="noopener noreferrer"&gt;GA4 ecommerce events setup guide&lt;/a&gt;, so credit is measured in money.&lt;/li&gt;
&lt;li&gt;Lead-gen sites: &lt;a href="https://trackstack.tech/en/track-form-submissions-ga4-no-code/" rel="noopener noreferrer"&gt;track form submissions in GA4 without code&lt;/a&gt; so a lead is a real event.&lt;/li&gt;
&lt;li&gt;Campaign context: &lt;a href="https://trackstack.tech/en/ga4-custom-dimensions-setup-2026/" rel="noopener noreferrer"&gt;set up GA4 custom dimensions&lt;/a&gt; for the parameters being tagged.&lt;/li&gt;
&lt;li&gt;Journey comparison: &lt;a href="https://trackstack.tech/en/ga4-audiences-build-useful-segments/" rel="noopener noreferrer"&gt;build useful GA4 audiences&lt;/a&gt; and segments to compare short and long journeys.&lt;/li&gt;
&lt;li&gt;Sales outcomes: &lt;a href="https://trackstack.tech/en/connect-google-sheets-crm-2026/" rel="noopener noreferrer"&gt;connect Google Sheets to the CRM&lt;/a&gt;, the cheapest first step toward revenue-level attribution.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Acquisition is only half the story; for post-signup behavior, compare &lt;a href="https://trackstack.tech/en/mixpanel-vs-amplitude-2026/" rel="noopener noreferrer"&gt;Mixpanel and Amplitude&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is the best marketing attribution model?
&lt;/h3&gt;

&lt;p&gt;There is no universal best. Data-driven attribution is the strongest default when the platform supports it and tracking is clean. Compare it with last-click and a position-based view, and treat big disagreements as a prompt to test, not a result to trust.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the difference between single-touch and multi-touch attribution?
&lt;/h3&gt;

&lt;p&gt;Single-touch attribution gives all credit to one interaction. Multi-touch spreads it across several, by a fixed rule (linear, time-decay, position-based) or an algorithm (data-driven). Multi-touch reflects real behavior better, but still depends on touchpoints being tracked.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does GA4 still offer first-click, linear, time-decay and position-based models?
&lt;/h3&gt;

&lt;p&gt;No. Google removed them from GA4 and Google Ads in 2023. Rule-based views now need an external tool, a spreadsheet model built from exported paths, or a dedicated attribution platform.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is data-driven attribution better than last-click?
&lt;/h3&gt;

&lt;p&gt;Usually, not automatically. It captures earlier touches and adapts over time, while last-click ignores them. The trade-offs are opacity and a narrow field of view. For short, impulse-driven purchases the two often give similar results.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which attribution model should a small business use?
&lt;/h3&gt;

&lt;p&gt;Start with the platform default (data-driven in GA4 and Google Ads), keep last-click as a baseline, and add a position-based view if the sales cycle exceeds a week or two. With very few conversions, simple comparisons and occasional on/off tests beat trusting any algorithm.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do attribution, incrementality and marketing mix modeling differ?
&lt;/h3&gt;

&lt;p&gt;Attribution assigns credit to touchpoints in tracked journeys. Incrementality testing measures the extra conversions a channel causes by comparing exposed and unexposed groups. Marketing mix modeling estimates channel effects from aggregate spend and sales. Attribution is fastest; the other two are better evidence for big budget decisions.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Data-driven attribution is the best default in 2026 where a platform offers it; keep last-click as a baseline.&lt;/li&gt;
&lt;li&gt;Linear, time-decay and position-based work as sanity checks for low volume or long sales cycles.&lt;/li&gt;
&lt;li&gt;First-click and last-click alone mislead: each gives 100% of the credit to one touch.&lt;/li&gt;
&lt;li&gt;GA4 and Google Ads only offer data-driven and last-click; Meta's view windows shrank to one day in January 2026.&lt;/li&gt;
&lt;li&gt;Compare two or three models, focus on where they disagree, and settle the big disagreements with holdout tests.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://trackstack.tech/en/marketing-attribution-models-explained-2026/" rel="noopener noreferrer"&gt;Trackstack Editorial&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>marketing</category>
      <category>ga4</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Heatmaps vs Session Recordings: When to Use Each (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Mon, 20 Jul 2026 05:48:15 +0000</pubDate>
      <link>https://dev.to/trackstack/heatmaps-vs-session-recordings-when-to-use-each-2026-4k0n</link>
      <guid>https://dev.to/trackstack/heatmaps-vs-session-recordings-when-to-use-each-2026-4k0n</guid>
      <description>&lt;p&gt;Heatmaps and session recordings get bundled into the same "behavioral analytics" category, and most teams install both, look at both once, and never build a repeatable workflow around either. Here's a clear rule for which tool to reach for first, how much traffic is actually needed before trusting what's on screen, and how to use the two together instead of picking one and ignoring the other.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick Answer
&lt;/h2&gt;

&lt;p&gt;Use a heatmap when the question starts with "what are most visitors doing" — CTA placement, scroll depth, aggregate attention on a page. Use a session recording when the question starts with "why did this specific visitor drop off." Heatmaps need roughly 2,000-3,000 recorded sessions per page before patterns are reliable; below that, filter straight to recordings instead of trusting a noisy map.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a Heatmap Actually Shows
&lt;/h2&gt;

&lt;p&gt;A heatmap aggregates behavior from many sessions into a single color-coded overlay on a page. Three types matter most: click maps (where visitors click or tap, including on non-interactive elements visitors mistakenly think are clickable), scroll maps (how far down a page visitors actually read, revealing whether key content sits below a "false bottom"), and move/attention maps (where the cursor hovers, a rough proxy for visual attention on desktop).&lt;/p&gt;

&lt;p&gt;A heatmap shows what happened and where. It never explains why — it flattens hundreds of different individual stories into a single aggregate image, so a button clicked by confused visitors looks identical to one clicked by satisfied ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a Session Recording Actually Shows
&lt;/h2&gt;

&lt;p&gt;A session recording — also called session replay — reconstructs one visitor's complete journey: mouse movements, clicks, scrolls, typing, hesitation, and page navigation, played back like a video. It isn't a literal screen recording; it's rebuilt from the actual DOM events the browser captured.&lt;/p&gt;

&lt;p&gt;This is an investigative tool, not a monitoring one. Watching recordings at random without a specific question is one of the least efficient ways to spend CRO time — it mostly confirms assumptions that already existed rather than surfacing anything new.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Core Difference: Aggregate vs Individual
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Heatmap&lt;/th&gt;
&lt;th&gt;Session Recording&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Answers&lt;/td&gt;
&lt;td&gt;What are most visitors doing&lt;/td&gt;
&lt;td&gt;Why did this visitor do that&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scope&lt;/td&gt;
&lt;td&gt;Aggregate, hundreds-thousands of sessions&lt;/td&gt;
&lt;td&gt;Individual, one session at a time&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Minimum data for reliability&lt;/td&gt;
&lt;td&gt;~2,000-3,000 sessions/page&lt;/td&gt;
&lt;td&gt;10-15 filtered recordings of the same pattern&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best for&lt;/td&gt;
&lt;td&gt;Layout decisions, CTA placement, above-the-fold content&lt;/td&gt;
&lt;td&gt;Debugging funnel drop-off, form abandonment, rage clicks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Typical workflow position&lt;/td&gt;
&lt;td&gt;First — find the pattern&lt;/td&gt;
&lt;td&gt;Second — confirm the mechanism&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When to Reach for a Heatmap First
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Deciding where to place a CTA, image, or piece of content on a high-traffic page and wanting data instead of a guess.&lt;/li&gt;
&lt;li&gt;Comparing desktop vs mobile attention zones on the same page — these are frequently very different and worth checking before a redesign.&lt;/li&gt;
&lt;li&gt;Needing a fast, shareable visual for stakeholders who won't sit through recordings but will understand a red-blue overlay in five seconds.&lt;/li&gt;
&lt;li&gt;Validating whether a recent layout change actually shifted behavior — heatmap comparison mode across two date ranges is faster than watching dozens of before/after recordings.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When to Reach for Session Recordings First
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Traffic is healthy but conversions aren't moving, and it's unclear what's stopping people — the single clearest trigger for pulling up recordings.&lt;/li&gt;
&lt;li&gt;There's already a specific, well-defined question, like "why do mobile visitors abandon on the shipping form."&lt;/li&gt;
&lt;li&gt;A funnel report shows a specific step losing users and the mechanism, not just the number, needs explaining.&lt;/li&gt;
&lt;li&gt;Chasing a bug report or support ticket and needing to reproduce exactly what a user experienced.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Diagnostic Workflow: Using Both Together
&lt;/h2&gt;

&lt;p&gt;The teams that get the most out of behavioral analytics don't pick one tool — they run a sequence:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start with funnel analysis (GA4 key events or equivalent) to find where in the journey users are actually dropping off.&lt;/li&gt;
&lt;li&gt;Pull up a heatmap on that specific page to spot the pattern — a scroll map showing 70% of visitors never reach the CTA, or a click map showing clicks piling up on a non-interactive image.&lt;/li&gt;
&lt;li&gt;Filter session recordings down to visitors who match that exact pattern — same page, same behavior, same device type if relevant — and watch 10 to 15 of them.&lt;/li&gt;
&lt;li&gt;Form a specific, testable hypothesis from what was observed, ship the fix, then re-run the heatmap to confirm behavior actually shifted.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A repeating pattern across 10+ sessions is a real signal; three rage clicks across three sessions might just be coincidence.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Much Traffic You Actually Need
&lt;/h2&gt;

&lt;p&gt;A heatmap built on too little traffic is decorative, not diagnostic. General guidance: at least a few hundred sessions before click and scroll patterns start meaning anything, and roughly 2,000-3,000 recorded sessions per page before finer patterns stabilize. Under 200 sessions a week, treat any heatmap as noise and go straight to recordings or a small round of moderated usability testing instead.&lt;/p&gt;

&lt;p&gt;A homepage or top landing page hits that threshold fast, but a seasonal campaign page or a low-traffic blog post may never accumulate enough sessions to heatmap reliably — don't force a heatmap where the sample size can't support one.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Tool Landscape in 2026
&lt;/h2&gt;

&lt;p&gt;The category has consolidated. Hotjar is now part of Contentsquare, with features split into three separately billed modules — Experience Analytics (heatmaps and recordings, from $49/month), Voice of Customer (surveys, from $99/month), and Product Analytics (custom pricing) — so teams that budgeted for one Hotjar line item now need to model three.&lt;/p&gt;

&lt;p&gt;Microsoft Clarity remains 100% free at any traffic volume and covers the core heatmap and recording use cases well enough that most teams starting out should install it before paying for anything. Smartlook reached end-of-sale on May 31, 2026, following Cisco's acquisition and its integration into AppDynamics — anyone still running it needs a migration plan now, not later.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Bot Traffic Problem Nobody Mentions
&lt;/h2&gt;

&lt;p&gt;A meaningful share of "sessions" hitting sites in 2026 aren't human visitors at all — they're AI crawlers and scraping bots — and most heatmap and session recording tools have no upstream filter for this. A rage-click cluster on a checkout button might be real customer confusion, or it might be a headless browser bot failing to navigate a JavaScript-rendered form.&lt;/p&gt;

&lt;p&gt;If a heatmap tool records everything the browser sends without bot filtering, an "aggregate pattern" from 3,000 sessions might actually represent far fewer real humans than the count suggests. Before trusting a heatmap pattern enough to redesign around it, it's worth sanity-checking the traffic source mix for that page — if a large share comes from data-center IPs or known crawler user agents, filter those out before reading anything into the pattern.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Ways Teams Misread the Data
&lt;/h2&gt;

&lt;p&gt;Confusing click density with conversion contribution is the most common heatmap mistake: a click map that lights up bright red on social icons isn't a success signal, it's a distraction signal — visitors are clicking away from the purchase decision, not toward it.&lt;/p&gt;

&lt;p&gt;On the recording side, the equivalent mistake is watching sessions without a hypothesis. Always filter first — by page, by behavior, by device, by traffic source — and only then start watching. Not segmenting by device is a third common gap: mobile and desktop attention zones are frequently very different on the same page, and an unsegmented heatmap will average the two into a pattern that describes neither audience accurately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Form Analytics Fits In
&lt;/h2&gt;

&lt;p&gt;Neither a standard click heatmap nor a raw session recording is built to efficiently answer "which specific form field is causing abandonment" on its own — it would take watching dozens of recordings just to spot the pattern manually. Form analytics, bundled in tools like Mouseflow and Lucky Orange (sold as a separate add-on in Hotjar's post-Contentsquare split), tracks field-level metrics directly: time spent per field, which fields get abandoned most, and how many attempts a field takes before submission succeeds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy and Consent Considerations
&lt;/h2&gt;

&lt;p&gt;Session recordings capture form inputs, so masking sensitive fields (passwords, payment details, personal data) is not optional — every tool worth using offers field-level masking, and it should be on by default for any field collecting PII.&lt;/p&gt;

&lt;p&gt;Both heatmaps and session recordings fall under the same cookie consent requirements as other analytics tags: they should only fire after a visitor consents. Anyone serving EU or UK traffic should confirm their CMP blocks the heatmap/recording script pre-consent the same way it blocks other marketing and analytics tags — a separately-installed heatmap script is a common place for consent gaps to slip through unnoticed.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need both heatmaps and session recordings, or can I pick one?&lt;/strong&gt;&lt;br&gt;
Most modern tools (Hotjar, Clarity, Mouseflow, LogRocket) include both in the same subscription, so there's rarely a reason to run only one. Heatmaps find the pattern; recordings explain the mechanism behind it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How many session recordings should I watch before drawing a conclusion?&lt;/strong&gt;&lt;br&gt;
At least 10 to 15 recordings showing the same pattern. Three examples might be a coincidence; ten or more gives enough density to separate a real, fixable issue from one-off user error.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How much traffic do I need before a heatmap is reliable?&lt;/strong&gt;&lt;br&gt;
Roughly a few hundred sessions as a bare minimum, with patterns stabilizing around 2,000-3,000 recorded sessions per page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Microsoft Clarity actually good enough, or is Hotjar needed?&lt;/strong&gt;&lt;br&gt;
For most teams, functionally yes — Clarity is free at any traffic volume and covers the core heatmap and recording use cases. Paid tiers add polish, surveys, and deeper integrations that matter at scale.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can heatmaps or session recordings replace GA4?&lt;/strong&gt;&lt;br&gt;
No. GA4 shows what happened in aggregate numbers — conversion rates, funnel drop-off, traffic sources. Heatmaps and session recordings show the visual and behavioral "why" behind those numbers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do session recordings slow down a website?&lt;/strong&gt;&lt;br&gt;
Modern recording scripts are lightweight and asynchronous, so impact is usually minimal but not zero — on already slow sites, an additional tracking script can measurably affect Core Web Vitals. Loading it via a tag manager rather than hardcoding it makes it easy to pause or remove if it becomes a performance issue.&lt;/p&gt;




&lt;p&gt;Heatmaps answer "what are most visitors doing" (aggregate, needs 2,000-3,000 sessions/page to be reliable). Session recordings answer "why did this visitor do that" (individual, needs 10-15 filtered recordings to spot a real pattern). Run them in sequence: funnel analysis finds the drop-off, heatmap finds the pattern, recordings confirm the mechanism. Watch for AI/bot traffic contaminating both — most tools don't filter it upstream, so "aggregate" patterns may represent fewer real humans than the session count suggests. Microsoft Clarity is free and good enough for most teams starting out; Hotjar (now split under Contentsquare) and Mouseflow add depth at scale.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>ux</category>
      <category>webdev</category>
      <category>marketing</category>
    </item>
    <item>
      <title>How to Set Up Conversion Tracking in Google Ads</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Mon, 13 Jul 2026 05:46:12 +0000</pubDate>
      <link>https://dev.to/trackstack/how-to-set-up-conversion-tracking-in-google-ads-17a6</link>
      <guid>https://dev.to/trackstack/how-to-set-up-conversion-tracking-in-google-ads-17a6</guid>
      <description>&lt;p&gt;Conversion tracking is the one setup task that determines whether every other Google Ads decision — bidding, budget, keyword targeting — is based on real signal or guesswork. This walks through a current, correct 2026 setup: which tracking method to choose, how to enable Enhanced Conversions, and how to stay compliant with EEA/UK traffic. No agency jargon, just the exact steps and the reasoning behind each one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two Ways to Track Conversions: Native Tag vs GA4 Key Events Import
&lt;/h2&gt;

&lt;p&gt;Before touching Google Tag Manager, the measurement path needs deciding first, because mixing the two without understanding the tradeoff is the most common setup mistake out there.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Native Google Ads Tag&lt;/th&gt;
&lt;th&gt;GA4 Key Events Import&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Setup location&lt;/td&gt;
&lt;td&gt;Google Ads → Goals → Conversions&lt;/td&gt;
&lt;td&gt;GA4 → link to Ads, mark event as Key Event&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reporting delay&lt;/td&gt;
&lt;td&gt;Usually within 24 hours&lt;/td&gt;
&lt;td&gt;6-24 hours, sometimes longer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Attribution model&lt;/td&gt;
&lt;td&gt;Google Ads data-driven attribution&lt;/td&gt;
&lt;td&gt;GA4's own attribution model&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enhanced Conversions support&lt;/td&gt;
&lt;td&gt;Full, native&lt;/td&gt;
&lt;td&gt;Limited&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best used for&lt;/td&gt;
&lt;td&gt;Primary bidding signal&lt;/td&gt;
&lt;td&gt;Secondary measurement, diagnostics&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;GA4 renamed "Conversions" to "Key Events" back in March 2024, and it's easy to assume importing them into Google Ads is equivalent to native tracking. It isn't. GA4 imports run on GA4's own attribution model and typically arrive with a longer delay, so Smart Bidding works with staler, differently-weighted data. Use the native Google Ads conversion tag for whatever action drives bidding, and keep GA4 as the analysis and diagnostics layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step-by-Step: Creating a Conversion Action
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In Google Ads, go to Goals → Conversions → + New conversion action.&lt;/li&gt;
&lt;li&gt;Choose the source: Website, App, Phone calls, or Import (for offline/CRM data).&lt;/li&gt;
&lt;li&gt;Name the action clearly — "Purchase," "Lead Form Submit," "Phone Call 60s+" — not "Conversion 1."&lt;/li&gt;
&lt;li&gt;Set the value: a fixed value for consistent-value actions, or "Use different values for each conversion" for e-commerce carrying real order totals.&lt;/li&gt;
&lt;li&gt;Set the count setting to "One" for leads and signups, "Every" for purchases where each transaction matters.&lt;/li&gt;
&lt;li&gt;Choose a conversion window — 7 days for impulse purchases, 30 for considered purchases, up to 90 days for B2B sales cycles.&lt;/li&gt;
&lt;li&gt;Set the attribution model to data-driven (Google's default and recommended choice for most accounts in 2026).&lt;/li&gt;
&lt;li&gt;Deploy the resulting Event Snippet via Google Tag Manager, triggered on the confirmation or thank-you page — not the form page itself.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If tags are already being managed through GTM for GA4 ecommerce events, add the Google Ads Conversion tag as a parallel tag firing on the same trigger — no need to duplicate the trigger logic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Enhanced Conversions: Setup and Why It Matters
&lt;/h2&gt;

&lt;p&gt;Enhanced Conversions hashes first-party data a customer already provided — email, phone, name — using SHA-256, then matches it against signed-in Google accounts to recover conversions that cookies and ad blockers would otherwise hide. Google's published case studies show a 5-17% average lift in reported conversion volume once enabled.&lt;/p&gt;

&lt;p&gt;To turn it on: in the conversion action's data sources panel, select "Conversions" and enable "Turn on enhanced conversions" under Customer data use. In GTM, use manual configuration (not automatic detection) for the User-Provided Data fields, mapping email and phone variables explicitly from the dataLayer — automatic detection carries a higher compliance risk since it scrapes form fields without an explicit mapping.&lt;/p&gt;

&lt;p&gt;One important 2026 deadline: starting June 15, 2026, offline conversion imports and Enhanced Conversions for leads uploads migrated to Google's Data Manager API and are blocked from the older Google Ads API. Any custom integration built for offline conversion uploads before that date needs checking — this is the kind of silent breakage that shows a green checkmark in the dashboard while quietly stopping data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Consent Mode v2 and EEA/UK Compliance
&lt;/h2&gt;

&lt;p&gt;Consent Mode v2 has been mandatory for advertisers serving EEA and UK users since March 2024, and it's not optional with any European traffic. The mechanism: when a visitor denies consent, Google tags don't just switch off — they send anonymous "cookieless pings" that Google uses to model the conversions it can't directly observe, recovering a meaningful share of otherwise-lost data.&lt;/p&gt;

&lt;p&gt;A cookie consent banner needs to push four required parameters — &lt;code&gt;ad_storage&lt;/code&gt;, &lt;code&gt;ad_user_data&lt;/code&gt;, &lt;code&gt;ad_personalization&lt;/code&gt;, &lt;code&gt;analytics_storage&lt;/code&gt; — to the dataLayer before any Google tag fires, with a default state of "denied" until the visitor actively consents. When managing this through server-side tracking, consent state has to be communicated on both the client and server sides — server-side alone does not exempt anyone from consent requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Server-Side Tracking for Higher Accuracy
&lt;/h2&gt;

&lt;p&gt;Server-side Google Tag Manager sends conversion data from a business's own infrastructure instead of the visitor's browser, bypassing ad blockers, Safari's Intelligent Tracking Prevention, and JavaScript failures entirely. Teams running it report recovering an additional 8-15% of conversions on iOS-heavy traffic, plus faster page loads since fewer client-side scripts are running.&lt;/p&gt;

&lt;p&gt;It's not free — hosting a container typically runs $20-100/month depending on traffic volume, and it needs proper setup to avoid becoming just another point of failure. Rule of thumb: under roughly $10,000/month in Google Ads spend, client-side tracking with Enhanced Conversions is usually accurate enough. Above that, or with a real gap between platform-reported conversions and actual sales, server-side tends to pay for itself quickly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Offline Conversion Imports for Lead-Gen Businesses
&lt;/h2&gt;

&lt;p&gt;For B2B or high-consideration businesses, the form submission isn't the outcome that matters — the closed deal 30 to 90 days later is. Offline conversion imports close that loop: capture the GCLID (Google Click ID) at form submission and store it alongside the lead record in the CRM, then upload it back to Google Ads once the deal closes, with a real dollar value attached. This lets Smart Bidding optimize toward leads that actually become customers, not just leads that fill out a form.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choosing the Right Attribution Model
&lt;/h2&gt;

&lt;p&gt;Data-driven attribution (DDA) is Google's default and the right choice for roughly 90% of accounts in 2026. Instead of crediting 100% of a conversion to the last click — the old "last-click" model, which systematically over-credits branded search and under-credits upper-funnel awareness campaigns — DDA uses machine learning to distribute credit across every touchpoint based on the account's actual conversion patterns.&lt;/p&gt;

&lt;p&gt;The attribution model can be reviewed or changed per conversion action under Tools and Settings → Conversions → select the action → Edit settings. The only common reason to override DDA is a genuinely low-volume account (under roughly 300 conversions in the last 30 days), where the model doesn't have enough data to learn from and automatically falls back to a simpler rules-based model — nothing needs configuring differently there, Google handles the fallback.&lt;/p&gt;

&lt;p&gt;Worth flagging for teams running both Google Ads and Meta campaigns: attribution models don't talk to each other across platforms. Facebook and Instagram campaigns will often report overlapping conversions with different credit assigned, and reconciling that against actual revenue — not either platform's self-reported number — is the only way to know real blended CAC.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Verify Your Setup Is Working
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Check Goals → Conversions → Summary for a green checkmark; a yellow warning means the tag fired but hasn't recorded a conversion yet — wait 24-48 hours before troubleshooting further.&lt;/li&gt;
&lt;li&gt;Use GTM Preview mode to walk through a full test conversion and confirm the Conversion Linker, Google Ads Conversion tag, and GA4 Config tag all fire in the correct order on the correct page.&lt;/li&gt;
&lt;li&gt;Open the DevTools Network tab and check for &lt;code&gt;gcs=G100&lt;/code&gt; before consent is granted, confirming Consent Mode defaults are actually being respected pre-consent.&lt;/li&gt;
&lt;li&gt;Cross-check reported conversion counts against the CRM or order system monthly — a persistent mismatch usually points to duplicate firing or a broken trigger, not a Google Ads bug.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A recent audit on a mid-size SaaS account found the Conversion Linker tag missing from one landing page template — a silent gap that had been under-reporting form-fill conversions by roughly 12% for three months, invisible in the dashboard because the tag that was firing still showed a green checkmark.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Mistakes That Break Conversion Tracking
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Multiple primary conversions competing for bidding credit&lt;/strong&gt; — counting both "form submit" and "purchase" as primary in the same campaign confuses Smart Bidding about what to optimize for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low-value micro-conversions set as primary&lt;/strong&gt; — page views or newsletter signups pulling bidding attention away from actual revenue-generating actions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Conversion value left at a flat $1&lt;/strong&gt; — Target ROAS can't prioritize high-value customers if every conversion looks identical.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate firing on page refresh&lt;/strong&gt; — the thank-you page firing a second conversion when a user hits refresh or the back button.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-domain tracking gaps&lt;/strong&gt; — a separate checkout domain breaking the click ID chain, so purchases get attributed as direct traffic instead of paid.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;How long does it take for conversions to show up in Google Ads?&lt;/strong&gt;&lt;br&gt;
Typically within 24 hours for standard conversions, though cross-device and view-through conversions can take up to 3 days to fully process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Native Google Ads tag or GA4 import?&lt;/strong&gt;&lt;br&gt;
Use the native tag as the primary bidding signal. GA4 Key Events imports run on a different attribution model with longer reporting delays, giving Smart Bidding a weaker, staler signal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Enhanced Conversions mandatory?&lt;/strong&gt;&lt;br&gt;
Not mandatory, but strongly recommended for any account with EEA/UK traffic or spending over roughly $1,000/month. Google's own data shows a 5-17% lift in reported conversions once correctly configured.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Consent Mode v2 needed for US-only advertisers?&lt;/strong&gt;&lt;br&gt;
Not legally required as of 2026, but several states (California, Colorado, Virginia, Connecticut, and others) have privacy laws creating similar obligations, and Consent Mode's conversion modeling improves accuracy regardless of jurisdiction.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What changed with offline conversion imports in June 2026?&lt;/strong&gt;&lt;br&gt;
Starting June 15, 2026, offline conversion imports and Enhanced Conversions for leads uploads moved to Google's Data Manager API and were blocked from the older Google Ads API. Custom integrations built before that date need checking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is server-side tracking worth it for a small business?&lt;/strong&gt;&lt;br&gt;
Usually not below roughly $10,000/month in ad spend. Above that threshold, or with a persistent gap between platform-reported and actual sales, the 8-15% additional recovered conversions typically justify the hosting cost.&lt;/p&gt;




&lt;p&gt;Create the conversion action natively in Google Ads (not via GA4 import) and deploy it through GTM. Turn on Enhanced Conversions immediately for a 5-17% lift in reported conversions. If serving EEA/UK traffic, Consent Mode v2 is mandatory — push the four consent parameters to the dataLayer before any Google tag fires. Watch the June 15, 2026 deadline: offline conversion imports moved to the Data Manager API and old integrations may have silently broken. Server-side tracking pays off above ~$10K/month in spend. Verify monthly with GTM Preview and a CRM cross-check — broken tracking looks fine in the dashboard while quietly costing you optimization accuracy.&lt;/p&gt;

</description>
      <category>googleads</category>
      <category>analytics</category>
      <category>marketing</category>
      <category>ppc</category>
    </item>
    <item>
      <title>Hotjar vs Microsoft Clarity vs LogRocket</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Wed, 01 Jul 2026 18:18:08 +0000</pubDate>
      <link>https://dev.to/trackstack/hotjar-vs-microsoft-clarity-vs-logrocket-5888</link>
      <guid>https://dev.to/trackstack/hotjar-vs-microsoft-clarity-vs-logrocket-5888</guid>
      <description>&lt;p&gt;Heatmaps and session recordings all look similar in a demo, which makes &lt;strong&gt;Hotjar vs Microsoft Clarity vs LogRocket&lt;/strong&gt; a deceptively hard choice. The truth is these three are not really competitors — they are built for three different jobs. One is free and aimed at marketers, one is a qualitative research suite, and one is a developer debugging tool that happens to record sessions. Picking by price alone is how teams end up with the wrong fit.&lt;/p&gt;

&lt;p&gt;This comparison is for SMB marketers, product owners, and developers deciding where to invest in behavior analytics in 2026 — what each tool is actually for, real pricing (including a major change to Hotjar), retention and privacy trade-offs, and a clear framework so you choose by use case rather than by a feature list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answer: which one to use
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Microsoft Clarity&lt;/strong&gt; is the default for most teams: it is genuinely free with unlimited sessions, strong heatmaps, and AI summaries — start here unless you have a specific reason not to. &lt;strong&gt;Hotjar&lt;/strong&gt; earns its price when you need the qualitative layer Clarity lacks: surveys, feedback widgets, funnels, and 365-day retention. &lt;strong&gt;LogRocket&lt;/strong&gt; is for engineering teams that need to debug — it captures console logs, network requests, and JavaScript errors alongside the replay. Pick Clarity for free behavior data, Hotjar to understand the "why," and LogRocket to fix the "what broke."&lt;/p&gt;

&lt;h2&gt;
  
  
  What each tool is built for
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Microsoft Clarity — free behavior analytics
&lt;/h3&gt;

&lt;p&gt;Clarity is a 100% free session-recording and heatmap tool with no paid tier and no session caps. Beyond standard click and scroll maps, it includes two diagnostics competitors charge for: &lt;strong&gt;dead-click heatmaps&lt;/strong&gt; (clicks on things that are not interactive) and &lt;strong&gt;error-click heatmaps&lt;/strong&gt; (clicks that trigger JavaScript errors), which are gold for spotting broken UI. In 2026 it also bakes in Copilot AI to summarise sessions, plus a native GA4 integration. It pairs naturally with your &lt;a href="https://trackstack.tech/en/ga4-website-basic-setup-10-common-mistakes/" rel="noopener noreferrer"&gt;basic GA4 setup&lt;/a&gt; as the qualitative half of the picture.&lt;/p&gt;

&lt;h3&gt;
  
  
  Hotjar — the qualitative UX suite
&lt;/h3&gt;

&lt;p&gt;Hotjar pairs heatmaps and recordings with the tools that explain behaviour: on-page surveys, feedback widgets, user interviews, and conversion funnels. It also adds move maps (tracking mouse hover, which correlates with attention) and automatic frustration and engagement scoring so you can skip to the recordings that matter. One important 2026 change: Hotjar officially merged into Contentsquare on &lt;strong&gt;July 1, 2025&lt;/strong&gt;, so its pricing page now redirects there and the product is being folded into Contentsquare's modules.&lt;/p&gt;

&lt;h3&gt;
  
  
  LogRocket — developer debugging
&lt;/h3&gt;

&lt;p&gt;LogRocket records sessions, but its real job is engineering. It captures console logs, network requests, JavaScript errors, and application state, so a developer can replay exactly what happened before a bug and connect a UX issue straight to a stack trace. It is the tool of choice when your engineers own support escalations and debugging time is the bottleneck — and it tends to overlap with performance work like &lt;a href="https://trackstack.tech/en/core-web-vitals-2026-what-really-matters-and-how-to-fix-it-fast/" rel="noopener noreferrer"&gt;Core Web Vitals&lt;/a&gt; rather than marketing CRO.&lt;/p&gt;

&lt;h2&gt;
  
  
  2026 pricing
&lt;/h2&gt;

&lt;p&gt;The pricing gap here is the widest in the category — from completely free to enterprise quotes. Because of the Contentsquare transition and LogRocket's tiering, verify current numbers before committing; the figures below reflect mid-2026.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Microsoft Clarity&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; $0 — unlimited sessions, recordings, and heatmaps, no caps, no credit card&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paid tiers:&lt;/strong&gt; none — there is no "Clarity Pro"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That genuinely-free model is unusual in a category where "free" normally means a few hundred sessions before a paywall. Clarity's only real ceiling is retention and feature depth, not volume — you will never get an overage bill.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hotjar (now Contentsquare)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; $0 — the new Contentsquare free plan offers around 5,000 monthly sessions with no sampling (a big upgrade from the old 35-sessions-per-day cap)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paid:&lt;/strong&gt; from roughly $32–$49/month depending on plan and session volume, with 365-day data retention on all plans&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Higher tiers:&lt;/strong&gt; scale to unlimited sessions with sampling, into the ~$171/month range&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;LogRocket&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; $0 — around 1,000 sessions per month&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team / Developer:&lt;/strong&gt; roughly $69–$99/month for about 10,000 sessions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Higher tiers:&lt;/strong&gt; around $349/month for 50,000 sessions; AI error context (Galileo) sits on the upper plans&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One pricing nuance that bites: LogRocket and most paid tools are "always-on," so every visit counts against quota. On a high-traffic site a 10,000-session plan can be exhausted in days, while Clarity simply never charges. Count cost per thousand sessions against your real traffic, not the monthly headline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Feature comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Criterion&lt;/th&gt;
&lt;th&gt;Clarity&lt;/th&gt;
&lt;th&gt;Hotjar&lt;/th&gt;
&lt;th&gt;LogRocket&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Price&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;Free + from ~$32/mo&lt;/td&gt;
&lt;td&gt;Free + from ~$69/mo&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Session limit&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Unlimited&lt;/td&gt;
&lt;td&gt;~5,000/mo free&lt;/td&gt;
&lt;td&gt;~1,000/mo free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Data retention&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;~30 days&lt;/td&gt;
&lt;td&gt;365 days&lt;/td&gt;
&lt;td&gt;Plan-dependent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Surveys / feedback&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Dev tooling (errors, network)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Basic JS errors&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Full (console, network, state)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AI&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Copilot summaries&lt;/td&gt;
&lt;td&gt;In Contentsquare&lt;/td&gt;
&lt;td&gt;Galileo (higher tiers)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Best for&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Free behaviour data&lt;/td&gt;
&lt;td&gt;UX research, the "why"&lt;/td&gt;
&lt;td&gt;Engineering debugging&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Real-world scenarios
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Fixing a leaking checkout.&lt;/strong&gt; If customers abandon at checkout, Clarity's free recordings and dead-click maps will show you where they get stuck — for nothing. Watch ten sessions of the checkout flow and the friction is usually obvious. Dead-click maps in particular reveal when users tap something that looks clickable but is not — a common hidden cause of checkout drop-off that standard analytics never surfaces.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Understanding why a landing page underperforms.&lt;/strong&gt; When a page gets traffic but no conversions, heatmaps tell you what people do, not why. Hotjar's on-page survey ("What stopped you signing up today?") plus its move maps close that gap. This is where paying for Hotjar earns its keep.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reproducing a customer-reported bug.&lt;/strong&gt; When support says "a user couldn't submit the form and saw an error," marketing tools cannot help. LogRocket lets a developer replay that exact session with the console errors and failed network calls visible inline, turning a vague report into a reproducible bug. The rule of thumb: if the person who will watch the replay is a developer, LogRocket pays off; if it is a marketer or designer, Clarity or Hotjar will tell them what they need without the price tag.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest limitations
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Where Clarity falls short.&lt;/strong&gt; Recordings are typically retained only about 30 days, so long-term trend analysis is out. It has no surveys, feedback widgets, or funnels, and you cannot look up a session by a customer's email or name — only non-identifying custom tags. The biggest catch behind "free": Microsoft reserves the right to use your aggregated, anonymised data to improve its own products and AI, which can be a non-starter for healthcare, finance, or government teams.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where Hotjar falls short.&lt;/strong&gt; Cost climbs as traffic grows, and the Contentsquare merger has made the product and pricing feel less simple than the old "install a script and see heatmaps by the afternoon" Hotjar. It is web-only with no native mobile SDK, and it offers no developer tooling — no console, network, or error capture.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where LogRocket falls short.&lt;/strong&gt; It is the most expensive and the most complex, and marketers will find it overkill. Its always-on model burns through session quotas fast on high-traffic sites, and the best AI error context sits behind upper tiers. If nobody on your team is going to use the console logs and network traces, you are paying for power you will never touch.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Choose Microsoft Clarity&lt;/strong&gt; if you want free, unlimited behaviour data and can accept 30-day retention and the data-ownership trade-off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Hotjar&lt;/strong&gt; if you need surveys, feedback, funnels, and long retention to understand the "why" behind behaviour.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose LogRocket&lt;/strong&gt; if your engineers own debugging and you need console, network, and error data with each replay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run Clarity plus Hotjar&lt;/strong&gt; if budget allows — many teams use Clarity for unlimited volume and Hotjar for qualitative depth.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid LogRocket&lt;/strong&gt; if you are a marketing-only team; the depth is wasted and the cost is high.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid Clarity&lt;/strong&gt; if your compliance rules forbid sharing behavioural data with a third party.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Hotjar, Microsoft Clarity, and LogRocket are not three versions of the same product — they are a marketing tool, a research suite, and an engineering tool. For most SMBs the smartest starting move is free: install Clarity, watch real sessions, and only add Hotjar when you need to ask users why, or LogRocket when your developers need to debug what broke. Match the tool to the job and you avoid paying for power you will not use. When you are ready to act on what you find, pair these insights with proper &lt;a href="https://trackstack.tech/en/ga4-ecommerce-events-setup-guide/" rel="noopener noreferrer"&gt;GA4 ecommerce events&lt;/a&gt; so the qualitative story and the quantitative numbers finally line up.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is Microsoft Clarity really free?&lt;/strong&gt;&lt;br&gt;
Yes, completely — no paid tier, no session caps, no credit card. The trade-off is data ownership: Microsoft uses aggregated, anonymised Clarity data to improve its own products and AI, and recordings are retained only about 30 days. For most businesses that is acceptable; for strict-governance industries it may not be.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Hotjar still available after the Contentsquare merger?&lt;/strong&gt;&lt;br&gt;
Yes. Hotjar merged into Contentsquare on July 1, 2025, and its pricing page now redirects there, but the product still works. The free plan actually improved to around 5,000 monthly sessions, though the tooling is gradually being folded into Contentsquare's broader modules.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use Clarity and Hotjar together?&lt;/strong&gt;&lt;br&gt;
Yes, and many optimisation teams do. There is no technical conflict running both. A common setup is Clarity on every page for unlimited volume and frustration signals, with Hotjar for surveys, feedback, and deeper qualitative research where it adds the most value.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which tool is best for developers?&lt;/strong&gt;&lt;br&gt;
LogRocket, clearly. It captures console logs, network requests, JavaScript errors, and application state alongside the session replay, so developers can reproduce bugs from a customer report. Clarity surfaces basic JS errors and error-clicks, but it lacks the deep debugging tooling LogRocket provides.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do Clarity or Hotjar slow down my site?&lt;/strong&gt;&lt;br&gt;
Both add a tracking script, so there is a small performance cost, as with any analytics tool. The impact is usually minor, but always-on session recording on heavy pages can add weight — worth checking against your performance budget if page speed is a priority.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the catch with Microsoft Clarity being free?&lt;/strong&gt;&lt;br&gt;
The catch is data and retention, not money. Microsoft funds Clarity as a loss-leader and uses anonymised behavioural data to improve Bing, Edge, and its AI systems, and recordings expire after roughly 30 days. If those terms fit your privacy posture, it is the best free behaviour tool available.&lt;/p&gt;

&lt;p&gt;These three are not really competitors. &lt;strong&gt;Clarity&lt;/strong&gt; is genuinely free (unlimited sessions, heatmaps, dead-click/error-click maps, Copilot summaries) — the default starting point, with ~30-day retention and a data-ownership trade-off. &lt;strong&gt;Hotjar&lt;/strong&gt; (now part of Contentsquare since July 2025) adds the qualitative layer — surveys, feedback, funnels, 365-day retention — from ~$32/mo. &lt;strong&gt;LogRocket&lt;/strong&gt; is a developer tool: console, network, errors, and state alongside the replay, from ~$69/mo and always-on. Start with Clarity, add Hotjar to learn &lt;em&gt;why&lt;/em&gt;, add LogRocket to debug &lt;em&gt;what broke&lt;/em&gt;.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>ux</category>
      <category>webdev</category>
      <category>tools</category>
    </item>
    <item>
      <title>How to Track Form Submissions in GA4 Without Coding (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Mon, 29 Jun 2026 17:32:36 +0000</pubDate>
      <link>https://dev.to/trackstack/how-to-track-form-submissions-in-ga4-without-coding-2026-2ln1</link>
      <guid>https://dev.to/trackstack/how-to-track-form-submissions-in-ga4-without-coding-2026-2ln1</guid>
      <description>&lt;p&gt;Your contact form is probably the most valuable interaction on your site — and the one most likely to be tracked badly or not at all. The good news: you can &lt;strong&gt;track form submissions in GA4&lt;/strong&gt; without writing a single line of code. The catch is that the easiest method is also the least reliable, so picking the right approach for your specific form matters more than the setup itself.&lt;/p&gt;

&lt;p&gt;This guide is for marketers and developers who already have &lt;a href="https://trackstack.tech/en/ga4-website-basic-setup-10-common-mistakes/" rel="noopener noreferrer"&gt;basic GA4 setup&lt;/a&gt; running and want accurate lead data without shipping custom code — four no-code methods, when each works and when it quietly fails, how to turn a tracked submission into a key event, and the pitfalls (double counting, inflated numbers, embedded forms) that wreck most setups.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answer: which no-code method to use
&lt;/h2&gt;

&lt;p&gt;If your form redirects to a thank-you page, track visits to that page — it is the most reliable no-code method. If it does not redirect, use Google Tag Manager: the built-in &lt;strong&gt;Form Submission trigger&lt;/strong&gt; for standard HTML forms, or an &lt;strong&gt;Element Visibility trigger&lt;/strong&gt; on the success message for AJAX forms. GA4's built-in &lt;strong&gt;Enhanced Measurement&lt;/strong&gt; can track forms with zero setup, but it is notoriously unreliable and often inflates numbers, so treat it as a quick test rather than a final solution. Whatever you pick, verify it in DebugView and mark it as a key event.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 4 no-code methods
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Method 1 — Enhanced Measurement (zero setup, big catch)
&lt;/h3&gt;

&lt;p&gt;GA4 can track forms automatically with no tools at all. Go to &lt;strong&gt;Admin → Data Streams → your web stream → Enhanced Measurement&lt;/strong&gt;, open the settings, and toggle on "Form interactions." GA4 then attempts to fire &lt;code&gt;form_start&lt;/code&gt; and &lt;code&gt;form_submit&lt;/code&gt; events on its own.&lt;/p&gt;

&lt;p&gt;The honest reality: this is widely regarded as one of GA4's least reliable features. It only catches standard HTML &lt;code&gt;&amp;lt;form&amp;gt;&lt;/code&gt; elements with native submit behaviour, so it misses most modern AJAX and JavaScript forms — and when it does fire, it frequently over-counts, with some sites reporting thousands of phantom submissions a day. It also fires &lt;code&gt;form_submit&lt;/code&gt; on interactions that are not real submissions, so a single visitor can generate several. Use it for a five-minute sanity check, not as your reporting source.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 2 — thank-you page (the most reliable)
&lt;/h3&gt;

&lt;p&gt;If submitting your form sends users to a dedicated confirmation page, that redirect is the cleanest signal you have. In GTM, create a trigger of type &lt;strong&gt;Page View&lt;/strong&gt; with the condition &lt;code&gt;Page Path equals /thank-you/&lt;/code&gt;, then attach a GA4 Event tag named something like &lt;code&gt;generate_lead&lt;/code&gt;. When the thank-you page loads, the event fires.&lt;/p&gt;

&lt;p&gt;This method needs no understanding of how the form submits, works across every form type, and is the most trustworthy of the four. Its one weakness: anyone reaching that URL directly — via a bookmark, email link, or internal link — counts as a conversion. Make the thank-you page unreachable except by submitting, and the data stays clean. It is the ideal pairing for a &lt;a href="https://trackstack.tech/en/lead-magnet-automated-funnel-structure/" rel="noopener noreferrer"&gt;lead magnet funnel&lt;/a&gt; where the confirmation page already exists. To verify, open GTM Preview, submit the form, confirm the tag fires on the thank-you URL, then check GA4 Realtime.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 3 — GTM Form Submission trigger
&lt;/h3&gt;

&lt;p&gt;For standard forms that do not redirect, GTM has a built-in listener. First enable the &lt;strong&gt;Form built-in variables&lt;/strong&gt; (Variables → Configure → tick the Form group). Then create a trigger of type &lt;strong&gt;Form Submission&lt;/strong&gt;, leave "Check Validation" on so it only fires on successful submits, and target a specific form by Form ID if you have several. Attach your GA4 Event tag and you are done — no code.&lt;/p&gt;

&lt;p&gt;The limitation is real: this listener was designed for old-school forms that POST and reload, so it does not reliably detect AJAX submissions where the page never navigates. If Preview mode shows no &lt;code&gt;gtm.formSubmit&lt;/code&gt; event when you submit, your form is almost certainly AJAX — move to Method 4. When it does work, it is genuinely set-and-forget and captures useful context like the form ID and page automatically.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 4 — Element Visibility for AJAX forms
&lt;/h3&gt;

&lt;p&gt;Most modern forms submit in the background and show an inline "Thanks, we got your message" without reloading. The no-code trick is to track when that success message appears. In GTM, create an &lt;strong&gt;Element Visibility trigger&lt;/strong&gt;, point it at the confirmation element with a CSS selector (for example &lt;code&gt;.form-success&lt;/code&gt;), enable "Observe DOM changes," and fire your GA4 Event tag on it. The message only appears on a genuine submission, so it is a clean signal — just pick a stable selector and test it in Preview first.&lt;/p&gt;

&lt;p&gt;Many form plugins make this even easier by pushing their own dataLayer event on submit, which a GTM Custom Event trigger can catch directly. If your plugin offers a native GA4 or dataLayer integration, that is usually the most robust no-code route of all — let the plugin do the listening for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four methods compared
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Method&lt;/th&gt;
&lt;th&gt;Needs GTM?&lt;/th&gt;
&lt;th&gt;Works on AJAX forms?&lt;/th&gt;
&lt;th&gt;Reliability&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Enhanced Measurement&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Rarely&lt;/td&gt;
&lt;td&gt;Low (often inflated)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Thank-you page&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes (if it redirects)&lt;/td&gt;
&lt;td&gt;Highest&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Form Submission trigger&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Good (standard forms)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Element Visibility&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Good (needs a CSS selector)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Turn the event into a key event
&lt;/h2&gt;

&lt;p&gt;Tracking the event is only half the job — to use it as a conversion, you must promote it. In GA4 go to &lt;strong&gt;Admin → Events&lt;/strong&gt;, find your form event (e.g. &lt;code&gt;generate_lead&lt;/code&gt;), and toggle "Mark as key event." Note the terminology: Google renamed "conversions" to "key events" in March 2024, though they still appear as conversions when imported into Google Ads — the function is identical, only the label changed. (If a colleague asks where conversions went, that is the answer.)&lt;/p&gt;

&lt;p&gt;For sharper reporting, add a &lt;code&gt;value&lt;/code&gt; parameter to the tag so a quote request can be worth more than a newsletter signup — say 100 versus 10 — which feeds straight into ROI calculations.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common pitfalls that wreck your data
&lt;/h2&gt;

&lt;p&gt;Form tracking fails quietly more often than loudly. These are the issues that make your numbers wrong while everything looks fine.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Double counting:&lt;/strong&gt; running Enhanced Measurement form tracking and a custom GTM setup at once fires two events per submission. If you build custom tracking, turn off the Form interactions toggle.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inflated thank-you pages:&lt;/strong&gt; direct visits, bookmarks, and email links to the confirmation URL all count as conversions. Block direct access to that page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Embedded third-party forms:&lt;/strong&gt; HubSpot and Typeform sit in cross-origin iframes that standard triggers cannot read. HubSpot fires a global JavaScript event GTM can catch; Typeform can redirect to a thank-you page on your domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bots and spam:&lt;/strong&gt; automated submissions inflate counts — filter aggressively and sanity-check against reality.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Consent gaps:&lt;/strong&gt; if your cookie banner blocks GA4 before consent, submissions go untracked.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The single best habit is to cross-check monthly. Compare GA4's form event count against the records in your inbox or CRM — if GA4 shows double, you have a duplication problem; if it shows far fewer, tracking is missing submissions. Tracking that worked last month can break silently after a theme, plugin, or layout change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which method should you use?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Thank-you page&lt;/strong&gt; if your form redirects — the most reliable and least fragile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GTM Form Submission trigger&lt;/strong&gt; for standard HTML forms that POST and reload.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Element Visibility&lt;/strong&gt; for AJAX forms with an inline success message.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your form plugin's native integration&lt;/strong&gt; if it offers one — often the most robust no-code option.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enhanced Measurement only&lt;/strong&gt; as a quick test, never as your final reported source of truth.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For most teams the practical answer is a thank-you page where possible and Element Visibility everywhere else. You do not need one method for the whole site — a contact form can use the thank-you page while a pop-up lead magnet uses Element Visibility, as long as event names stay consistent. Once leads are tracked accurately, the natural next step is routing them onward — for example to &lt;a href="https://trackstack.tech/en/website-crm-telegram-integration/" rel="noopener noreferrer"&gt;send leads to your CRM&lt;/a&gt; the moment a form is submitted.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;You do not need a developer to track form submissions in GA4 — you need the right method for how your form behaves. Thank-you page tracking is the most reliable, Element Visibility covers AJAX forms, the GTM Form Submission trigger handles standard ones, and Enhanced Measurement is a quick test at best. Whichever you choose, verify it in DebugView, mark it as a key event, watch for double counting, and cross-check against your CRM every month.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Can I track form submissions in GA4 without Google Tag Manager?&lt;/strong&gt;&lt;br&gt;
Yes, using Enhanced Measurement's Form interactions toggle, which needs no GTM. The trade-off is reliability — it only catches standard HTML forms and often over-counts. For accurate data without GTM, the alternative is a form plugin with a native GA4 integration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why is GA4 not tracking my form submissions?&lt;/strong&gt;&lt;br&gt;
The most common reason is an AJAX form that does not trigger a standard browser submit, so Enhanced Measurement and the GTM Form Submission trigger both miss it. Use an Element Visibility trigger on the success message instead, and confirm in GTM Preview that an event actually fires on submit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why does GA4 show more form submissions than I received?&lt;/strong&gt;&lt;br&gt;
Usually double counting — Enhanced Measurement form tracking running alongside a custom GTM setup, both firing on one submission. Disable the Form interactions toggle if you built your own tracking. Inflated thank-you pages from direct visits and bot spam are the other common causes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do I mark a form submission as a conversion?&lt;/strong&gt;&lt;br&gt;
In GA4, go to Admin → Events, find your form event, and toggle "Mark as key event." Google renamed conversions to key events in 2024, but they still import into Google Ads as conversions. The event must have fired at least once before it appears in the list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I track HubSpot or Typeform forms in GA4?&lt;/strong&gt;&lt;br&gt;
Yes, but not with standard triggers, because they load in cross-origin iframes. HubSpot fires a global JavaScript event that GTM can listen for with a Custom Event trigger. Typeform can redirect to a thank-you page on your own domain, which GA4 then tracks as a page view.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Enhanced Measurement form tracking accurate?&lt;/strong&gt;&lt;br&gt;
Not reliably. It works for basic HTML forms on simple sites but misses AJAX and JavaScript forms and frequently inflates submission counts. For trustworthy data, use a thank-you page or a GTM trigger instead, and disable Enhanced Measurement form tracking to avoid duplicates.&lt;/p&gt;

&lt;p&gt;You can track GA4 form submissions with no code. Four methods: &lt;strong&gt;thank-you page&lt;/strong&gt; (most reliable — fire a GA4 event on the confirmation pageview), &lt;strong&gt;GTM Form Submission trigger&lt;/strong&gt; (standard HTML forms only), &lt;strong&gt;Element Visibility&lt;/strong&gt; (AJAX forms — fire when the success message appears), and &lt;strong&gt;Enhanced Measurement&lt;/strong&gt; (zero setup but unreliable, a quick test at best). Verify in DebugView, mark the event as a key event, don't run Enhanced Measurement alongside custom tracking (double counting), and cross-check GA4 against your CRM monthly.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>ga4</category>
      <category>marketing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>GA4 Custom Dimensions: A Setup Guide with Real Examples (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Sat, 27 Jun 2026 15:51:32 +0000</pubDate>
      <link>https://dev.to/trackstack/ga4-custom-dimensions-a-setup-guide-with-real-examples-2026-pei</link>
      <guid>https://dev.to/trackstack/ga4-custom-dimensions-a-setup-guide-with-real-examples-2026-pei</guid>
      <description>&lt;p&gt;GA4 ships with dozens of built-in dimensions, but the moment you want to report on something specific to your business — which blog category drives signups, which membership tier converts, which product colour sells — you hit the wall. That is where &lt;strong&gt;GA4 custom dimensions&lt;/strong&gt; come in: they let you attach your own data to events and users and make it visible in reports.&lt;/p&gt;

&lt;p&gt;This guide is for marketers and developers who already have &lt;a href="https://trackstack.tech/en/ga4-website-basic-setup-10-common-mistakes/" rel="noopener noreferrer"&gt;basic GA4 setup&lt;/a&gt; running and want to extend it without breaking anything — what custom dimensions really are, the three scopes, the exact 2026 limits, a step-by-step setup with GTM, real examples for each scope, and the mistakes that quietly ruin your data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answer: how custom dimensions work
&lt;/h2&gt;

&lt;p&gt;A custom dimension is two things working together: an event parameter (or user property) you &lt;em&gt;send&lt;/em&gt; from your site, and a registration in GA4 Admin that &lt;em&gt;maps&lt;/em&gt; that parameter to a readable name and a scope. Both halves are required — sending without registering means the data sits invisible in raw collection; registering without sending means an empty dimension. Crucially, registration is not retroactive: data only appears from the moment you register it forward, so set it up before you need the history.&lt;/p&gt;

&lt;h2&gt;
  
  
  What GA4 custom dimensions actually are
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Event parameter vs registered dimension.&lt;/strong&gt; An event parameter is the key-value pair sent with an event at collection time — for example, &lt;code&gt;file_name: "pricing.pdf"&lt;/code&gt; sent with a &lt;code&gt;file_download&lt;/code&gt; event. The parameter is where the data lives. A custom dimension is the registration in GA4 Admin that connects that parameter name to a display label and makes it visible in standard reports, Explorations, and audiences. Without registration, the parameter still exists in raw collection and in the BigQuery export, but it is invisible in the GA4 interface. This split trips people up constantly: they see the parameter in DebugView, assume the job is done, then wonder why it never shows in a report. The two steps are separate by design, and you need both.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The three scopes: event, user, item.&lt;/strong&gt; Scope decides how the value attaches to your data, and choosing wrong is the single most common cause of broken reports.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Event-scoped&lt;/strong&gt; dimensions attach to one event only — the next event from the same user will not inherit the value.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-scoped&lt;/strong&gt; dimensions attach to the user profile and persist across every future event until overwritten — right for stable attributes like subscription tier.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Item-scoped&lt;/strong&gt; dimensions live inside the items array of ecommerce events and describe individual products.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Note that session scope is not available for custom dimensions in GA4. If you genuinely need a value to apply to every event in a session, you have to send it with each event yourself. Getting scope right at the design stage saves hours of debugging, since a mis-scoped dimension fails quietly rather than throwing an error.&lt;/p&gt;

&lt;h2&gt;
  
  
  The limits you must plan around
&lt;/h2&gt;

&lt;p&gt;These limits are per property — not per account or per stream — and easy to hit on a complex setup. One important nuance: deleting an event-scoped dimension frees the slot after a 48-hour wait, but archiving a user-scoped dimension does &lt;strong&gt;not&lt;/strong&gt; free its slot, so the 25 user-scoped definitions are effectively fixed.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Standard property&lt;/th&gt;
&lt;th&gt;Analytics 360&lt;/th&gt;
&lt;th&gt;Notes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Event-scoped&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;50&lt;/td&gt;
&lt;td&gt;125&lt;/td&gt;
&lt;td&gt;Slot frees 48h after deletion&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;User-scoped&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;100&lt;/td&gt;
&lt;td&gt;Archiving does NOT free a slot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Item-scoped&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;Explorations only, not standard reports&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Custom metrics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;50&lt;/td&gt;
&lt;td&gt;125&lt;/td&gt;
&lt;td&gt;Numeric values only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Calculated metrics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Built from numeric metrics&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How to set up a custom dimension, step by step
&lt;/h2&gt;

&lt;p&gt;The order of sending and registering does not strictly matter, but do both at roughly the same time — a gap means missing data for that window.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1 — send the parameter
&lt;/h3&gt;

&lt;p&gt;Push the value into the data layer, then read it into your GA4 event tag in GTM. For a blog where you want to know which category drives engagement:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;dataLayer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;event&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;article_view&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;article_category&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;analytics&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;author_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;editorial&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In GTM, create Data Layer Variables for &lt;code&gt;article_category&lt;/code&gt; and &lt;code&gt;author_name&lt;/code&gt;, then add them as parameters on your GA4 event tag. The parameter name you send must match the name you register exactly — &lt;code&gt;article_category&lt;/code&gt; is not the same as &lt;code&gt;articleCategory&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2 — register it in GA4 Admin
&lt;/h3&gt;

&lt;p&gt;Go to &lt;strong&gt;Admin → Custom definitions → Custom dimensions → Create custom dimension&lt;/strong&gt;. Enter a Dimension name (the readable label in reports, e.g. "Article Category"), pick the Scope (Event), and type the Event parameter name exactly as it arrives (&lt;code&gt;article_category&lt;/code&gt;). Save. That registration tells GA4 — and connected tools like Looker Studio — to expect the parameter and surface it as a dimension.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3 — verify in DebugView, then wait
&lt;/h3&gt;

&lt;p&gt;Before trusting anything, open DebugView and confirm the parameter is arriving with the right value on the right event. A common agency mistake is registering a dimension before confirming the event actually fires. Once verified, data takes 24–48 hours to populate in standard reports — DebugView is immediate, reports are not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real examples by scope
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Event-scoped: content category and form name
&lt;/h3&gt;

&lt;p&gt;Event-scoped is right for data that describes a single action. Sending &lt;code&gt;article_category&lt;/code&gt; on an &lt;code&gt;article_view&lt;/code&gt; lets you see which topics drive engagement. Sending &lt;code&gt;form_name&lt;/code&gt; on a &lt;code&gt;form_submit&lt;/code&gt; lets you compare your newsletter form against your contact form. Both describe that one interaction and should not persist — which is exactly what event scope does.&lt;/p&gt;

&lt;h3&gt;
  
  
  User-scoped: membership tier
&lt;/h3&gt;

&lt;p&gt;For stable attributes that should follow the user everywhere, use a user property. Set it on the first event after login, when you have the identity context:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nf"&gt;gtag&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;set&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;user_properties&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;membership_tier&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;premium&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now every subsequent event — page views, purchases, conversions — carries &lt;code&gt;membership_tier&lt;/code&gt;, so you can segment any report by plan. The classic mistake is sending this as an event parameter on the login event only, which leaves every later event blank.&lt;/p&gt;

&lt;h3&gt;
  
  
  Item-scoped: product attributes
&lt;/h3&gt;

&lt;p&gt;Item scope answers product-level questions like revenue per colour or margin tier. The custom parameters go inside each object in the items array of an ecommerce event:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;dataLayer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;event&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;add_to_cart&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;ecommerce&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;items&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt;
      &lt;span class="na"&gt;item_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;SKU_12345&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;item_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Running Shoes&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;item_color&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;blue&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;margin_tier&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;high&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
    &lt;span class="p"&gt;}]&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Remember that item-scoped dimensions only appear in Explorations, not standard reports. If you are wiring up ecommerce tracking from scratch, the &lt;a href="https://trackstack.tech/en/ga4-ecommerce-events-setup-guide/" rel="noopener noreferrer"&gt;GA4 ecommerce events&lt;/a&gt; guide covers the full items array first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes that silently break your data
&lt;/h2&gt;

&lt;p&gt;The most dangerous mistakes produce no error — your dimension just stays empty or wrong while you assume it works.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Wrong scope:&lt;/strong&gt; event scope for something stable like membership tier (data only on one event), or user scope for something transient like a search term (every future event inherits the wrong value).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Name mismatch:&lt;/strong&gt; the registered name and the sent parameter must be identical, character for character.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Passing PII:&lt;/strong&gt; never send emails, phone numbers, or names as dimension values — it violates Google's Terms and can get your property permanently deleted.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High cardinality:&lt;/strong&gt; dimensions with thousands of unique values (full URLs, user IDs, timestamps) overflow into an aggregated &lt;code&gt;(other)&lt;/code&gt; row and become useless — keep values to a bounded set of categories.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hoarding slots:&lt;/strong&gt; registering every parameter you ever send. Audit quarterly and retire anything not queried in 90 days.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also remember the 100-character value limit (with a few exceptions like &lt;code&gt;page_location&lt;/code&gt; at 1,000), and that raw exports keep everything regardless — so if you need full history or unregistered fields, lean on BigQuery or &lt;a href="https://trackstack.tech/en/server-side-tracking-when-needed-what-it-costs/" rel="noopener noreferrer"&gt;server-side tracking&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which scope should you use?
&lt;/h2&gt;

&lt;p&gt;Work backwards from the question you want to answer rather than from the data you happen to have. If the answer is "per action," reach for event scope; "per person," user scope; "per product," item scope.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Event scope&lt;/strong&gt; — the value describes a single action: content category, button label, form name, video title.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User scope&lt;/strong&gt; — the value is a stable trait of the person: subscription tier, customer type, company size, signup source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Item scope&lt;/strong&gt; — the value describes a product inside an ecommerce event: colour, size, brand, margin tier.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custom metric instead&lt;/strong&gt; — the value is numeric and you want to sum or average it: loyalty points, scores, credits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing&lt;/strong&gt; — if GA4 already captures it; check the built-in dimensions before spending a slot.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Custom dimensions are what turn GA4 from a generic report into a tool that answers your specific questions — but only if you get the fundamentals right. Send the parameter and register it together, pick the scope deliberately, respect the per-property limits, verify in DebugView, and never pass PII. Start with two or three high-value dimensions rather than registering everything, keep a small register of what each one is for, and audit quarterly.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Are GA4 custom dimensions retroactive?&lt;/strong&gt;&lt;br&gt;
No. Data only appears from the moment you register the dimension forward — there is no backfill. If you send a parameter for a week before registering it, reports will miss that week. Raw data streamed to BigQuery keeps the parameter regardless.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the difference between an event parameter and a custom dimension?&lt;/strong&gt;&lt;br&gt;
The parameter is the key-value data sent with an event at collection time. The custom dimension is the GA4 Admin registration that maps that parameter to a readable name and scope, making it visible in reports. Without registration the parameter exists in raw data but not in the GA4 interface.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How many custom dimensions can I create?&lt;/strong&gt;&lt;br&gt;
On a standard property: 50 event-scoped, 25 user-scoped, 10 item-scoped, plus 50 custom metrics, all per property. Analytics 360 raises these to 125, 100, and 25. Deleting an event-scoped dimension frees its slot after 48 hours; archiving a user-scoped one does not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why is my custom dimension showing no data?&lt;/strong&gt;&lt;br&gt;
Usually one of three reasons: the parameter name does not match the registered name exactly, the event is not actually firing (check DebugView), or you registered it less than 24–48 hours ago. Item-scoped dimensions also only show in Explorations, not standard reports.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Should membership tier be event-scoped or user-scoped?&lt;/strong&gt;&lt;br&gt;
User-scoped. It is a stable attribute that should follow the user across every event, so set it as a user property after login. As an event parameter on the login event only, it will be blank on all later events.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I send personal data as a custom dimension?&lt;/strong&gt;&lt;br&gt;
No. Passing emails, phone numbers, full names, or other PII violates Google's Terms of Service and can result in your property being permanently deleted. Use non-identifying values like tiers, categories, or hashed identifiers.&lt;/p&gt;

&lt;p&gt;A GA4 custom dimension = an event parameter (or user property) you send + a registration in GA4 Admin that maps it to a name and scope. Both are required, and registration is not retroactive (no backfill). Pick scope by the question: per action → event, per person → user, per product → item. Limits per property: 50 event / 25 user / 10 item / 50 metrics — and archiving a user-scoped one never frees the slot. Match parameter names exactly, verify in DebugView, wait 24–48h, and never send PII.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>ga4</category>
      <category>googleanalytics</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Coda vs Notion: Which Is Better for Your Workspace? (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Wed, 24 Jun 2026 04:42:42 +0000</pubDate>
      <link>https://dev.to/trackstack/coda-vs-notion-which-is-better-for-your-workspace-2026-3mfi</link>
      <guid>https://dev.to/trackstack/coda-vs-notion-which-is-better-for-your-workspace-2026-3mfi</guid>
      <description>&lt;p&gt;Both Coda and Notion promise the same thing — one workspace to replace your wiki, project tracker, and lightweight database — but they get there from opposite directions. Notion is document-first: everything is a block on a page, and you build outward. Coda is app-first: every doc can behave like a small application, with spreadsheet-grade formulas and automations baked in. The label "all-in-one workspace" hides a real fork in the road.&lt;/p&gt;

&lt;p&gt;This &lt;strong&gt;Coda vs Notion&lt;/strong&gt; comparison is for SMB teams and operators deciding where to centralise their work in 2026 — the genuine difference in philosophy, the pricing models that can swing your annual bill by thousands, where each wins and frustrates, and a clear framework for choosing (including the team-structure question most comparisons skip).&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answer: Coda or Notion?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Notion&lt;/strong&gt; is the better default for most teams: easier to learn, document-first, stronger AI agents, native offline support, and a vast template ecosystem. &lt;strong&gt;Coda&lt;/strong&gt; wins when you need spreadsheet-grade formulas, app-like automation, and — crucially — when you have many content consumers but few creators, because its maker billing only charges the people who build docs. Pick Notion for clarity, writing, and fast adoption; pick Coda for logic, automation, and real cost savings on consumer-heavy teams.&lt;/p&gt;

&lt;h2&gt;
  
  
  The core difference: documents vs applications
&lt;/h2&gt;

&lt;p&gt;Before pricing or features, understand the philosophy, because it shapes everything else. Notion wants documents that are easy and forgiving; Coda wants documents that behave like software. It comes down to a simple question: do you need a document you read and edit, or a document that calculates and does things for you? Confusing those two needs is the main reason teams pick the wrong tool and migrate six months later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Notion is built for.&lt;/strong&gt; Notion treats the page as the unit. You drag text, headings, databases, and embeds into any layout, and most people are productive within 15 minutes. It is strongest as a knowledge hub — wikis, notes, and lightweight databases — and shines when documentation and tasks live together; if your main goal is a searchable &lt;a href="https://trackstack.tech/en/company-knowledge-base-structure-access-search/" rel="noopener noreferrer"&gt;internal knowledge base&lt;/a&gt;, it is the natural fit. Its permission system is granular (five levels from full access to comment-only), so you can protect a table's structure while still letting people add rows. Founded in 2013, it has had years to polish the editing experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Coda is built for.&lt;/strong&gt; Coda treats the doc as a programmable surface. Its tables are full spreadsheets with a formula engine that rivals Excel (IF, VLOOKUP, SUMIF), plus buttons that trigger automations and Packs that sync two-way with tools like Slack, Jira, and Google Calendar. It also includes native time tracking, which Notion lacks. The payoff is power; the price is a steeper learning curve of 30–60 minutes. Coda also offers unlimited guest access by email on paid tiers, where Notion caps guests at 100 on Plus and 250 on Business — useful for agencies juggling many clients.&lt;/p&gt;

&lt;h2&gt;
  
  
  2026 pricing: the maker-billing story
&lt;/h2&gt;

&lt;p&gt;Pricing is the single biggest practical difference, and it is not about the sticker price — it is about who pays. Notion charges per seat: every user costs the same whether they write or only read. Coda uses maker billing: only Doc Makers (people who create docs) pay, while editors and viewers are free. That structural gap can swing a large team's annual bill by a five-figure number.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Notion&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; unlimited pages for individuals; block limits for 2+ member workspaces; 5MB file uploads&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plus:&lt;/strong&gt; $10/user/month annual ($12 monthly)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business:&lt;/strong&gt; $20/user/month annual ($24 monthly) — includes full Notion AI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enterprise:&lt;/strong&gt; custom — SAML SSO, SCIM, advanced controls&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Notion AI is now bundled into paid plans rather than a separate add-on, with a credit pool per plan. The catch: full AI sits on the Business tier, so unlocking it means upgrading every seat.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Coda&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; unlimited docs, tables, and automations, but with object/row caps per doc&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pro:&lt;/strong&gt; $10/Doc Maker/month annual — unlimited free editors, 2,000 AI credits per maker&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team:&lt;/strong&gt; $30/Doc Maker/month annual — advanced admin, 6,000 AI credits&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enterprise:&lt;/strong&gt; custom&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Which is actually cheaper.&lt;/strong&gt; Count your builders versus consumers. If everyone creates docs, Notion is usually cheaper — Business at $20 beats Coda Team at $30 per maker. But if a few build and many only read, Coda wins big: a 100-person company with 15 Doc Makers pays roughly $450/month on Coda Team versus about $2,000/month for Notion Business at the same headcount. Coda reports teams saving up to 78% when only a fraction create docs. Watch for "maker creep," though — depending on setup, someone who just wants to add a table row may need maker status.&lt;/p&gt;

&lt;h2&gt;
  
  
  Feature comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Criterion&lt;/th&gt;
&lt;th&gt;Notion&lt;/th&gt;
&lt;th&gt;Coda&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Approach&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Document-first&lt;/td&gt;
&lt;td&gt;App-like / formula-driven&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Billing model&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Per user (all pay)&lt;/td&gt;
&lt;td&gt;Per Doc Maker (editors free)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Entry paid price&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;$10/user/mo&lt;/td&gt;
&lt;td&gt;$10/maker/mo&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Formulas / automation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Basic&lt;/td&gt;
&lt;td&gt;Spreadsheet-grade, strong&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Ease of adoption&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;~15 min&lt;/td&gt;
&lt;td&gt;30–60 min learning curve&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AI&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Agents, bundled in plans&lt;/td&gt;
&lt;td&gt;Included for makers (credits)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Offline support&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (desktop)&lt;/td&gt;
&lt;td&gt;Limited (web-first)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When to choose each
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Choose Notion for knowledge and writing.&lt;/strong&gt; A team maintaining handbooks, onboarding guides, meeting notes, and a wiki is better served by Notion. Its editor is more pleasant for long-form writing, adoption is fast, and the template ecosystem covers nearly every workflow — it is also the easier base for &lt;a href="https://trackstack.tech/en/how-to-use-notion-as-a-lightweight-crm-2026-step-by-step/" rel="noopener noreferrer"&gt;running Notion as a lightweight CRM&lt;/a&gt; without much setup.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose Coda for interactive, data-rich systems.&lt;/strong&gt; If your documentation needs to calculate, automate, or behave like an app — live dashboards, OKR systems, approval flows, or API docs with automated changelogs — Coda does things Notion cannot. A practical test: if the same content would work as a static page, Notion is enough; if it needs to react to data (recalculating a metric, flipping a status, notifying Slack when a field changes), that is where Coda earns its complexity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose by team structure and budget.&lt;/strong&gt; This is the deciding factor many people miss. A large team with a handful of builders and a wide circle of viewers should lean Coda for the maker-billing savings. A team where everyone creates content should lean Notion, where flat per-seat pricing is simpler and often cheaper.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest limitations
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Where Notion frustrates.&lt;/strong&gt; Its flexibility invites over-engineering — teams build sprawling, messy workspaces. Its formulas are basic next to Coda's, deeper automation leans on third-party tools like Zapier, and performance degrades past roughly 10 concurrent editors on one page. Full AI also requires the Business tier across every seat. Search gets harder as the workspace grows into hundreds of pages, and without discipline the wiki becomes a place where everything exists but nothing is findable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where Coda frustrates.&lt;/strong&gt; Its power comes with complexity; non-technical teammates often need tutorials before they are productive. Offline support is limited because the app is web-first, and the free plan's per-doc object caps bite quickly. There is also a strategic question: Coda is now owned by Superhuman (formerly Grammarly), and its AI roadmap has folded into that suite — a different priority list than picking Coda standalone, which makes betting on a specific future feature riskier than with Notion's single roadmap.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose: a simple framework
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Choose Notion&lt;/strong&gt; for a polished knowledge hub, easy adoption, strong AI agents, and offline access.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Coda&lt;/strong&gt; for spreadsheet-grade formulas, app-like automation, native time tracking, or cross-doc logic.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Coda&lt;/strong&gt; if you have many viewers and few creators — maker billing saves significantly at scale.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Notion&lt;/strong&gt; if everyone on the team creates content, since flat per-seat pricing is simpler and often cheaper.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid Coda&lt;/strong&gt; if your team is non-technical and needs fast, frictionless adoption.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid Notion&lt;/strong&gt; if your core need is interactive, calculation-heavy documents rather than writing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Coda versus Notion is not a contest with one winner — it is a choice between two philosophies. Notion is better for clarity, writing, and rapid adoption, and it is the safer default for most teams. Coda is better for automation, structure, and system-building, and its maker billing makes it dramatically cheaper for teams with many consumers and few creators. The smartest move is the oldest one: build a real workflow in each on the free plan, count your builders versus consumers, and pick the tool that fits how your team actually works. (If AI is central to that decision, it is worth weighing &lt;a href="https://trackstack.tech/en/notion-ai-vs-chatgpt-note-taking-2026/" rel="noopener noreferrer"&gt;Notion AI vs ChatGPT&lt;/a&gt; separately too.)&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is Coda cheaper than Notion?&lt;/strong&gt;&lt;br&gt;
It depends on team structure. Coda only charges Doc Makers, so if you have many viewers and few creators, it is much cheaper — sometimes 50–80% less. But if everyone creates documents, Notion's flat per-seat pricing usually wins, with Business at $20 undercutting Coda Team at $30 per maker.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Notion or Coda easier to learn?&lt;/strong&gt;&lt;br&gt;
Notion, clearly. Its block-based editor and huge template library get most users productive within 15 minutes. Coda is more powerful but demands a 30–60 minute investment in tables, Packs, and formulas before it feels comfortable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Coda have better automation than Notion?&lt;/strong&gt;&lt;br&gt;
Yes. Coda has spreadsheet-grade formulas, in-doc buttons, and Packs with real two-way sync, so documents can act like applications. Notion's formulas are more basic and deeper automation usually relies on third-party tools like Zapier.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which has better AI in 2026?&lt;/strong&gt;&lt;br&gt;
Notion has the more coherent AI story: AI is bundled across paid plans and now includes agents that run multi-step actions across connected tools. Coda AI inside the doc is excellent for formula and data work, but its broader AI roadmap has shifted into the Superhuman suite after the acquisition.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use either tool for personal productivity?&lt;/strong&gt;&lt;br&gt;
Both work, but Notion is the better personal pick for notes, task tracking, and a "second brain," thanks to its simplicity and template ecosystem. Coda can work personally for advanced databases or mini-apps, but it is often overkill for simple personal workflows.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does Notion or Coda work offline?&lt;/strong&gt;&lt;br&gt;
Notion has a desktop app with offline support, so you can view and edit cached pages without internet. Coda is web-first with limited offline capability, which makes Notion the better choice for people who travel or work with unreliable connectivity.&lt;/p&gt;

&lt;p&gt;Notion is document-first and billed per seat; Coda is app-first (spreadsheet-grade formulas, automations, Packs) and billed per Doc Maker, with editors and viewers free. Notion wins on ease, AI agents, offline, and templates — the safer default. Coda wins on formulas, automation, and cost when you have many consumers and few creators (up to ~78% cheaper at scale). Count builders vs consumers, trial both free, and pick by team structure — not by which logo you know.&lt;/p&gt;

</description>
      <category>notion</category>
      <category>productivity</category>
      <category>tools</category>
      <category>nocode</category>
    </item>
    <item>
      <title>Loom vs Zoom: When to Use Asynchronous Video (2026)</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Wed, 17 Jun 2026 13:29:01 +0000</pubDate>
      <link>https://dev.to/trackstack/loom-vs-zoom-when-to-use-asynchronous-video-2026-20no</link>
      <guid>https://dev.to/trackstack/loom-vs-zoom-when-to-use-asynchronous-video-2026-20no</guid>
      <description>&lt;p&gt;Half the meetings on a calendar could have been a recorded video, and half the recorded videos teams send could have been a paragraph of text. The trick is knowing which is which. &lt;strong&gt;Loom&lt;/strong&gt; and &lt;strong&gt;Zoom&lt;/strong&gt; get compared as if they were rivals, but they solve opposite problems: Loom is asynchronous — record once, watched whenever — while Zoom is synchronous, everyone present at the same time. The real question is not which tool is better; it is when each mode of communication is the right one.&lt;/p&gt;

&lt;p&gt;This is for SMB owners, team leads, and remote-first managers trying to cut meeting bloat without losing the conversations that genuinely need to be live. Below: real 2026 pricing for both, the scenarios where each shines, the honest downsides of each, and a simple framework for choosing between a message, a recording, and a meeting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick answer: Loom or Zoom?
&lt;/h2&gt;

&lt;p&gt;Use &lt;strong&gt;Loom&lt;/strong&gt; when information flows one way and timing does not matter — status updates, walkthroughs, onboarding, code or design reviews, client explainers. The viewer watches on their own schedule, at their own speed, and nobody hunts for a slot on three calendars. Use &lt;strong&gt;Zoom&lt;/strong&gt; when real-time back-and-forth is required: brainstorming, negotiation, sensitive conversations, interviews, or any decision that needs live debate.&lt;/p&gt;

&lt;p&gt;In short: Loom replaces the meeting that should not exist; Zoom protects the meeting that should. Most teams need both, and the money question is smaller than it looks because Loom charges per recorder while Zoom charges per host.&lt;/p&gt;

&lt;h2&gt;
  
  
  Async vs sync: the distinction that actually matters
&lt;/h2&gt;

&lt;p&gt;Before comparing features, get the mental model right. Synchronous communication is expensive because it costs everyone the same hour at the same time. Asynchronous communication is cheap because each person spends their own time when it suits them. The skill is matching the channel to the message, not defaulting to a meeting out of habit.&lt;/p&gt;

&lt;p&gt;A practical rule: if someone needs to decide something &lt;em&gt;together, right now&lt;/em&gt;, that is sync. If they can react in an hour or tomorrow, that is async — and a recording or text will beat a call.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Loom is built for
&lt;/h3&gt;

&lt;p&gt;Loom is a video messaging tool acquired by Atlassian in 2023. You record your screen and camera, it generates a shareable link instantly, and the recipient watches without an account. It is ideal for "let me show you" moments — clumsy in text, but not worth a live call. Recordings become a searchable library, which quietly turns Loom into part of an &lt;a href="https://trackstack.tech/en/company-knowledge-base-structure-access-search/" rel="noopener noreferrer"&gt;internal knowledge base&lt;/a&gt; rather than a one-off.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Zoom is built for
&lt;/h3&gt;

&lt;p&gt;Zoom is the default for live video — meetings, webinars, interviews, real-time collaboration. Its strength is presence: reading reactions, interrupting, deciding together in one sitting. If you are weighing it against other live tools, trackstack.tech has a deeper &lt;a href="https://trackstack.tech/en/zoom-vs-google-meet-vs-teams-comparison/" rel="noopener noreferrer"&gt;Zoom vs Google Meet vs Teams&lt;/a&gt; breakdown. For anything that needs genuine dialogue, async video is a poor substitute and Zoom is the right call.&lt;/p&gt;

&lt;h2&gt;
  
  
  2026 pricing, plan by plan
&lt;/h2&gt;

&lt;p&gt;The pricing models are structurally different, and that difference often decides the budget more than the per-seat number. Loom charges per &lt;em&gt;Creator&lt;/em&gt; — the people who record — and viewers are free forever. Zoom charges per host license. A team where one person records explainers for forty viewers pays very differently across the two.&lt;/p&gt;

&lt;h3&gt;
  
  
  Loom pricing in 2026
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Starter (Free):&lt;/strong&gt; $0 — up to 25 videos per creator, 5-minute cap per video, 720p&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business:&lt;/strong&gt; $15/creator/month annual (or $18 monthly) — unlimited videos and length, up to 4K, remove Loom branding, viewer analytics&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business + AI:&lt;/strong&gt; $20/creator/month annual (or $24 monthly) — AI titles, summaries, chapters, filler-word and silence removal, edit by transcript&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enterprise:&lt;/strong&gt; custom — SSO (SAML), SCIM, advanced retention, Salesforce integration, 99.95% SLA&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The key cost lever: only recorders need a seat. If two of five teammates record regularly, you pay for two creators (about $360/year on Business annual) while the rest watch free. That viewer-free model is what makes Loom cheap for outbound explainers and expensive only when everyone records.&lt;/p&gt;

&lt;h3&gt;
  
  
  Zoom pricing in 2026
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Basic (Free):&lt;/strong&gt; $0 — unlimited 1:1 meetings, group meetings capped at 40 minutes, up to 100 participants, no cloud recording&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pro:&lt;/strong&gt; $13.33/user/month annual (or $16.99 monthly) — 30-hour meetings, 100 participants, 10GB cloud storage, AI Companion&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business:&lt;/strong&gt; $18.33/user/month annual (or $21.99 monthly) — 300 participants, SSO, managed domains, recording transcripts, 10-seat minimum&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business Plus:&lt;/strong&gt; $29/user/month — bundles Zoom Phone&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enterprise:&lt;/strong&gt; custom pricing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The famous gate is the 40-minute cap on free group meetings — the single most common reason teams upgrade to Pro. Watch the cloud-storage trap too: recordings pile up, and once you exceed the included allowance Zoom charges roughly $10/month per extra 30GB, billed every month the files stay there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Feature comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Criterion&lt;/th&gt;
&lt;th&gt;Loom (async)&lt;/th&gt;
&lt;th&gt;Zoom (sync)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Communication mode&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;One-way, watch anytime&lt;/td&gt;
&lt;td&gt;Real-time, everyone present&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Billing model&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Per creator (viewers free)&lt;/td&gt;
&lt;td&gt;Per host license&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Entry paid price&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;$15/creator/mo&lt;/td&gt;
&lt;td&gt;$13.33/user/mo&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free tier limit&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;25 videos, 5-min cap&lt;/td&gt;
&lt;td&gt;40-min group meetings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Scheduling needed&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Yes (calendars align)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Timezone-friendly&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Excellent&lt;/td&gt;
&lt;td&gt;Poor across wide gaps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Best for&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Walkthroughs, updates, reviews&lt;/td&gt;
&lt;td&gt;Debate, decisions, sensitive talks&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  When async video wins (reach for Loom)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Onboarding and repeatable training.&lt;/strong&gt; Record the setup walkthrough once and every new hire watches it on day one — no repeated live sessions. Pair recordings with written docs and a &lt;a href="https://trackstack.tech/en/task-management-system-priorities-sla-templates/" rel="noopener noreferrer"&gt;task management system&lt;/a&gt; so onboarding has both the "how" on video and the checklist to follow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code, design, and document review.&lt;/strong&gt; Talking through a pull request or a mockup while pointing at the screen carries nuance that inline comments lose, and the author watches when they reach that task rather than dropping everything for a call. This fits how &lt;a href="https://trackstack.tech/en/jira-vs-clickup-vs-asana-dev-teams/" rel="noopener noreferrer"&gt;dev teams run their workflow&lt;/a&gt;, where context matters but interrupt-driven meetings kill focus.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Async standups across timezones.&lt;/strong&gt; For a team split across five hours of timezone gap, a daily live standup is a tax on someone. A 90-second recorded update each morning keeps everyone informed without forcing anyone awake at an awkward hour — a core habit for &lt;a href="https://trackstack.tech/en/best-project-management-tools-remote-teams-2026/" rel="noopener noreferrer"&gt;remote teams&lt;/a&gt; that run distributed by design.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Client explainers and sales follow-ups.&lt;/strong&gt; A personalised two-minute walkthrough sent to a prospect lands better than another email and needs no booked call. Because viewers do not need a Loom account, this is genuinely frictionless for outbound — one of the clearest wins of per-creator pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a live call wins (reach for Zoom)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Decisions that need real debate.&lt;/strong&gt; When a topic has competing opinions and trade-offs to resolve, the back-and-forth of a live call reaches a conclusion in twenty minutes that a thread of recordings would drag out over two days. Branching discussions need interruption, and async cannot interrupt.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sensitive or high-stakes conversations.&lt;/strong&gt; Feedback, conflict, negotiation, and anything emotionally loaded belongs live. A recording cannot read the room or adjust mid-sentence when someone reacts. Sending a difficult message as a one-way video usually makes it worse, not faster.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Interviews, kickoffs, and relationship-building.&lt;/strong&gt; First meetings, hiring interviews, and project kickoffs benefit from rapport that only happens live. These are the moments where presence is the point, and trimming them to async saves time nobody wanted to save.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest limitations
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Where Loom frustrates.&lt;/strong&gt; Async has no immediacy — if you need an answer now, a recording is the wrong tool. Loom also tempts overuse: people record three-minute videos for things a two-line message would settle, which just moves the bloat from meetings to playback. And the per-creator cost climbs once the whole team records regularly, so it is not automatically the cheap option.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where Zoom frustrates.&lt;/strong&gt; Meeting fatigue is real, scheduling across timezones is constant friction, and the 40-minute free cap nudges you to pay quickly. Cloud-recording storage costs creep up if you record often, and a calendar packed with calls that should have been recordings is the exact problem async video exists to fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to choose: the escalation ladder
&lt;/h2&gt;

&lt;p&gt;Default to the lightest channel that does the job, and only escalate when it genuinely needs more:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Text first&lt;/strong&gt; — if it fits in a few lines and needs no visuals, send a message, not a video.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Loom (async video) next&lt;/strong&gt; — when you need to &lt;em&gt;show&lt;/em&gt; something, explain a process, or add tone, but no live reply is required.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zoom (live) last&lt;/strong&gt; — when the topic needs real-time debate, is sensitive, or involves a decision with trade-offs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Loom&lt;/strong&gt; if your team is distributed, your messages are mostly one-way, and only a few people record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose Zoom&lt;/strong&gt; if your work is collaborative and decision-heavy, or you run interviews and client calls regularly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid recording&lt;/strong&gt; anything urgent, emotional, or genuinely two-way — that is a call.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Loom versus Zoom is not a contest with a winner — it is a choice between two modes of communication, and the mature answer is to use both deliberately. Loom kills the meeting that should never have been scheduled; Zoom protects the conversation that genuinely needs everyone in the room. Get the async-versus-sync instinct right and you reclaim hours a week without losing the dialogue that matters. Audit your calendar for a fortnight, move the one-way meetings to recordings, and keep the rest live.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is Loom a replacement for Zoom?&lt;/strong&gt;&lt;br&gt;
No — they cover different needs. Loom handles one-way, watch-anytime communication; Zoom handles real-time meetings. Many teams use both: Loom to cut unnecessary meetings, Zoom for discussions that truly need to be live.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Loom free for viewers?&lt;/strong&gt;&lt;br&gt;
Yes. Loom charges per creator — the people who record — and viewers watch shared links for free without an account. That makes it cost-effective when only a few teammates record but many people watch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why does Zoom cut my meeting off at 40 minutes?&lt;/strong&gt;&lt;br&gt;
The 40-minute limit applies to group meetings on the free Basic plan. One-on-one meetings are unlimited. Upgrading to Pro at $13.33 per user per month (annual) removes the cap and extends meetings to 30 hours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I record meetings in Zoom instead of using Loom?&lt;/strong&gt;&lt;br&gt;
You can, but a Zoom recording is a captured live meeting, not a purpose-built async message. Loom is faster for quick screen walkthroughs, generates instant shareable links, and keeps a searchable library, whereas Zoom recordings are heavier and consume cloud storage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which is cheaper for a small team?&lt;/strong&gt;&lt;br&gt;
It depends on who records or hosts. Loom only bills the people who record, so a team where two people make videos for everyone is cheap. Zoom bills per host, so the cost tracks how many people run meetings, not how many attend.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does asynchronous video actually save time?&lt;/strong&gt;&lt;br&gt;
It does when it replaces a meeting that did not need everyone live, because viewers watch on their own schedule and often at faster speed. It saves nothing if it replaces a message that should have stayed text, so match the channel to the task.&lt;/p&gt;

&lt;p&gt;Loom is asynchronous (record once, watched anytime, billed per recorder); Zoom is synchronous (live, billed per host). Use Loom for one-way work — walkthroughs, onboarding, reviews, async standups, client explainers — and Zoom for real-time work: debate, sensitive talks, interviews, decisions. Escalate deliberately: text → Loom → Zoom. Most teams need both; getting the async-vs-sync call right is what reclaims hours.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>remote</category>
      <category>tools</category>
      <category>async</category>
    </item>
    <item>
      <title>Build a CRM Backend on Notion's API in 2026: $5/Month Stack with Node.js</title>
      <dc:creator>TrackStack</dc:creator>
      <pubDate>Sat, 06 Jun 2026 16:02:01 +0000</pubDate>
      <link>https://dev.to/trackstack/build-a-crm-backend-on-notions-api-in-2026-5month-stack-with-nodejs-4d37</link>
      <guid>https://dev.to/trackstack/build-a-crm-backend-on-notions-api-in-2026-5month-stack-with-nodejs-4d37</guid>
      <description>&lt;p&gt;The full version of this article teaches non-developers how to configure Notion's UI into a working CRM. This is the developer take: &lt;strong&gt;don't configure the UI — automate around the API.&lt;/strong&gt; I run a small-business CRM stack on Notion for ~$5/month total infrastructure (Notion Free + a $6 VPS for cron jobs and webhooks). Below is the actual code, the rate-limit math, and where this breaks down.&lt;/p&gt;

&lt;p&gt;If you're a non-dev founder, read the &lt;a href="https://trackstack.tech/en/how-to-use-notion-as-a-lightweight-crm-2026-step-by-step/" rel="noopener noreferrer"&gt;full version&lt;/a&gt; for the UI-first setup. If you're a developer who wants to skip the SaaS subscription and own your stack, this is for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  The architecture
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Website form]
    ↓ webhook
[Node.js receiver on VPS]
    ↓ Notion API
[Notion databases: Contacts, Deals, Activities]
    ↓ Notion webhooks
[Slack notifier on stage change]

[Cron @ 9am daily]
    ↓ Notion API
[Stale lead detector → Slack DM]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Four small services, all talking to Notion as the data layer. No CRM subscription. No Zapier monthly fee. ~80 lines of Node.js total. The actual CRM "logic" lives in your code, not in someone else's billing engine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Website form → Notion contact
&lt;/h2&gt;

&lt;p&gt;Create a Notion integration at &lt;code&gt;notion.so/profile/integrations&lt;/code&gt;, copy the secret, and share your Contacts database with it. Database ID comes from the URL (the 32-char hex after the workspace name).&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Client&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@notionhq/client&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;express&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;express&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;crypto&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;crypto&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Client&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_TOKEN&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;CONTACTS_DB&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_CONTACTS_DB_ID&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;app&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;express&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;use&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;express&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;());&lt;/span&gt;

&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/lead&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// Verify the source — your form should sign the payload&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;sig&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;x-form-signature&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;computed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;crypto&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createHmac&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;sha256&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;FORM_SECRET&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;update&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;body&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;digest&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;hex&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;sig&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="nx"&gt;computed&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;401&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;end&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;email&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;company&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;message&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;utm_source&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;body&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;email&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;400&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;error&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;email required&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="c1"&gt;// Dedupe by email — query existing first&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;existing&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;databases&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;database_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;CONTACTS_DB&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;property&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Email&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;email&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;equals&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;email&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;page_size&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;existing&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// Update last-contacted on the existing contact&lt;/span&gt;
    &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;pages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;update&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;page_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;existing&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;results&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Last Contacted&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;date&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;start&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;toISOString&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;status&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;updated&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;existing&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;results&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="c1"&gt;// Create new contact&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;pages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;parent&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;database_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;CONTACTS_DB&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;name&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nx"&gt;email&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;Email&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;email&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;Company&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;rich_text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;company&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;''&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;Status&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;select&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;new lead&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;Source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;select&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;utm_source&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;website&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Last Contacted&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;date&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;start&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;toISOString&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;Notes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;rich_text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;message&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;''&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;status&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;created&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;listen&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;3000&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Drop this on a Hetzner/DO/Linode $5-6/month VPS, point your form's webhook at &lt;code&gt;https://crm.yourdomain.com/lead&lt;/code&gt;, slap Caddy in front for TLS. Your website form now creates Notion contacts with deduplication.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The dedupe-by-email pattern&lt;/strong&gt; is the single most useful thing here — without it, retries and double-submissions clutter your database with duplicates within a week. Always upsert.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Notion webhook → Slack on stage change
&lt;/h2&gt;

&lt;p&gt;Notion shipped first-party webhooks in late 2024 — finally usable for reactive automations. Subscribe via the API to events on your Deals database:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// One-time setup: register a webhook for the Deals database&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://api.notion.com/v1/webhooks&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;Authorization&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`Bearer &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_TOKEN&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Notion-Version&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;2022-06-28&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://crm.yourdomain.com/notion-webhook&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;event_types&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;page.properties_updated&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
    &lt;span class="na"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;database_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_DEALS_DB_ID&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;}),&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then handle the events:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;/notion-webhook&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;express&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}),&lt;/span&gt; &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// Verify Notion's signature&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;signature&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;x-notion-signature&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;computed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;crypto&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createHmac&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;sha256&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_WEBHOOK_SECRET&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;update&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;digest&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;hex&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;signature&lt;/span&gt; &lt;span class="o"&gt;!==&lt;/span&gt; &lt;span class="s2"&gt;`sha256=&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;computed&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;401&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;end&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;event&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;parse&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;req&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;body&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;utf8&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;));&lt;/span&gt;

  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;type&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;page.properties_updated&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;pageId&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;entity&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;pages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;retrieve&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;page_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;pageId&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;

    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;stage&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;Stage&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;select&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;dealName&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Deal Name&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;]?.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="p"&gt;?.[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]?.&lt;/span&gt;&lt;span class="nx"&gt;plain_text&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;page&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;Value&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;number&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;stage&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;won&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;SLACK_WEBHOOK_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
          &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`🎉 Deal won: *&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;dealName&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;* — $&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;value&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nf"&gt;toLocaleString&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;?&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;}),&lt;/span&gt;
      &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;

  &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;status&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;200&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;end&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now when anyone on your team drags a deal card to "won" in Notion, your sales channel gets a celebration message. Same pattern for "lost" with a different emoji, or "negotiation" to ping the deal owner.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The catch:&lt;/strong&gt; Notion's webhooks fire on every property change, including bulk imports. If you update 50 deals in a script, you'll get 50 webhook calls. Add idempotency (track recently-seen event IDs in Redis or a sqlite file) and rate-limit your Slack notifications client-side.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Stale lead detector (the cron that actually saves leads)
&lt;/h2&gt;

&lt;p&gt;The single most valuable automation: a daily check for leads who haven't been contacted in 30+ days. This is what a real CRM does automatically; we'll build it in 30 lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// stale-leads.js — run via cron @ 9am daily&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Client&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@notionhq/client&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Client&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_TOKEN&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;THIRTY_DAYS_AGO&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="mi"&gt;30&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;86&lt;/span&gt;&lt;span class="nx"&gt;_400_000&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;toISOString&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;

&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;findStaleLeads&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;stale&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[];&lt;/span&gt;
  &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="nx"&gt;cursor&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="k"&gt;do&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;notion&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;databases&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;query&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;database_id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;NOTION_CONTACTS_DB_ID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;and&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
          &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;property&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Status&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;select&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;equals&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;new lead&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
          &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;property&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Last Contacted&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;date&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;before&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;THIRTY_DAYS_AGO&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
        &lt;span class="p"&gt;],&lt;/span&gt;
      &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="na"&gt;start_cursor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;cursor&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;page_size&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;(...&lt;/span&gt;&lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;results&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="nx"&gt;cursor&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;has_more&lt;/span&gt; &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;next_cursor&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;while &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;cursor&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;stale&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;findStaleLeads&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;

&lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;lines&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;stale&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="p"&gt;?.[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]?.&lt;/span&gt;&lt;span class="nx"&gt;plain_text&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Unnamed&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;email&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;Email&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;email&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;''&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;lastContacted&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;properties&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Last Contacted&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;]?.&lt;/span&gt;&lt;span class="nx"&gt;date&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;start&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;`• *&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;* (&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;email&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;) — last touched &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;lastContacted&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;})&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="se"&gt;\n&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;SLACK_WEBHOOK_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`☕ Morning. &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; stale leads (&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt; &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;top 10&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;all&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;):\n&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;lines&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}),&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;crontab -e&lt;/code&gt; and add &lt;code&gt;0 9 * * * /usr/bin/node /home/crm/stale-leads.js&lt;/code&gt;. Every morning at 9, your Slack gets a digest of leads who need a nudge.&lt;/p&gt;

&lt;p&gt;This is genuinely transformative for a 1-3 person sales motion. The cost of forgetting a warm lead for 60 days is way bigger than the cost of running this cron.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rate limits and pagination math
&lt;/h2&gt;

&lt;p&gt;Notion's API is rate-limited to &lt;strong&gt;~3 requests per second&lt;/strong&gt; average per integration. Burst above that and you'll get &lt;code&gt;rate_limited&lt;/code&gt; errors. Database queries return max 100 results per page; full-database scans need pagination.&lt;/p&gt;

&lt;p&gt;For a CRM with ~500 contacts and ~100 active deals, every operation is well within limits. The numbers that matter:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Form submission&lt;/strong&gt;: 2 API calls (query for dedupe + create/update). At 100 leads/day = 200 calls = 6,000/month.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Webhook handler&lt;/strong&gt;: 1 API call per event (retrieve page). At 50 stage changes/day = 1,500 calls/month.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Daily stale-lead cron&lt;/strong&gt;: ~5-10 paginated queries. ~300 calls/month.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Total: ~8,000 API calls/month. The Notion API has no hard monthly cap on free tier — just the per-second rate limit. You're effectively unlimited at this scale.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where you'd hit limits:&lt;/strong&gt; bulk imports (CSV migration of 10,000 contacts), aggressive polling instead of webhooks, or running this for 10+ teams off one integration. Use multiple integration tokens if you scale that far.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this stack breaks down
&lt;/h2&gt;

&lt;p&gt;Honest list — when it's time to graduate to a real CRM:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Email integration.&lt;/strong&gt; Notion's API doesn't have native email send/track. You can wire Postmark or SES for sending, but you're building a mini email-CRM yourself. Past ~10 sequences and &amp;gt;1k subscribers, use a real ESP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-step sequences.&lt;/strong&gt; A "3 emails over 7 days" drip campaign is doable but you're maintaining state in Notion which is awkward. Tools like Customer.io exist for this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team scaling.&lt;/strong&gt; Notion permissions are page-level. "Sales rep X sees only their leads" requires hacks (separate workspaces, complex view filters). Real CRMs do this in 30 seconds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reporting trust.&lt;/strong&gt; Your CFO wants a forecast. You can build pipeline-value sums in Notion, but win-rate trends, MEDDIC scoring, rep performance — those are weeks of formula-and-rollup hell. Buy a CRM.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For graduation paths, our &lt;a href="https://trackstack.tech/en/pipedrive-vs-hubspot-b2b/" rel="noopener noreferrer"&gt;Pipedrive vs HubSpot for B2B&lt;/a&gt; comparison and &lt;a href="https://trackstack.tech/en/best-crm-for-small-business-2026-2/" rel="noopener noreferrer"&gt;best CRM for small business&lt;/a&gt; roundup are the natural reads.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The full stack:&lt;/strong&gt; Notion (Free) + $5-6/month VPS + Caddy + ~80 lines of Node.js. Total infra: ~$5-10/month.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What you get:&lt;/strong&gt; dedup-on-submit, webhook-driven Slack notifications, stale-lead detection. The 90% of a real CRM that actually matters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What you don't get:&lt;/strong&gt; native email, sequences, sales-team reporting, deliverability tracking. Build these and you're rewriting HubSpot.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When it breaks:&lt;/strong&gt; past 500 contacts + email-heavy workflows + 5+ team members. Graduate at that point — don't fight it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The pattern generalises beyond CRM. Notion API + small Node.js services replaces a lot of $30-100/month SaaS subscriptions for early-stage businesses. The trade is: you own the stack, you maintain it, and one bug at 2 AM is yours to fix. For dev-founders who like that trade, it's a great deal.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://trackstack.tech/en/how-to-use-notion-as-a-lightweight-crm-2026-step-by-step/" rel="noopener noreferrer"&gt;trackstack.tech&lt;/a&gt; with the UI-first setup walkthrough and FAQ.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>api</category>
      <category>node</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
