Alooma can read and replicate all of the Localytics event data from your Localytics account. This allows you to merge client usage data with other data in your data warehouse.
Alooma provides a way for you to pull your Localytics data using Localytic's export to S3 support. According to your company/user name and your app's key, Localytics will export your data to the following S3 path:
Once Localytics Export is set up, every hour Localytics will write a new file containing events. Alooma monitors the path in S3 and picks up these files as they appear.
You can connect Localytics to Alooma in just a few steps:
Add your Localytics input from Alooma's plumbing screen.
Give your input a name. The name will appear in the plumbing screen, and will name the events that the input emits.
Provide the following access info:
AWS Access Key ID (20 uppercase characters). Found under Users in your dashboard.
AWS Secret Access Key (40 base64 characters). Where is my access key?
Bucket Name (between 3 and 63 lowercase characters)
Company name (from the Settings/Organization page)
App Key (the app key of the app you're importing from, which can be found on the Localytics Settings / Apps page)
Under advanced options you can choose which dates to pull data from:
All time will pull all the data from your bucket, and will continue to do so forever.
A date span pulls files written between the given dates, inclusive. If you select the date span option and don't specify dates, the input will only pull files written after the input was created
Keep the mapping mode to the default of OneClick if you'd like Alooma to automatically map the Localytics events directly to your target data warehouse. Otherwise, they'll have to be mapped manually from the Mapper screen.
That's it! You're ready to integrate Localytics data into Alooma!