Objects are designed to help businesses store and manage different data types. Whether you need to organize customer details, product information, service requests, or any other data point, they provide a structured and efficient solution.
Objects are incredibly useful, letting you store any type of data you need. For example, if you're using an order fulfillment software like ShipHero, you can create a specific object called "Shipment" to keep all the shipment details organized. This could include details like SKU, Product Name, Inventory Bin, Barcode, Quantity, etc
With all this detailed information stored, you can run much more effective marketing campaigns. For instance, after an order has been delivered, you could send a targeted email asking your customer to leave a review about their experience. By applying segmentation to the data in Objects, you can get the most accurate segments, making your campaigns even more targeted. This way, you can engage with your customers more effectively and achieve better results from your campaigns.
Types of Objects
ZEPIC offers standard objects like Contacts and Companies, but users can also create custom cubes for Orders, Products, Tickets, and more. This flexibility is important as it allows you to tailor your data management approach to suit your needs and ensures scalability and adaptability as your operations evolve.
Creating an Object in ZEPIC
The intuitive drag-and-drop interface makes creating custom Objects in ZEPIC a breeze. Marketers can independently create Objects without relying on engineering teams, streamlining the data structuring process and saving valuable time.
To create an Object in ZEPIC, follow the below steps:
Navigate to Objects from the left nav bar.
Alternatively, you can also go to Settings from the left nav bar, and select Objects under Data Management.
Your account includes three default objects: Contact, Company, and Visitors.
Please note that while the Visitors object is not visible in the UI, you can still use its data when creating segments.
Click on the Create Custom Object
Provide a name for your Object. The API name and plural form will be generated automatically, but you can customize them by clicking the Edit button. You can also add a description of your object.
Click on to proceed.
You can easily drag and drop various fields into your Object.
For instance, if you are creating an Object named "Invoices," you can add a Single Line Field to capture the invoice name. Continue by adding a Number Field for the invoice number, an Email Field for the customer's email address, and so on. This flexibility allows you to tailor the object precisely to your needs.After configuring the fields, you can assign a display name. For example, you might choose "Invoice Number" as the display name. This can be done quickly by selecting the desired field from the dropdown menu in the hamburger icon.
You can also map an avatar image when bringing in data from Connectors.
Click onto proceed. You can review the different layouts here—view how your cube’s data would look like in the list view, card view and the details view.
your configuration.
You can now start powering your campaigns with Segments created from your Cube.
Supported Properties in ZEPIC
Text (Single line,Multiline): Stores textual information.
Email: Manages email addresses for communication purposes.
Phone: Stores contact phone numbers.
Address (Compound Fields): The Address field in ZEPIC is a compound field that combines Street, City, State, Country, and Zip Code. This structure allows businesses to manage complete address details efficiently within a single field, improving data accuracy and user experience.
Dropdown: Offers predefined options for selection.
Date, DateTime: Captures dates and times.
Lookup: Establishes relationships between Cubes.
Lifecycle Properties: Tracks stages or statuses of objects.
URL: Stores website links or references.
Checkbox: Captures binary (yes/no) data.
Sections: Organizes related fields within a Cube.
Note: Once an API name is assigned to a Cube in ZEPIC, it remains unchanged. This ensures consistency and reliability in data integrations and system interactions.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article