Cookie Sync

The cookie syncing process allows exchange cookie info between platforms. So, it helps to keep cookies (and so, user's preferences info) more actual and makes targeting more accurate. 

How to set up Cookie sync 

You can enable cookie sync functionality on web traffic for SSP or DSP in just a few clicks.
Also, some amount of tech work should be done on the SSP and DSP side to ensure that the cookie sync process works.

Enabling cookie sync for SSP endpoint

SmartHub side

On SmartHub side, open the Main section and find the endpoint you need.
Click cookie sync symbol:

Click ‘Generate sync URL’:

Once the link generated, copy it:

Save the endpoint.

Provide the SSP with the generated URL.

Report

After setting sync links, you can get the report on each synced endpoint:

You will see the statistics with such data:
Date
New Users – the number of new users added
Existing Users – the number of users already exist (synced before)
Invalid Keys – the format of received user id is unknown/invalid
Invalid Redirects – the number of errors occurred on trying to call partner redirect link (i.e link doesn't return HTTP code 200 OK or 302 REDIR). 
Errors – an overall number of errors occurred within the syncing process (for example, we could not write cookies to the user). 

SSP side

As SmartHub provides SSP with a sync pixel, the SSP should replace ${USER_UID} macros with some user id (e.g. 520e8710-e39b-47d4-a812-492655340010) which SSP should put into placement code.
After the pixel called from the user’s browser, we save the USER ID that we received via replaced macro and assign our ID to the user (using cookies). We store data for a particular user for 14 days.
Example of the URL generated:  http://us.shb-sync.com/<image_id.gif>?puid=${USER_UID}

Example of the URL with the macro replaced:  http://us.shb-sync.com/image_id12345678.gif?puid=520e8710-e39b-47d4-a812-492655340010

Enabling cookie sync for DSP endpoint

DSP side

DSP provides a sync URL (Cookie Sync URL’ field in DSP endpoint settings). Such a link must contain at least one macro: ${REDIR} or ${USER_ID}. In case both macros used, we will use the first specified in a link.
Smarthub puts this link into adm, so the link is called when the impression occurs.
If ${USER_ID} macro is used, Smarthub will replace that macro with our User ID.
When an impression occurs, we will send our USER ID to the DSP.
If ${REDIR} macro is used, then, when the impression occurs, Smarthub will replace it with our URL, which will be sent to the DSP. DSP sends that URL back to us with the USER_ID macro replaced by the real ID.
Example of the redirect URLs with macro:
example.com/sync_endpoint?puid=${USER_ID}
example.com/sync_endpoint?redir=${REDIR}
http://us.shb-sync.com/<image_id.gif>?puid=${USER_ID} – an example of a link we will put into ${REDIR} parameter. 
After the user-sync process finished, SmartHub will send the cookie ID in the bid request as buyeruid.

SmartHub side

On SmartHub side, open the Main section and find the endpoint to set up.
Click cookie sync symbol:

Paste the link you received from the DSP into the Cookie Sync URL field:

Check “Only Synced Users” so that only users who are already synchronized are sent to the server.

Save the endpoint. 
If all settings on the partner’s side are done, cookie sync becomes active immediately after saving the endpoint.

Report

After setting sync links, you can get the report on each synced endpoint:

You will see the statistics with such data:
Date
New Users – the number of new users added.
Existing Users – the number of users already exist (synced).
Invalid Keys – the format  of received user id is unknown/invalid
Invalid Redirects – the number of errors occurred on trying to call partner redirect link (i.e link doesn't return HTTP code 200 OK or 302 REDIR). 
Errors – an overall number of errors occurred within the syncing process (for example, we could not write cookies to the user).