Table of Contents

**This is an old revision of the document!**

User Sync Documentation

DSP

Atomx stores the mapping

Requires dsp.user_sync = 1

Add mappings by loading our pixel with user= the DSP buyerid.

http://p.ato.mx/sync?d=123&user=xxx

We will send xxx in bidrequest.user.buyerid.

Optionally make our frontend load the pixel using:

dsp.user_sync_url = '${PROTOCOL}//...'
DSP stores the mapping

Get our user ID using:

http://p.ato.mx/sync?redir=http%3A%2F%2Fexample.com%2Fmap%3Fuser%3D%7BUSERID%7D&gif 

Will redirect to:

http://example.com/map?user=yyy

Where yyy will be the ID Atomx sends in bidrequest.user.id.

SSP

Atomx stores the mapping

Requires ssp.user_sync = 1

Add mapping by loading our pixel:

http://p.ato.mx/sync?s=123&user=yyy

Where yyy should be send as bidrequest.user.id in requests for the same user in the future.

Optionally send back a pixel with our bids in case we don't know the user:

ssp.user_sync_url = '${PROTOCOL}//...'
SSP stores the mapping
http://p.ato.mx/sync?redir=http%3A%2F%2Fexample.com%2Fmap%3Fuser%3D%7BUSERID%7D

Will redirect to:

http://example.com/map?user=xxx

Where xxx should be send in bidrequest.user.buyerid