How to Register LiveRamp Segments in Beeswax

Clients who manage their first-party and third-party data through LiveRamp can push segment data directly into Beeswax.  The process below describes the steps that should occur to successfully register new LiveRamp segments within Beeswax.

  1. Configure the segments you wish to deliver to Beeswax in the LiveRamp Connect tool.
    1. Note: Only segments that contain users from North America and in select EMEA, APAC, and LATAM countries are supported at this time. See the countries list here
    2. Please ensure that you input your Beeswax Buzzkey in the Client field under the Destination Specific Settings when configuring the destination account. This will ensure that the data accurately populates within your Buzzkey. 
  2. Notify your Beeswax account manager that Beeswax should be expecting an update to your LiveRamp taxonomy.  
  3. Beeswax will receive the updated taxonomy automatically, our Support team will add new taxonomy segments to your UI.
  4. Once LiveRamp begins to deliver the data (usually within a week of segment setup in LiveRamp Connect), Beeswax will start processing those users into the LiveRamp portion of your Segment taxonomy in the Beeswax UI.  You will see counts of the users in each segment under Trafficking > Segments.

Increasing the match rate with LiveRamp and Beeswax

LiveRamp has a feature to prioritize sync for a particular customer, so if you are a direct customer of LiveRamp, please request that they prioritize syncs with Beeswax more, especially on your own properties.

An alternative way is to place a Beeswax sync pixel on your properties, which will create a sync with LiveRamp.  This option is particularly useful for publishers who are operating a campaign where they do not have a direct relationship with the DMP in question. To do this - place the following pixel on the page:

 <img src="" />

This pixel will fire a redirect to LiveRamp with the Beeswax cookie ID of that user.

Learn more about LiveRamp and regions where you can enable it.  

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.