What data should I use with Wondaris?

The data you put into Wondaris or expose via OYD mode, really depends on your use cases, however there are a few things that need to be considered to allow you to do various activations.

As a general rule of thumb, consider putting as much data about your customers into Wondaris as possible (including behavioural data), this allows you to expand your use cases over time with less need to go back and add more data. This of course must be balanced with legal requirements for privacy, as well as information security requirements (ie: data minimisation strategies).

For marketing using customer match mechanisms, you will need to check the destinations you are sending to, to ensure you have all the required fields. Commonly, DSPs require at least some sort of hashed identifier, like email or phone number, appropriately formatted prior to hashing (Wondaris will do the hashing and some preparation of the identifiers prior to hashing - for more info, ask our support team - support@wondaris.com or your implementation partner).

Data Set: Customer customer

• Mandatory Fields:

  • Unique Identifier (e.g., Customer ID)

  • Hashed Email Address

• Other Suggested Fields:

  • First Name (optional: Last Name)

  • Phone Number

  • Billing Address

  • Shipping Address

  • Preferred Language

  • Loyalty Program Membership (if applicable)

  • Customer Lifetime Value (optional)

  • Any other customer attributes used for segmentation (e.g., demographics, interests)

Data Set: Transaction event

• Mandatory Fields:

  • Transaction ID

  • Order Date/Time

  • Order Total

  • Customer identifier (to link to the customer data)

• Other Suggested Fields:

  • Items Purchased (product ID, quantity, price)

  • Currency

  • Payment Method

  • Discounts Applied

  • Return/Exchange Information

  • Shipping Method

Data Set (Optional): Event event

• Mandatory Fields:

  • Event Type (e.g., Product Viewed, Cart Abandoned, Purchase Completed)

  • Event Timestamp

  • Customer identifier/s (to link to the customer data)

• Other Suggested Fields:

  • Product ID (if applicable)

  • Category (if applicable)

  • Campaign ID (if applicable)

  • Referral Source (if applicable)

• Data Set: Customer (same as Omni-channel Commerce)

• Data Set: Transaction (same as Omni-channel Commerce)

• Data Set: Event (same as Omni-channel Commerce)

• Additional Considerations:

  • Include website activity data like page views, searches, and clickstream behaviour.

Data Set: Customer (same as Omni-channel Commerce)

• Additional Suggested Fields:

  • Account Number(s)

  • Account Type(s)

  • Product Subscriptions (e.g., credit cards, loans)

Data Set: Transaction

• Mandatory Fields:

  • Transaction Date/Time

  • Transaction Type (e.g., Deposit, Withdrawal, Payment)

  • Amount

  • Currency

  • Customer identifier (to link to the customer data)

• Other Suggested Fields:

  • Account Involved

  • Merchant Information (if applicable)

Data Set: Event

• Mandatory Fields:

  • Event Type (e.g., Login, Bill Payment, Funds Transfer)

  • Event Timestamp

  • Customer identifier/s (to link to the customer data)

• Other Suggested Fields:

  • Login Device (if applicable)

  • Successful/Failed Attempts

Data Set: Customer (same as Omni-channel Commerce)

• Additional Suggested Fields:

  • Frequent Flyer/Loyalty Program Number(s)

  • Preferred Travel Destinations

  • Past Booking History (destinations, dates, travel style)

Data Set: Booking

• Mandatory Fields:

  • Booking ID

  • Booking Date/Time

  • Confirmation Number

  • Customer identifier (to link to the customer data)

• Other Suggested Fields:

  • Travel Dates & Duration

  • Destination City/Country

  • Accommodation Type & Details (hotel name, room type)

  • Transportation Details (airline, flight number, class)

  • Activities or Services Booked (tours, spa treatments)

  • Total Price Paid

  • Payment Method

Data Set: Event

• Mandatory Fields:

  • Event Type (e.g., Booking Confirmed, Itinerary Viewed, Trip Completed)

  • Event Timestamp

  • Customer identifier/s (to link to the customer data)

• Other Suggested Fields:

  • Review Submitted (rating, comments)

  • Customer Service Interaction (reason for contact)

  • Loyalty Program Points Earned/Redeemed

Data Set: Customer (same as Omni-channel Commerce)

• Additional Suggested Fields:

  • Subscription Information (type, start date, renewal status)

  • Preferred Content Genres (movies, music, books)

Data Set: Subscription

• Mandatory Fields:

  • Subscription ID

  • Subscription Type (e.g., monthly, annual)

  • Start Date

  • Renewal Date (if applicable)

  • Customer identifier (to link to the customer data)

Data Set: Viewing History

• Mandatory Fields:

  • Content Type (e.g., movie, TV show, song)

  • Content ID

  • Viewing Date/Time

  • Duration Watched (optional)

  • Customer identifier (to link to the customer data)

Data Set: Event

• Mandatory Fields:

  • Event Type (e.g., Content Added to Watchlist, Review Submitted, Playback Started)

  • Event Timestamp

  • Customer identifier/s (to link to the customer data)

• Other Suggested Fields:

  • Device Used for Viewing

  • Sharing Activity (shared content with others)

