Confidential. Prepared exclusively for definity. © 2026 Syed Yasir. All rights reserved.
definity definity
Confidential · Prepared for definity
Tracking & Measurement Audit

Connecting every demo and signup back to the spend that earned it.

An outside-in review of how www.definity.ai collects, protects and uses marketing data, with a clear plan to link LinkedIn clicks to pipeline and revenue.

Read the summary
Client
definity
Website
www.definity.ai
Date
September 17, 2026
Prepared by
Syed Yasir
01

Executive summary

definity.ai collects plenty of behavior data, but its two most valuable conversions, demo bookings and signups, are not reaching GA4 or LinkedIn.

What is working

  • A cookie consent banner is installed.
  • GA4, LinkedIn Insight Tag, HubSpot and PostHog are live.
  • A first- and last-touch attribution idea is already in place.

What is broken

  • Demo bookings and signups are invisible to ad platforms.
  • Tags run before visitors give consent.
  • Three GTM containers, one empty and one misconfigured.

Why it matters

  • LinkedIn budget learns from page visits, not pipeline.
  • Growth from free signups cannot be credited to channels.
  • Privacy gaps are a trust risk with enterprise buyers.
3of 15 checks pass
PassPartialFail
Hover or tap a block to read the check.

    Three priorities

    02

    Scope and method

    An outside view built from public data. No account access was used.

    Consent and network scans

    Four homepage scans recorded every request before and after "Accept all". One additional scan rated server-side readiness, cookie life and page speed.

    Public page review

    Homepage, Book a Demo, Pricing and the signup path to app.definity.run.

    GTM container files

    The live published version of GTM-T7QZM8T5, GTM-W4Q3MM7M and GTM-WPFVJX8Z, read tag by tag.

    Limits: scans ran from outside the EU, on the homepage only. Tag names, paused tags and drafts are not visible in public files. Items marked To confirm need a short check inside the relevant account.

    03

    Current state

    What loads on the site today, and how it scores.

    Server-side readiness

    Score out of 100, from the readiness scan

    Requests by platform

    91 requests in about six minutes on one page

    Requests sent before any consent choice

    Per platform, before the banner was clicked

    Tracking cookie lifetime

    Days, as measured in the readiness scan

    Marketing and analytics stack

    PlatformIDHow it loadsSends data before consent
    04

    Key findings

    Twelve findings, sorted by business impact. Open any row for evidence, impact and the fix.

    05

    GTM container audit

    Three containers are live on every page. Select one to see what it runs.

    06

    Business implications

    What the technical findings mean for growth, budget and trust.

    LinkedIn spend is optimized without its best signals

    LinkedIn sees page visits, but not demo bookings, qualified leads or deals. One conversion may also include newsletter signups. Bidding learns from the wrong actions, so cost per qualified demo is hard to control.

    Free-plan growth cannot be credited to its sources

    Signups happen on app.definity.run and lose their original source. The path from Explorer to Pro cannot be tied back to campaigns, the podcast, partners or the AWS Marketplace.

    Trust and compliance exposure with enterprise buyers

    definity sells to enterprise data teams, including a Fortune 500 financial services customer. Emails in URLs, tracking before consent and undisclosed identification tools are the kind of gaps security reviews ask about.

    Hidden cost in page weight and ownership

    Three containers, two session recorders and a broken tag add load to every visit, with a page speed score of 66. Without one owner, every future change carries more risk.

    07

    Recommendations

    One clean container, a server-side layer on your own domain, and a feedback loop from HubSpot to LinkedIn.

    7.1 Target setup

    Sources
    definity.ai and docsOne GTM web container with consent
    app.definity.runBackend events with user ID
    HubSpotDeal stage changes
    Collection
    Server-side GTMRuns on a first-party subdomain such as data.definity.ai. Longer-lasting cookies, consent checks, hashing, one control point.Your domain, your data
    Destinations
    GA4 and BigQueryAcquisition and funnel reporting
    LinkedIn Conversions APIQualified demos and deals as signals
    PostHog and HubSpotProduct usage and lead context

    7.2 Consent mapping

    ToolBanner categoryConsent Mode signalBefore consent (EU and UK)
    GA4Analyticsanalytics_storageCookieless pings only
    PostHogAnalyticsanalytics_storageBlocked
    Microsoft ClarityAnalyticsanalytics_storageBlocked, or Clarity consent API
    LinkedIn Insight and conversionsMarketingad_storage, ad_user_dataBlocked
    HubSpot trackingMarketingad_storageBlocked, forms still work
    Vector and ApolloMarketingad_storage, ad_personalizationBlocked
    Attribution cookiesMarketingad_storageBlocked

    7.3 Event tracking plan

    EventFires whenKey parametersSent toPriority

    No personal data is sent to GA4. Hashed email is used only for server-side ad platform matching.

    08

    KPI framework

    definity grows through two motions: free signups and enterprise demos. The KPIs follow both paths to revenue.

    Website visitby channel, campaign and partner
    High-intent viewpricing, docs, customer stories
    Demo booked
    Free signup
    Qualified lead
    Activated account
    Opportunity
    Revenue
    09

    Roadmap and next steps

    Four weeks from scattered tags to revenue-linked data. Each phase delivers value on its own.

    Timing assumes access to GTM, GA4, HubSpot and LinkedIn Campaign Manager, plus developer time for app events.

    Once the data is clean