Scuba Analytics Destination

Scuba Analytics’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 Scuba Analytics. For any issues with the destination, contact the Scuba Analytics Support team.

Getting Started

To set up the Scuba Analytics 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 Scuba Analytics from the Segment portal select Scuba Analytics 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 Scuba Analytics with the associated method as an attribute of the event.

Page

If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:

analytics.page()

Screen

If you’re not familiar with the Segment Specs, take a look to understand what the Screen method does. An example call would look like:

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

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. Identify methods can be used with Actors properties and Flow Properties in Scuba Analytics to update the associate with the user in the Identify method. An example call would look like:

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

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.