No matter how many Omniture Support people tell you that there is no limit on the number of characters you can use as your serial number when implementing Event Serialization, they are wrong!
The limit is 20 characters.
It took me 3 phone calls and a weeks worth of bad data to figure that out. It is no where to be found in their white papers either, so don’t bother looking there.
Subscribe to
Nice to know… but can you give us an example of when Event Serialization would exceed 20 characters? Thanks,
Basically, I was using the UUID Gem for Ruby on Rails to generate the ID. UUID will not create an ID smaller than 32 characters. I ended up using a timestamp based id instead to come in at 14 characters.
I have not been able to find anything for serialization. As you mentioned, the the documentation is not very good. What I need to know is what do I use to serialize my custom events. I can’t use javascript, because it is not serverside. Any ideas as to what I should use to create a unique number for my custom events?
Thanks!
Javascript is not a serverside code so you could do something like:
s.events=”event1:”+unique_id();
and create a Javascript function called unique_id that returns a uid.
Hope that helps.