Extend purchaseID, transactionID and eventID beyond their current 20char limits

Avatar

Avatar
Validate 1
Level 3
jeromerichard
Level 3

Likes

31 likes

Total Posts

28 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Validate 1
Level 3
jeromerichard
Level 3

Likes

31 likes

Total Posts

28 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 25
Boost 10
View profile
jeromerichard
Level 3

02-12-2014

Hi guys,

 

I'm increasingly running into situations where I'd like to use a full or transaction identifier from a 3rd party platform as a common identifier for SiteCatalyst's s.purchaseID and s.transactionID variables, however I can't as they are beyond the current 20char limit specified by SiteCatalyst.

 

Likewise, if I want to serialise my custom events against a shopping cart generated session id, I can't as this id is typically longer than 20chars.

 

Given that props are 100chars, and eVars are 250chars, I would love to see s.purchaseID, s.transactionID and eventID extended to at least 100chars so that I can use them as intended.

 

Cheers, Jez

2 Comments

Avatar

Avatar
Boost 5
Level 2
adam_haining
Level 2

Likes

17 likes

Total Posts

12 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile

Avatar
Boost 5
Level 2
adam_haining
Level 2

Likes

17 likes

Total Posts

12 posts

Correct reply

1 solution
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Applaud 5
View profile
adam_haining
Level 2

20-01-2016

This is a big one.  Lots of work arounds have been created to do something with the 20 char limitation, but it is an every increasing problem as few systems have GUIDs or unique IDs that are fewer than 20 characters.

Avatar

Avatar
Coach
MVP
StewSchilling
MVP

Likes

342 likes

Total Posts

278 posts

Correct reply

85 solutions
Top badges earned
Coach
Give Back 25
Springboard
Bedrock
Validate 1
View profile

Avatar
Coach
MVP
StewSchilling
MVP

Likes

342 likes

Total Posts

278 posts

Correct reply

85 solutions
Top badges earned
Coach
Give Back 25
Springboard
Bedrock
Validate 1
View profile
StewSchilling
MVP

17-12-2018

Yep.  Still an issue.

I've seen so many situations where a simple prefix of a date string or a siteID would provide the uniqueness needed, but alas... 20 characters. 

I've also seen the situation that Adam mentions where the orderID is just too big for 20 characters.

The worst feeling ever is to tell a client that they've been feeding 24 characters into purchaseID for several years, but four of those characters were thrown away...