- Specify loose tier as the companion type when you configure a flight. When a flight with the companion type that is set to loose tier is evaluated and selected to serve, subsequent ad requests to the same page give priority to the same flight once that flight's tier is reached.
- Use secondary state vector IDs to map additional identity information about a user to a primary state vector ID. When an ad call includes a secondary ID and the data lookup for that ID produces a value for the primary ID, the value of the primary ID is used to store the state vector data. Also, any state vector data that had previously been stored using the secondary ID is merged into the primary ID’s state vector. Contact SAS Technical Support to enable this feature.
- Specify the exchange in user-defined networks with the name of the vendor or a number that represents the vendor. If the value of the vendor tag is not a valid user-defined network, the call is attributed to the generic headerbidding network if the network is enabled. Otherwise, the headerbidding information in the ad request is ignored and the rest of the ad call is handled normally.
- Use Universal ID version 2.0 by specifying UID2 in the real-time identifier partner field.
