Fundamentals

  • Our approach to Privacy
  • Payload, Security
  • Tracking code, how Nudge collects data
  • Nudge Products

    • Content Measurement API

  • JW Player Video event tracking in Nudge
  • Cloudinary Video event tracking in Nudge

    • Marketing Operations

  • Using Nudge on NoCode platforms
  • Using Nudge with Bubble.io
  • Using Nudge with Webflow
    • Home Breadcrumb Docs Breadcrumb Fundamentals Breadcrumb Payload, Security

    Payload, Security

    The Nudge payload is designed to be lightweight.

    A summary of the payload and how the code loads on page:

    • The initial piece of tracking javascript runs 3.5-4kb.
    • Our initial JS is delivered by CDN, and usually renders in 60 – 200ms. This script loads the bare-bones essentials to deploy the rest of the tracking.
    • After, our impression is recorded with all key user information, this is also ~4kb.
    • After this, we track (every second) additional information, this is 357 bytes per second.
    • These pings usually render in 90-400ms, depending on the strength of your connection.

    All calls made to the Nudge servers are non-blocking and asynchronous.

    Nudge hashes IPs to geo-locate impressions. Then discards the data from the impression profile.

    Depending on your config, this payload is 70-90% smaller than other analytics systems. Assuring minimal overhead to provide greater fidelity into your content.



    We'd welcome your feedback, this was content was:
    🙌 💪 👍 👎
    “Join