Key idea
Execution labels help organize activity; they do not reveal whether a trade is informed, profitable, or unhedged.
Sweep and block labels are often presented as signs of urgency or size. They can make an activity feed easier to scan, but they do not tell you whether the participant has superior information or whether the position will succeed. Their usefulness begins with the provider's exact definition.
Treat execution labels as sorting tools. They can identify records to inspect, while the contract, timing, and broader context determine the next research question.
Read the provider's classification rule
Providers may group executions using venue, size, timing, or other attributes. A label on one platform may not map perfectly to a label on another. Before comparing counts, verify that the definitions and aggregation windows match.
If a methodology is not disclosed, record that uncertainty. Avoid using the label to make a more specific claim than the available documentation supports. “Classified as a sweep by this feed” is different from asserting the identity or motive of the participant.
Watch for fragmented activity
Imagine a hypothetical order that results in several executions close together. If the feed shows five prints, that does not necessarily mean five independent traders arrived at the same conclusion. It may describe fragments of one order or a grouped execution event.
When studying activity, preserve both the raw records and any grouping rule you apply. Count grouped events consistently. Otherwise, a change in how the display combines prints can look like a change in market participation.
Compare the contract context
Inspect expiration, strike, transaction price, and underlying price. A short-dated contract near a scheduled event presents different questions from a longer-dated contract away from the money. The execution label does not remove those distinctions.
Next, look at what the underlying did before and after the observation. Did the activity precede a move, follow it, or appear during a quiet interval? Define the window before checking the outcome so you do not choose the most flattering segment afterward.
Design a small classification study
Collect a modest sample using one unchanged definition. Record the label, contract details, event context, and subsequent behavior at fixed checkpoints. Include examples that did nothing and examples with ambiguous classification.
Your first goal is to learn what the feed represents, not to prove that one label is a winning strategy. A useful result might be discovering that the label adds little beyond the contract's event exposure or liquidity.
DAXA's flow research areas can be explored alongside the broader platform. Check the current feature comparison before choosing access, and use the labels to support a documented investigation rather than substitute for one.
Sources and further reading
Bring more context to your research
Explore DAXA’s research workspace and choose a membership that fits the information you use.