Epsilon (Actions) Destination
Epsilon 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.
To connect the Epsilon (Actions) destination:
- From your workspace's Destination catalog page search for Epsilon.
- Select Epsilon (Actions) and click Add Destination.
- Select an existing Source to connect to Epsilon (Actions).
- Contact Epsilon support to obtain your Company ID and Company Magic credentials.
- Enter the Company ID and Company Magic in the Epsilon destination settings in Segment.
Your Company ID. Contact Epsilon support for assistance.
Company Magic. Contact Epsilon support for assistance.
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 |
Build your own Mappings. Combine supported triggers with the following Epsilon-supported actions:
Mapping limits per destination
Individual destination instances support a maximum of 5 mappings.
Sync an event containing standard fields only to Epsilon
Standard Fields Event is a Cloud action. The default Trigger is type = "track"
Unique identifier for the message. Used for cache busting.
The namespace of the Mobile App.
The name of the event to send to Epsilon.
The version of the Mobile App.
Form ID used in Epsilon’s system to identify app visits vs. conversions.
Optional
Promo ID used in Epsilon’s system to identify the promotion associated with the event.
Unique identifiers for the user.
Type of the device (e.g., iOS, Android).
Optional
Department of the product.
Optional
Category of the product.
Optional
Sub-category of the product.
Optional
Unique identifier for the product
Optional
Brand of the product.
Optional
Manufacturer Universal Product Code for the product.
Optional
Manufacturer Model Part Number for the product.
Optional
Unique identifier for the transaction.
Optional
Contains the total purchase price in decimal format. Do not include any tax or shipping costs.
Optional
An array of all items in the conversion.
Optional
Currency of the transaction. Use ISO 4217 currency codes (e.g., USD, EUR).
Optional
Differentiate between types of online purchases (Delivery, Pickup, etc.)
Optional
For Pickup conversions, denote the store location of the pickup.
Optional
The name of the custom event to send to Epsilon.
Optional
Add custom properties to the event.
The Epsilon destination supports the following predefined event types:
| 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 |
| 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 |
| Event | Details |
|---|---|
| Custom Event | Allows you to send any custom event with flexible field mapping |
All events sent to Epsilon include:
| 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 |
| 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 |
| 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 |
| 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 |
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.
The destination automatically maps device identifiers based on the device type:
- iOS devices: Uses
idfafor device ID andidfvfor vendor ID - Android devices: Uses
google_play_idfor device ID andgoogle_app_set_idfor vendor ID
For custom events, you can include additional properties that will be passed through to Epsilon alongside the standard fields.
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.
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.