Best Practices

Maximizing Addressable Inventory Coverage

Header bidders that support passing envelopes from publishers include Prebid, Amazon TAM, Inmobi, Index Wrapper, and OpenWrap; integrating with these technologies will ensure you’re able to capture ATS-generated envelopes across cookieless/MAIDless environments.
For additional RampID coverage where a device-based identifier is present, use of Real Time ID Sync (RTIS) for cookies, as well as MAID and CTV ID <>envelope mapping files provides additional coverage (these files map a device ID to an envelope, which you can use as an input to your Sidecar).

Use weekly envelope mapping file deliveries to do a full refresh, do not cache envelopes longer than 7 days.

To receive envelopes from other SSPs, make a request of the SSP to be configured in their Sidecar (they will send envelopes to using oRTB or other methods you may have in place with them).
Scaling internationally – assuming appropriate contracts are in place:

Ensure that LiveRamp has your relevant IPs for the locations where you'll be running Sidecar.
Deploy Sidecar in each regional data center to minimize latency.

Use alias [email protected] to make updates to your own Sidecar mappings.

Please indicate the DSP, a seat number (can be any combination of text or numbers you specify and recognize), and whether you’d like to send envelopes or RampIDs to the partner
Once configuration is confirmed by LiveRamp, please confirm with the DSP that they are receiving RampIDs from your Sidecar.

We recommend providing Sidecar with 2-4 dedicated cores and ~300MB RAM to start. Nothing is persisted to disk, so storage requirements are basic.
Sidecar can run co-resident with the exchange applications, or as a standalone service.
SSPs should aim for less than 2ms latency at the 99th percentile of calls. Network usage will vary by SSP.

Most SSPs are using a framework to evaluate increases in CPM and sell-through for traffic with a RampID associated with it.

Become a "destination" to enable LiveRamp customers to send you RampIDs for targeting.
Provide Exposure Logs for buyers to do RampID level measurement.
Partner with LiveRamp to create a Capabilities Guide to educate buyers on your capabilities.
Consider whether other audience targeting products are appropriate for your business: examples include establishing a Data Marketplace, or becoming an onboarding reseller.

New Sidecar versions are generally released quarterly, and customers will be notified. Frequent Docker pulls are not necessary.