ParticipationRate (FIX tag 849)

PercentageFIX 4.4

ParticipationRate (tag 849) is a Percentage field defined in FIX 4.4. It appears in 8 message types, always optionally.

At a glance

Tag
849
Name
ParticipationRate
Datatype
Percentage (float)
Dialects
FIX 4.4
Messages
8

What the specification says

For a TargetStrategy=Participate order specifies the target participation rate. For other order types this is a volume limit (i.e. do not be more than this percent of the market volume)

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 849

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength120
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
849ParticipationRate0.05
10CheckSum150
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 849 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeRequirednessWhere in the message
CrossOrderCancelReplaceRequesttConditionaldirectly on the message body
ExecutionReport8Conditionaldirectly on the message body
MultilegOrderCancelReplaceACConditionaldirectly on the message body
NewOrderCrosssConditionaldirectly on the message body
NewOrderListEConditionalinside the ListOrdGrp component
NewOrderMultilegABConditionaldirectly on the message body
NewOrderSingleDConditionaldirectly on the message body
OrderCancelReplaceRequestGConditionaldirectly on the message body

Wire format

A decimal rate where 1.0 means 100%, not 1%. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 849 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[849];field?.name;   // "ParticipationRate"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

Other Percentage fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44