Topics started by matcwhite

3 Topics

M
Contributor I
matcwhiteContributor I
asked in Developer Group

Existing data in v1/v2 migration?

Hello,We have a custom Klaviyo integration for our ecommerce infrastructure, which has been using the v1/v2 APIs for a couple of years.I have fully understood and tested the differences between event structure in the v1/v2 APIs and the new APIs and how to migrate event generating code from the old format to the new format.However, what I can’t quite establish is, what happens to all the existing events data (and profiles) - do we need to re-upload all historical data in the new format?I.e. Are historical events already uploaded via v1/v2 100% compatible with equivalent events uploaded with the new APIs?Are we required to delete all existing metrics and re-upload using the new APIs?Thanks in advance!Mat.    

0
M
Contributor I
2 hours ago
M
Contributor I
matcwhiteContributor I
asked in Developer Group

Include image data in event properties?

Hello,I am wondering if it is possible to include the raw data for an image (pdf or jpg) in an events’ properties when posting a Create Event to /api/events.We have a customer confirmation email which needs to include a QR code for the post office to scan. I’d rather not have to create website links for the QR code images.Any ideas?Many thanks,Mat   

1
Brian Turcotte
Community Manager
1 month ago
M
Contributor I
matcwhiteContributor I
asked in Developer Group

v1/v2 vs v3 event payload data formats?

Hello,We have a completely custom integration where we post JSON data to the /track API to create events and trigger customer notification emails, etc.We’re now faced with migrating to the new APIs. The documentation around the migration from v1/v2 to the new APIs is ver clear on the new endpoints such as /api/events and new functionality etc.However what’s not so clear to me is any change between the data format of the original API payloads vs new API payloads?The Track API reference (https://developers.klaviyo.com/en/v1-2/docs/track-api-reference#back-end-tracking-events-server-side) refers to special fields such as $event_id, $value, $email, $first_name etc. However I cannot find any reference to these in the new documentation. For example the documentation for Create Event (https://developers.klaviyo.com/en/reference/create_event) gives the example payload JSON below: { "data": { "type": "event", "attributes": { "properties": { "newKey": "New Value" },

3
S
Klaviyo Employee
1 month ago

Most helpful members this week

Terms & ConditionsCookie settings

Links & Resources

Platforms

Partners

Useful Things

About

  • Terms and Privacy
    © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.