Entirely is a group and open ecosystem of specialized marketing-technology companies. Its composable approach lets organizations combine portfolio products with their existing stack instead of requiring every marketing function to run in one application.
Within this ecosystem, Elaine is responsible for customer engagement: it activates customer and context data through personalized messages, campaign automation, transactional communication, delivery, and engagement analytics.
Products in the Entirely portfolio
| Product | Primary role | Relationship to Elaine |
|---|---|---|
| Elaine | Customer engagement, campaign automation, personalized and transactional messaging, and engagement analytics. | Activates audiences, content, events, and recommendations through customer communication. |
| MARMIND | Marketing Resource Management (MRM) for planning campaigns, budgets, resources, workflows, and performance. | Can provide the planning and orchestration context for campaign work executed in Elaine. |
| Censhare | Product Information Management (PIM), Digital Asset Management (DAM), and content management. | Can supply governed product information and approved digital assets for Elaine content. |
| Facelift | Social media and communication orchestration, including publishing, community management, collaboration, and analytics. | No supported Elaine integration is documented in this public knowledge base at present. |
| epoq | AI-supported e-commerce personalization, including product recommendations, search, and guided selling. | Recommendation results can be used as product suggestions in personalized Elaine messages. |
Documented joint scenarios
- Plan and control campaign work in MARMIND and initiate message creation in Elaine.
- Use Censhare product data and make approved Censhare assets available to Elaine editors.
- Insert epoq recommendation results into personalized Elaine messages.
- Use Entirely Intent Signals from web and app touchpoints to trigger or steer configured campaign activities in Elaine.
Integration boundaries
Entirely describes a portfolio and integration approach, not a single shared data model or automatic connection between every product. Available objects, synchronization direction, identity matching, latency, permissions, and licensing depend on the specific integration. Treat each joint scenario as an architecture decision and confirm its supported scope before implementation.