Supported Data Formats for Apsis One Profile Data
This article covers all the data formats used in Apsis One. Keep it handy whenever you import or export Profile data, build Segments, or set up an integration, so your values land in the right format the first time.
In this article
Attribute data types — Text, Numbers, Boolean, Location, Dates, Timestamps
Limited values — bounce codes, exit flow reasons, achievement types
Email addresses
The Email Attribute must be a correctly formatted email address, with a valid domain (e.g. gmail) and a valid domain extension (e.g. .com):
email_address@domain.com
💡 Only public email addresses can be reached by email sendings.
Phone numbers
The Mobile Attribute must use the MSISDN format — country code followed by the number. For example: 46793699558.
Attribute data types
Text
A UTF-8 encoded text (string) value, with a 1,000-character limit. Chinese and Cyrillic characters are supported in Apsis One.
Numbers
The Number Attribute type accepts number values only. If you need decimals, choose the Number with decimals Attribute type instead.
Boolean
A Boolean Attribute or Event data value can only be true or false, in lower case.
Location
Use the ISO 3166-1 alpha-2 format — two-letter country codes such as SE or US.
Dates
For date-type Attributes, Apsis One accepts all the date formats listed below. Timezones are disregarded.
💡 What you import is normalised to a date. A value like Tue, 07 Mar 1993 04:22:23 +0300 on a date-type Attribute (such as the default Date of Birth) is converted to 1993-03-07 — the time and offset are dropped.
Format | Result in Apsis One |
2013-02-08 | 08/02/2013 |
2013-02 | 01/02/2013 |
2013-W06-5 | 08/02/2013 |
2013-039 | 08/02/2013 |
20130208 | 21/08/2013 |
201303 | 03/01/2013 |
2013 | 01/01/2013 |
2013W065 | 08/02/2013 |
2013W06 | 04/02/2013 |
2013050 | 24/01/2013 |
2013-02-08T09 | 08/02/2013 |
2013-02-08 09 | 08/02/2013 |
2013-02-08 09:30 | 08/02/2013 |
2013-02-08 09:30:26 | 08/02/2013 |
2013-02-08 09:30:26.123 | 08/02/2013 |
2013-02-08 24:00:00.000 | 09/02/2013 |
20130208T080910,123 | 08/02/2013 |
20130208T080910.123 | 08/02/2013 |
20130208T080910 | 08/02/2013 |
20130208T0809 | 08/02/2013 |
20130208T08 | 08/02/2013 |
2013-W06-5 09 | 08/02/2013 |
2013-039 09 | 08/02/2013 |
2013-02-08 09+07:00 | 08/02/2013 |
2013-02-08 09-0100 | 08/02/2013 |
2013-02-08 09Z | 08/02/2013 |
2013-02-08 09:30:26.123+07:00 | 08/02/2013 |
2013-02-08 09:30:26.123+07 | 08/02/2013 |
6 Mar 17 21:22 UT | 06/03/2017 |
6 Mar 17 21:22:23 UT | 06/03/2017 |
6 Mar 2017 21:22:23 GMT | 06/03/2017 |
06 Mar 2017 21:22:23 Z | 06/03/2017 |
Mon 06 Mar 2017 21:22:23 z | 06/03/2017 |
Mon, 06 Mar 2017 21:22:23 +0000 | 06/03/2017 |
6 Mar 17 00:00 UT | 06/03/2017 |
6 Mar 17 00:00:00 EST | 06/03/2017 |
6 Mar 2017 00:00:00 CST | 06/03/2017 |
06 Mar 2017 00:00:00 PST | 06/03/2017 |
Mon 06 Mar 2017 00:00:00 z | 06/03/2017 |
Mon, 06 Mar 2017 00:00:00 +9999 | 06/03/2017 |
Timestamps
Apsis One supports importing and storing Unix timestamps for Timestamp-type Attributes.
For a Timestamp-type Attribute — for example, a custom Member since Attribute — a value like Tue, 07 Mar 2017 04:22:23 +0300 is converted to 1488844800 (07 Mar 2017 00:00:00 +0000). The time of day is dropped during conversion.
Timestamps (e.g.
1599116184) are imported without milliseconds.Negative values are supported for dates before 1970.
Migrating from Apsis Pro?
If you're migrating from Apsis Pro to Apsis One, the accepted date format is ISO-8601 (YYYY-MM-DD).
A Date + Time (Unix) value is cut to just the date if it follows the
YYYY-MM-DDformat.
💡 In development. Support for 19700720, 1970.07.20, and 1970/07/20 as date formats in the Migration Wizard is coming soon.
File Import Wizard — supported encodings
When you save a Microsoft Excel file, or export data from another system, make sure the file is encoded as one of the following supported formats:
UTF-8 | Big5 | UTF-16BE | EUC-JP |
ISO-8859-1 | windows-1250 | UTF-16LE | EUC-KR |
ISO-8859-2 | windows-1251 | UTF-32BE | KOI8-R |
ISO-8859-5 | windows-1252 | UTF-32LE | IBM420 |
ISO-8859-6 | windows-1253 | ISO-2022-JP | IBM424 |
ISO-8859-7 | windows-1254 | ISO-2022-CN | GB18030 |
ISO-8859-8 | windows-1255 | ISO-2022-KR | Shift_JIS |
ISO-8859-9 | windows-1256 |
|
|
Limited values
Certain Events have a limited set of values. If you plan to build a Segment with one of these Events, the lists below show exactly what to target.
Bounce codes and reasons
💡 Example. To include all Profiles with hard bounces, use Email – Bounce: bounceReason contains "Hard" in your Segment.
Code | Reason |
1004 | Other – Unknown |
2000 | Hard – General hard bounce |
2001 | Hard – Recipient email does not exist |
2002 | Hard – Domain name does not exist |
2004 | Hard – Closed email account |
3001 | Soft – Mailbox is full |
3002 | Soft – Recipient email server is currently too busy |
3003 | Soft – Email account is inactive |
4000 | Technical – General error |
4003 | Technical – Network error |
4007 | Technical – SPF authentication error |
4008 | Technical – DMARC authentication error |
4009 | Technical – DKIM authentication error |
9999 | Soft – Unknown |
Exit flow Event reasons
💡 Example. To include all Profiles who exited a flow when they finished it, use Marketing Automation – Exit flow: Reason equals "Finished" in your Segment. This however requires that you always use an exit node in your flows.
Reason | What it means |
Finished | The Profile reached the Finish Node and completed the flow. |
MatchTags | The Profile matched the Tag specified in the Flow Settings under Terminate. |
OverLimit | The Profile entered the flow the maximum number of times specified in the Flow Settings. |
CheckedProfile | The Profile didn't pass a Check Profile node, and the path for those who don't match was the final node of the flow. |
Reset | The Profile was removed from the flow when it was paused and reactivated. |
NodeDeleted | The Profile was in a node that was deleted, and left the flow. |
MissingConsent | The Profile is missing consent for the node's given channel. |
TooManyHardBounces | The Profile's email address bounced enough times to reach the bounce limit. |
MissingEmail | The Profile doesn't have an email Attribute, which the email node requires. |
MissingSMS | The Profile doesn't have an SMS Attribute, which the SMS node requires. |
ProfileNotRetrieved | A technical error prevented the email node from finding the Profile. Contact support. |
ProfileLocked | The Profile was locked in Audience. |
AttributeNotFound | The Profile doesn't have the Attribute needed to complete the email node. |
AttributeValueNotFound | The Profile doesn't have the Attribute value needed to complete the email node. |
UnknownReason | Unknown reason. Contact support. |
WebhookError | The Webhook node returned an error from a failed request. |
InsufficientCredits | Your Apsis One account doesn't have enough SMS credits, so the Profile left in the SMS node. |
Bounce | The Profile's email address or mobile number bounced in the Email or SMS node. |
Timeout | The Profile didn't perform the action specified by the Wait for Event node, and the no-action path was the final node of the flow. |
Achievement type
The Achievement Event type has limited values — either MQL, SQL, or PQL. Read more about Achievement Events →
Other
Event dates: ISO-8601 (
YYYY-MM-DD).Magento Attributes and Events: Unix time.