Localytics: Import Profiles
Import profile data from Localytics to add mobile user data to user profiles in Lytics.
Integration Details
- Implementation Type: Server-side.
- Implementation Technique: REST API.
- Frequency: One-time batch, or daily continuous import.
- Resulting Data: Full user profiles from Localytics.
This integration utilizes the the Localytics Profile Export API. You will need to set up the ProfileDB export in the Localytics UI as described in the linked doc. Once the export is started, and then the import started in Lytics, the job will:
- Import the Localytics ProfileDB export file.
- Every day at 16:00 UTC, if Profile Changes is selected.
- change logs from Localytics for the prior 24 hours are imported
- on the first of the month a full profile import is run instead of the change logs
- If Profile Changes is not selected, the full profile export will be imported every day.
- Ingested profile data is written to the
localytics_profilesdata stream in Lytics.
Fields
The following fields are included in the default mapping of the localytics_profiles stream:
| Source Field | Lytics Default Field | Description | Type |
|---|---|---|---|
_ll.google_advertising_id unique id | google_aid | Current Google Advertising ID | string |
_ll.advertising_id unique id | idfa | Current IDFA | string |
_ll.raw_customer_id unique id | localytics_customer_id | Localytics Customer ID | string |
$email unique id | string | ||
| _ll.carrier | localytics_device_carrier | Localytics Device Carrier | string |
| _ll.device_uuid | localytics_device_id | Localytics Device ID | string |
| _ll.device_timezone | localytics_timezone | Localytics Device Timezone | int |
| _ll.language | localytics_language | Localytics Language | string |
| _ll.limit_advertising | localytics_limit_advertising | Localytics Limit Advertising | boolean |
| _ll.type | localytics_type | Localytics Event Type | string |
| _ll.os_ver | localytics_os_version | Localytics OS Version | string |
| _ll. platform | localytics_platform | Localytics Platform | string |
| _ll.push_status | localytics_push_status | Localytics Push Status | string |
| _ll.user_type | localytics_user_type | Localytics User Type | string |
| _ll.last_session_date | localytics_last_session_date | Localytics Last Session Date | date |
| $first_name | first_name | First Name | string |
| $last_name | last_name | Last Name | string |
| $full_name | full_name | Full Name | string |
Configuration
Follow these steps to set up and configure an import job for Localytics in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Localytics.
- Select the Import Audiences job type from the list.
- Select the Authorization you would like to use or create a new one.
- Complete the configuration steps for your job.
- In the ProfileDB ID numeric field enter the ID of the Localytics Profile DB to pull profile data from. See Localytics documentation for details.
- Select the Keep Updated checkbox to continuously import Localytics profiles every day. Uncheck to run import once.
- From the Update Type input select whether to pull from the complete profile export or the profile changes from Localytics. To use profile changes, a profile changes export must be started in Localytics. Profile changes will result in less data being ingested into Lytics, and may lead to faster profile updates. Select Full Profile DB if profile changes is not available.
- Click Start Import.
Profile data should appear in the localytics_profile stream in the Data Streams section of Lytics within an hour, and the mapped user fields above will be added to the user profiles as new profile data is imported.