FAQs for LiveRamp Tags
See below for FAQs for LiveRamp tags.
Note
See our other LiveRamp tag implementation guides for FAQs for those specific tags.
Why am I seeing a 451 error status when I try to call the tag?
LiveRamp’s pixel server returns a 451 status code when a request is made from a country on the country exclusion list for that tag. If you are serving traffic from the EU, there might be special paperwork required, so please work with your account team to determine where you are allowed to use your tag if you believe this is necessary.
How can I URL encode values?
This tool from Bing will encode or decode a string.
All letters (a-z, A-Z), numbers (0-9), dashes (-), underscores (_), periods (.), and tildes (~) can remain as is. Other symbols should be changed to their associated three-character string in the second row of the table below.
! | # | $ | % | & | ' | ( | ) | * | + | , | / | : | ; | = | ? | @ | [ | ] |
%21 | %23 | %24 | %25 | %26 | %27 | %28 | %29 | %2A | %2B | %2C | %2F | %3A | %3B | %3D | %3F | %40 | %5B | %5D |
What’s the best way to implement a LiveRamp tag?
There is no definitive answer to this question as it depends entirely on your technology stack, other partners you’re working with, the outcome you’re trying to accomplish, etc. There are a large number of ways to implement a tag, and you should use the one that will work best for your use case.