EPICA Destination

EPICA is the world’s first Prediction-as-a-Service platform. Powered by AI, EPICA captures, processes and analyses online data sources to accurately predict customer behavior. EPICA provides predictive analytics for growth marketers, leveraging machine learning to automate audience insights and recommendations.

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

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

Getting Started

The first step is to make sure EPICA supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “EPICA” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your EPICA Account settings.

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()

Page calls will be sent to EPICA as a 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"];

Screen calls will be sent to EPICA as a screen.

Identify

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

analytics.identify('userId123', {
  email: 'john.doe@segment.com',
  firstName: 'Peter',
  lastName: 'Gibbons',
  phone: '888-8880'
});

Identify calls will be sent to EPICA as an identify event. Traits are optional but EPICA recommends the following:email,firstName,lastName andphone.

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', {
  color: 'Red',
  size: 'Large'
})

Track calls will be sent to EPICA as a track event and can be seen populated in the Data Platform > Personas section of EPICA admin panel, which includes unified profiles across a single customer journey.

There are two types of Personas:

  • Anonymous - events triggered by a visitor who only has an anonymousId
  • Identified - events triggered by an identified user with a userId, email or phone

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 via your Segment dashboard without having to touch any code.

API Key

You can find your API key in your account settings page

Adding EPICA to the integrations object

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


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!