Building a cookie sync with LiveRamp will enable us to match your cookies to other partner cookies, mobile devices, proprietary platform IDs, and RampIDs.
Cookie syncs with LiveRamp leverage standard pixel-based syncing, off of your and/or LiveRamp’s traffic, to build a large pool of shared cookies.
Minimum Syncing Period
In general, a cookie sync should be active for at least two weeks before leveraging it for any workflows, allowing enough traffic to be synced to create a strong match rate. However, how quickly the cookie sync reaches sufficient scale is dependent on how much traffic is being sent to LiveRamp by the partner.
Maximizing Match Rates
The cookie sync tag should be placed on as much of your traffic as possible, increasing the amount of traffic synced and the number of cookies you can match with LiveRamp.
Implement the Cookie Sync Tag to Sync off of Your Traffic
Using your online footprint, you can fire the LiveRamp tag to initiate a cookie sync with LiveRamp. To direct us your traffic, simply redirect to the LiveRamp pixel:
https://idsync.rlcdn.com/<lr_partner_id>.gif?partner_uid=<cookie_ID>
Additionally, if you have a web page, a cookie sync can be initiated by embedding the LiveRamp pixel in either an iframe or a gif pixel in your page’s footer.
Iframe:
<iframe name="_rlcdn" width=0 height=0 frameborder=0
src="https: //idsync.rlcdn.com/<lr_partner_id>.html?partner_uid=<cookie_ID> "></iframe>
Gif:
<img border='0' hspace='0' vspace='0' width='1' height='1'
src="https: //idsync.rlcdn.com/<lr_partner_id>.gif?partner_uid=<cookie_ID>"/>
Additional Guidelines
Make sure to follow these additional guidelines to avoid having calls fail:
Cookie strings must be between 4 and 84 characters long. Including a cookie ID that is shorter than 4 characters or longer than 84 characters will cause the call to fail.
Cookie strings cannot be blank. Making a pixel call that does not contain a cookie ID will cause the call to fail.
All special characters (characters outside of the ASCII character set, such as “#”, “%”, and “&”) must be URL encoded. If your calls will include special characters, we recommend that you URL encode your entire call. Including a cookie string that contains special characters that are not URL encoded will cause the call to fail.
Syncing off of LiveRamp’s Traffic
Under certain circumstances, we can also initiate a sync off of our web footprint. Contact your LiveRamp representative to see if this option makes sense for your integration.
Data Deliveries
For information about receiving data from LiveRamp, see "Set Up LiveRamp File Deliveries."