--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-epsilon#article headline: Epsilon (Actions) Destination description: Send mobile app, e-commerce, and custom events from Segment to the Epsilon (Actions) Destination for data-driven, personalized marketing. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-epsilon inLanguage: en dateModified: 2026-06-10T17:19:57.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Epsilon (Actions) Destination ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Epsilon (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Epsilon](https://www.epsilon.com) is a global advertising and marketing technology company that provides data-driven marketing solutions, helping brands create personalized customer experiences across all channels. This destination is maintained by Epsilon. For any issues with the destination, [contact their Support team](mailto:support@epsilon.com). ## Getting started To connect the Epsilon (Actions) destination: 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for *Epsilon*. 2. Select *Epsilon (Actions)* and click **Add Destination**. 3. Select an existing Source to connect to Epsilon (Actions). 4. Contact Epsilon support to obtain your **Company ID** and **Company Magic** credentials. 5. Enter the **Company ID** and **Company Magic** in the Epsilon destination settings in Segment. ## Destination Settings | Field | Description | Required | Type | | ------------- | -------------------------------------------------------- | -------- | ------ | | Company ID | Your Company ID. Contact Epsilon support for assistance. | Yes | string | | Company Magic | Company Magic. Contact Epsilon support for assistance. | Yes | string | ## Available Presets Epsilon (Actions) has the following presets | Preset Name | Trigger | Default Action | | --------------------------- | ----------------------------------------- | --------------------- | | First App Open/App Download | Event event = "Application Installed" | Standard Fields Event | | Transaction Complete | Event event = "Order Completed" | Standard Fields Event | | Sign in/Create Account | Event event = "Signed In" | Standard Fields Event | | App Open | Event event = "Application Opened" | Standard Fields Event | | Add to Cart | Event event = "Product Added" | Standard Fields Event | | Add to Saved List | Event event = "Product Added To Wishlist" | Standard Fields Event | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Epsilon-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Standard Fields Event](#standard-fields-event) ### Standard Fields Event Sync an event containing standard fields only to Epsilon Standard Fields Event is a **Cloud** action. The default Trigger is `type = "track"` | Field | Description | Required | Type | | ------------------------------ | ---------------------------------------------------------------------------------------------- | -------- | ------ | | Cache Buster | Unique identifier for the message. Used for cache busting. | Yes | STRING | | App ID / Namespace | The namespace of the Mobile App. | Yes | STRING | | Event Name | The name of the event to send to Epsilon. | Yes | STRING | | App Version | The version of the Mobile App. | Yes | STRING | | Form ID | Form ID used in Epsilon’s system to identify app visits vs. conversions. | Yes | STRING | | Promo ID | Promo ID used in Epsilon’s system to identify the promotion associated with the event. | No | STRING | | Identifiers | Unique identifiers for the user. | Yes | OBJECT | | Device Type | Type of the device (e.g., iOS, Android). | Yes | STRING | | Department | Department of the product. | No | STRING | | Category | Category of the product. | No | STRING | | Sub Category | Sub-category of the product. | No | STRING | | Product ID | Unique identifier for the product | No | STRING | | Brand | Brand of the product. | No | STRING | | Universal Product Code | Manufacturer Universal Product Code for the product. | No | STRING | | Manufacturer Model Part Number | Manufacturer Model Part Number for the product. | No | STRING | | Transaction ID | Unique identifier for the transaction. | No | STRING | | Conversion Value | Contains the total purchase price in decimal format. Do not include any tax or shipping costs. | No | NUMBER | | Items Purchased | An array of all items in the conversion. | No | OBJECT | | Currency | Currency of the transaction. Use ISO 4217 currency codes (e.g., USD, EUR). | No | STRING | | Order Type | Differentiate between types of online purchases (Delivery, Pickup, etc.) | No | STRING | | Store Location | For Pickup conversions, denote the store location of the pickup. | No | STRING | | Custom Event Name | The name of the custom event to send to Epsilon. | No | STRING | | Custom Properties | Add custom properties to the event. | No | OBJECT | ## Supported events The Epsilon destination supports the following predefined event types: ### Mobile app events | Event | Details | | --------------------------- | ----------------------------------------------------------- | | First App Open/App Download | Tracks when a user first opens or downloads your mobile app | | App Open | Tracks subsequent app opens | | Sign in/Create Account | Tracks user authentication events | ### E-commerce events | Event | Details | | --------------------- | -------------------------------------------- | | Shop Department View | Tracks when users view product departments | | Shop Subcategory View | Tracks when users view product subcategories | | Shop Product View | Tracks individual product views | | Add to Favorites | Tracks when users add products to favorites | | Add to Saved List | Tracks when users add products to wishlists | | Add to Cart | Tracks when users add products to their cart | | Transaction Complete | Tracks completed purchases | ### Custom events | Event | Details | | ------------ | --------------------------------------------------------------- | | Custom Event | Allows you to send any custom event with flexible field mapping | ## Event data structure All events sent to Epsilon include: ### Standard fields | Field | Details | | ---------------------------- | ------------------------------------------ | | Company ID (`dtm_cid`) | Your Epsilon company identifier | | Company Magic (`dtm_cmagic`) | Your Epsilon authentication token | | Form ID (`dtm_fid`) | Used to identify app visits vs conversions | | App ID | Mobile app namespace | | App Version | Version of your mobile app | | Device Type | iOS or Android | ### User identifiers | Field | Details | | -------------- | ------------------------------------------------------ | | Device ID | Mobile device identifier (IDFV or Google App Set ID) | | Advertising ID | Mobile advertising identifier (IDFA or Google Ad ID) | | User Agent | Device user agent string | | IP Address | User's IP address | | Email Hash | Hashed email address (automatically hashed by Segment) | | Mobile Hash | Hashed phone number (automatically hashed by Segment) | | User ID | Your internal user identifier | ### Product information (for applicable events) | Field | Details | | ------------ | ------------------------- | | Department | Product department | | Category | Product category | | Sub Category | Product subcategory | | Product ID | Unique product identifier | | Brand | Product brand | | UPC | Universal Product Code | | MPN | Manufacturer Part Number | ### Transaction information (for conversion events) | Field | Details | | ---------------- | --------------------------------------------------------------- | | Transaction ID | Unique order identifier | | Conversion Value | Total purchase amount (excluding tax/shipping) | | Currency | ISO 4217 currency code (for example, USD, EUR) | | Order Type | Type of order (such as, Delivery, Pickup) | | Store Location | For pickup orders, the store location | | Items | Array of purchased items with quantities, prices, and discounts | ## Data processing ### Email and phone hashing Segment automatically hashes email addresses and phone numbers using SHA-256 before sending them to Epsilon. You can provide either hashed or unhashed values - Segment will ensure proper hashing. ### Device-specific mapping The destination automatically maps device identifiers based on the device type: * **iOS devices**: Uses `idfa` for device ID and `idfv` for vendor ID * **Android devices**: Uses `google_play_id` for device ID and `google_app_set_id` for vendor ID ### Custom properties For custom events, you can include additional properties that will be passed through to Epsilon alongside the standard fields. ## Preset mappings The destination includes preset mappings for common e-commerce events: | Segment Event | Epsilon Event | Description | | ------------------------- | ------------- | ----------------------- | | Application Installed | firstOpen | First app open/download | | Application Opened | appOpen | Subsequent app opens | | Signed In | signIn | User authentication | | Product Added To Wishlist | addSavedList | Add to wishlist | | Product Added | cart | Add to cart | | Order Completed | conversion | Purchase completion | These presets automatically map the appropriate Segment event properties to Epsilon's expected field structure. ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/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.