[go: up one dir, main page]
HomeGuidesChangelogDiscussions
Changelog
Back to All

v2.0.0-alpha Release

over 4 years ago by Ian Meyers

👍

Check out the full v2 documentation for a complete picture of updates and enhancements

V2 Map Endpoint

The primary enhancement in this version of the sidecar is the ability to support multiple identifiers in a single identity envelope. Our launch partner is The Trade Desk, offering UID2.0. Read more about our partnership here.

Presently, exchanges provide an envelope to the /map endpoint (optionally limiting seatIDs) and receive one or more seat/IDL 2-tuples in a successful response.

This release introduces a new map endpoint under the path /v2/map. The envelope is still provided as a query parameter. Without further options, output will be delivered as follows:

[
    {
        "source": "liveramp.com",
        "mapping": {
            "SEAT0001": "XY0024Bro9-...lpMs",
            "SEAT0002": "XY04664X0Yq...vQ2dqEYs"
        }
    },
    {
        "source": "uidapi.com",
        "mapping": {
            "SEAT0001": "AgAAAAPQ8Qy6FO3w4M2diZFxjbYu...",
            "SEAT0002": "AgAAAAPQ8Qy6FO3w4M2diZFxjbYu..."
        }
    }
]

As shown above, output is grouped by "source", currently either liveramp.com or uidapi.com, the apex domain for The Trade Desk's UID2 service. Within each object, there is an additional attribute for "mapping" that contains the seat/identifier tuples.

As with the "v1" /map endpoint, output can be limited by selecting specific seatIDs. Additionally, output can now be limited in the "v2" endpoint by providing an idsource parameter, i.e. &idsource=liveramp.com. When applied to the "v1" /map endpoint, the specified idsource will override the default source.

As with LiveRamp IDLs, UID2s should be added to the user extension object as an additional "eid" in OpenRTB2.5 bid requests.

Passthrough Seat Configuration

In order to support identity envelope propagation (e.g. exchange-to-exchange workflows), we now support setting up a seat as a "pass-through" seat. This will output the envelope under the liveramp.com source (in v2) without any transformation. This enables you to rebroadcast the identity envelope to exchanges running their own sidecar instances, without needing to manage a separate workflow outside of the sidecar. 

[
    {
        "source": "liveramp.com",
        "mapping": {
            "SEAT0001": "XY0024Bro9-...lpMs",
            "SEAT0002": "XY04664X0Yq...vQ2dqEYs",
            "EXCHANGE0003": "AvPel2ZRj_bHCBYUow6fBpEk3sVeuyFfyKg9PIiJUzBOWhoHXTUpXmpFqMv1hbm9_I8eLD3zOStW2hd_6SHOjzoAuXXAvel2BjSn1ALIFyzq"
        }
    }

Update on Performance

Although additional features have been enabled to support more identifiers in the envelope, we have observed generally consistent performance between previous and the current versions of the sidecar.

The best results, based on latency and throughput per CPU core, are achieved with a relatively low number of CPUs (1, 2, 4 or 6) and when the number of connections equals 2x the number of CPUs.

600 594