What is Transmission Control Protocol (TCP)?
Transmission Control Protocol (TCP) is a transport-layer protocol in the Internet protocol suite. It delivers a byte stream between two hosts with ordering, retransmission of lost data, and flow control. Most web browsing, email, and file transfers use TCP because applications need reliable delivery over IP, which by itself only offers best-effort routing.
Table of Contents
How does TCP establish a connection and move data?
TCP is connection-oriented. A client and server complete a three-way handshake (SYN, SYN-ACK, ACK) before application data flows. Data is split into segments with sequence numbers so the receiver can reorder out-of-sequence packets and detect gaps. The sender expects acknowledgments; if one is missing, it retransmits. The receiver advertises a window so a fast sender cannot overrun slow hardware. Congestion control adjusts send rates when the network shows loss or delay.
This design favors correctness over minimum delay. If a packet is lost, later data waits while TCP recovers that segment (head-of-line blocking at the transport layer). That is why real-time media sometimes uses UDP or protocols built on UDP instead of raw TCP.
TCP compared to UDP
User Datagram Protocol (UDP) sends datagrams without a connection, ordering, or built-in retransmission. TCP adds reliability and state; UDP adds little beyond ports and an optional checksum. Many systems use TCP for HTTP/HTTPS historically; HTTP/3 uses QUIC over UDP while implementing its own reliability rules.
Why TCP matters for click fraud and ad fraud
Fraud and bot traffic still often rides on TCP because web ads and landing pages are served over HTTPS (TLS on TCP). Security and anti-fraud stacks observe TCP and TLS behavior: handshake timing, window growth, retransmission patterns, and how sessions align with claimed device or geography. Unusual combinations (for example, datacenter-style RTT with residential claims, or automation libraries that reuse TCP/TLS fingerprints) support risk scoring alongside suspicious behavior signals.
TCP does not reveal click intent by itself, but it is part of the network context that specialists use to separate automated or bot sessions from typical human browsing. That context complements application data such as GCLID and post-click events. For a broader view of abuse types, see click fraud and ad fraud. Teams also combine network signals with how fraud detection works in practice.
