Interana Destination


Interana’s full stack solution allows you to visually explore trillions of data points from multiple data sets all in real time without the need for ETL, data aggregation, or writing any SQL.

This destination is maintained by Interana. For any issues with the destination, please reach out to their team.

NOTE: The Interana Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on September 24, 2019. If you are interested in joining their beta program or have any feedback to help improve the Interana Destination and its documentation, please let their team know!

Getting Started

To set up the Interana Integration, first you will need: The root URL for your destination cloud storage directory

  • For AWS S3 this is typically in the format or https://{your bucket}.{your region}.amazonaws.com/{your directory}
  • For Azure Blob Storage this is typically in formation of https://{your storage account name}.blob.core.windows.net/{your container} Credentials to access your cloud storage account
  • For AWS and S3 backed clusters you will need S3 credentials with write access to your bucket
  • For Azure and Blob Storage backed clusters you will need a Shared Access Signature with write access to your container To begin sending data to Interana from the Segment portal select Interana as a new destination.
    1. In the “API Key” field insert your Blob Shared Access Signature or your S3 credentials. For S3 credentials, comma separate the access key id & the secret access key in the format of “accessKeyId,secretAccessKey”
    2. In the “Bucket Container URL” field insert the URL for the cloud storage directory.
  • For S3: https://{your bucket}.{your region}.amazonaws.com/{your directory}
  • For Azure Blob Storage: https://{your storage account name}.blob.core.windows.net/{your container}
    1. In the “Platform” field insert “AWS” or “Azure” depending on the provider of your cloud storage.

Methods Supported

All methods will be tracked as a new event in Interana with the associated method as an attribute of the event.

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page()

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. Identify methods can be used with Actors properties and Flow Properties in Interana to update the associate with the user in the Identify method. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@segment.com'
});

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings from your Segment dashboard without having to touch any code.

API Key

Enter your S3 credentials or your Azure Blob Storage Shared Access Signature (SAS).

BUCKET CONTAINER URL

Enter URL for the AWS S3 bucket name or Azure Blob Storage container. (e.g. ‘https://my-storage.blob.core.windows.net/my-container’ ).

PLATFORM

Enter ‘AWS’ or ‘Azure’

Adding Interana to the integrations object

To add Interana to the integrations JSON object (for example, to filter data from a specific source), use one of the following valid names for this integration:

  • interana

  • Interana

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account