Server Side Track API Limited to 2083 char payload on URI (get)

Question

According to documentation, when registering a server side track event, I am to use GET and include the payload in the url. The payload is a json document that is base64 encoded. No problem.

However, when sending an order placed event including addresses and items, it is very easy to exceed the 2083 url character limit, which throws an exception, and makes the method call unusable.

Can I use Post instead, and include the payload that way, and if so, is it still base 64 encoded, or just the json payload?

Thanks

alex.hong · Accepted Answer

Hey there @Michael Khalsa,Welcome to the Community and thanks for sharing your question!For POST track/identify calls, you send the payloads as form url encoded data. see the example requests in the docs fortrack postandidentify post.We also have a great community post regarding a conversation in this same topic:Although not the exact question, it goes into the technicalities of it (especially the most recent comment).Hope that answered your question!Alex

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials