Aptos Integration

Fire any collected data from Odicci directly into Aptos to increase customer knowledge, build triggers and automations to better engage newly and enriched profiles.

Step 1 - Activate your Aptos Integration

In your Odicci account click on the icon in the top right corner and select settings. Within settings navigate to Integrations, scroll to Aptos and click on ADD.

Make sure you have your Aptos Partner ID and API key at hand and copy / paste it to activate the integration.

If the credentials are valid you will automatically you will see a success message.

Step 2 - Field Mapping

In your Odicci experience click on settings (cog wheel inside studio) to access the integration configuration. Tick the Aptos integration checkbox to activate the integration for the current experience.

Then just select your Odicci field from the dropdown on the left and map it to your Aptos field using the dropdown on the right.

Currently, the following fields in Aptos are available to be mapped to:

• addressLine1: (string) The value of the first address line.  This generally holds the street address
• addressLine2: (string) The value of the second address line.  This generally holds the apartment.
• addressLine3: (string) The value stored in the third address line. This generally holds the city.
• addressLine4: (string) The value stored in the fourth address line. This generally holds the State or Province.
• birthDate: (string: date = yyyy-mm-dd) The customer's birthdate. Note that Michael Kors prefer to use a format from the studio where no year (i.e., yyyy) is included. This is acceptable since the integration passes a hardcode for the year.
• countryCode: (string) The 3-letter ISO-3166 country code of the targeted country. For full list, see https://www.iso.org/obp/ui/#search.
• directMailOptin: (string) The opt-in preference associated with the address. 
• emailAddress: (string) The email address of the customer
• emailOptin: (string) The opt-in preference associated with the email address
• firstName: (string) The first name of the customer.
• genderCode: (string) The customer’s gender. 
• lastName: (string) The last name of the customer.
• phoneNumber: (string: maxLength-16) The numeric phone number. Phone numbers with punctuation, special characters, and/or letters will be rejected.
• phoneCountryCode: (string) The ISO-3166 country code (e.g. USA, CAN). For full list, see https://www.iso.org/obp/ui/#search.
• postalCode: (string) The zip code or postal code for the address.
• preferredLanguageCode: The 3-letter language code of the preferred language of the customer. For list of 3-letter language codes, please see the CRM Language Code section at the end of this document.
• StoreNumber: The store number linked to the experience.  If there is no store linked to the experience, enter the value “9999” into a hidden field and map to this Aptos field.
• textOptin: (string) The opt-in preference associated with the phone number for text messaging.
• title: (string) The title associated with the customer.  Dr, Duke, Madame, Miss, Mr, Mr & Mrs, Mr and Mrs, Mrs, Ms, Rev, Sir.
• voiceOptin: (string) The opt-in preference associated with the phone number.

Step 3 - Test Integration

Once your integration has been setup in Odicci, publish your experience and enter some data to make sure all fields have been mapped correctly.

Once submitted, you can check the integration push has been successful in the reporting section of the experience. If the push has failed, please ensure you have mapped all fields correctly before contacting support.

If you have had successful pushes, the last check to be made is within Aptos to ensure the data fields have been updated for that record.