Data Set: Customer (same as Omni-channel Commerce)

• Additional Suggested Fields:

  • Mobile Phone Number

  • Service Plan Details (data allowance, call minutes)

Data Set: Usage Data

• Mandatory Fields:

  • Usage Period

  • Data Usage (MB, GB)

  • Voice Call Minutes

  • SMS/MMS Messages Sent (counts)

  • Customer identifier (to link to the customer data)

Data Set: Service Interactions

• Mandatory Fields:

  • Interaction Type (e.g., Phone Call, Online Chat)

  • Date/Time of Interaction

  • Customer identifier (to link to the customer data)

• Other Suggested Fields:

  • Reason for Contact

  • Resolution Status

Data Set: Customer

• Mandatory Fields:

  • Hashed Email Address

  • Hashed Phone Number

  • Hashed Postal Address (if applicable)

  • Customer ID

  • Date of Birth (if applicable)

  • Gender (if applicable)

• Other Fields:

  • Subscription Status (e.g., free, paid)

  • Subscription Start Date

  • Subscription End Date

  • Content Preferences (e.g., topics of interest, authors followed)

  • Engagement Metrics (e.g., articles read, videos watched, comments posted)

  • Social Media Handles

Data Set: Transaction

• Mandatory Fields:

  • Transaction ID

  • Customer ID

  • Transaction Date

  • Transaction Amount

  • Product Purchased (e.g., subscription, media item)

• Other Fields:

  • Payment Method

  • Discounts Applied

  • Renewals and Cancellations

Data Set: Events

• Mandatory Fields:

  • Event ID

  • Customer ID

  • Event Date

  • Event Type (e.g., page view, article read, video watched, comment posted, ad impression, ad click)

• Other Fields:

  • Content Viewed (e.g., article title, video name)

  • Device Type

  • Browser

  • IP Address

  • Referring URL

Data Set: Content

• Mandatory Fields:

  • Content ID

  • Content Title

  • Content Type (e.g., article, video, image)

  • Publication Date

• Other Fields:

  • Author

  • Category

  • Tags

  • Word Count (for articles)

  • Video Length (for videos)

Data Set: Media

• Mandatory Fields:

  • Media ID

  • Media Name

  • Media Type (e.g., display ad, video ad)

  • Placement (e.g., website, mobile app)

• Other Fields:

  • Media Size

  • Media Format

  • Target Audience

  • Cost per Impression (CPM)

  • Cost per Click (CPC)

Data Set: Customer

• Mandatory Fields:

  • Hashed Email Address

  • Hashed Phone Number

  • Hashed Postal Address (Service Address)

  • Customer ID

  • Service Account ID / Meter ID (Primary)

• Other Fields:

  • Service Address (Un-hashed, for internal use)

  • Mailing Address (if different from Service Address)

  • Date of Birth (if applicable)

  • Gender (if applicable)

  • Customer Segment (e.g., Residential, Small Business, Industrial)

  • Rate Plan/Tariff Name

  • Enrolment Date

  • Customer Lifetime Value (CLV)

  • Communication Preferences (e.g., email, SMS, postal)

  • Paperless Billing Flag

  • Any other customer attributes that you as a business use to segment customers

Data Set: Service Account / Premises

• Mandatory Fields:

  • Service Account ID / Meter ID

  • Customer ID (linked to the individual/household)

  • Service Address

  • Utility Type (e.g., Electric, Gas, Water)

• Other Fields:

  • Property Type (e.g., House, Apartment, Commercial)

  • Size of Premises (if available)

  • Number of Occupants (estimated, if available)

  • Heating/Cooling System Type (e.g., Gas, Electric Heat Pump)

  • Meter Installation Date

  • Service Status (e.g., Active, Suspended)

  • Grid/Service Area ID

Data Set: Usage / Meter Reads

• Mandatory Fields:

  • Service Account ID / Meter ID

  • Read Date / Time

  • Usage Quantity (e.g., kWh, Therms, Gallons)

  • Unit of Measure

• Other Fields:

  • Read Type (e.g., Actual, Estimated)

  • Interval Data (if smart meters are in use - a link to the granular data set)

  • Demand Peak (kW) (if applicable)

  • Temperature/Weather Data at Time of Read (if enriched)

Data Set: Billing / Transactions

• Mandatory Fields:

  • Bill/Transaction ID

  • Service Account ID

  • Bill Date

  • Bill Amount Due

  • Payment Status

• Other Fields:

  • Payment Date

  • Payment Method (e.g., Autopay, Credit Card, Mail)

  • Invoice Details (e.g., energy charges, taxes, fees)

  • Discounts or Credits Applied

  • Arrears/Debt Status

Data Set: Outage / Service Disruption

• Mandatory Fields:

  • Outage ID

  • Service Account ID / Location ID (Impacted)

  • Start Date / Time

  • Restoration Date / Time

• Other Fields:

  • Cause of Outage (e.g., Weather, Equipment Failure)

  • Estimated Number of Customers Affected

  • Customer-Reported vs. System-Detected Flag

  • Repair/Work Order ID