Best Practices

The best practices below assume that you have completed the basic setup for API integration. If you have not yet completed the basic setup for API integration, please refer to Before You Begin.

Transfer offline data to DFINERY server

You can use DFINERY Import API to transfer various offline data to DFINERY server.

User attribute update and event occurrence scenario after new user inflow

The user consented to receive marketing communications after signing up through an offline store. The user then made a purchase at an offline store.

1. When signing up through an offline store, a new user profile is created via the integrated profile creation and update API.

2. After signing up, if the user consents to receive marketing, the user's marketing consent properties are updated through the user property creation and update API.

3. Afterwards, when purchasing at an offline store, the purchase event of the user is loaded through the event loading API.

In general, it is recommended to call the Create Unified Profile > Create User Profile > Load Event API in this order.