1. A customer visits a website and browses a few products.
   
2. The customer adds a product to their cart and proceeds to checkout.
   
3. The customer enters their personal information and completes the purchase.
   
4. ReBid CDP will capture all of these events and associate them with the customer's profile. This profile will now contain information about the customer's interests, activities, and personal information.
   
5. ReBid CDP can then use this information to personalize the customer's experience and deliver more relevant content and offers. 
   

ReBid CDP Profile Fields

1. id: The profile ID, represents a unique identifier for each profile.
   
2. ids: A list of previous profile IDs and IDs from external systems, used to reference the same profile stored in external systems.
   
3. metadata: Contains metadata information such as time, time zone, visits, and auxiliary metadata.
   
4. aux: Additional auxiliary metadata associated with the profile.
   
5. time: Sub-field that stores various time-related information.
   
6. insert: Represents the timestamp of the profile insertion.
   
7. update: Indicates the timestamp of the profile update.
   
8. segmentation: Stores the segmentation timestamp.
   
9. visit: Contains visit-related details such as the last visit timestamp, current visit timestamp, visit count, and time zone (tz).
   
10. data: Holds the actual profile data with a predefined structure used for reporting and describing personal information.
    
11. media: Contains media-related information such as images, webpages, and social media handles.
    
12. pii: Stores personally identifiable information, including attributes like first name, last name, birthday, language preferences, gender, education level, civil status, and physical attributes.
    
13. identifier: Includes various identifiers associated with the profile, such as ID, badge, passport, credit card, token, and coupons.
    
14. contact: Stores contact information like email, phone number, messaging app handles, and address details.
    
15. job: Contains job-related information like position, salary, job type, company details (name, size, segment, country), and department.
    
16. preferences: Represents profile preferences, including purchases, colors, sizes, devices, channels, payments, brands, fragrances, and other preferences.
    
17. devices: Stores device-related information, including device names and geographic details like country, county, city, latitude, longitude, and postal code.
    
18. metrics: Includes various metrics associated with the profile, such as lifetime value (LTV), etc.
    
19. loyalty: Contains loyalty-related information, such as loyalty codes and loyalty card details (ID, name, issuer, points, expiration date).
    
20. stats: Additional statistics associated with the profile, such as the number of emails sent/received, SMS count, and error count.
    
21. traits: A field where custom profile attributes/properties can be stored. It allows storing any custom data that does not fit into the predefined profile data schema.
    
22. collections: Holds collections related to the profile, allowing the storage of one-to-many relationships with other objects (e.g., purchases, devices).
    
23. segments: Represents a set of segments to which the profile belongs. The field truncates the name if it exceeds 64 characters.
    
24. consents: Stores a list of consents given by the profile.
    
25. active: Indicates whether the profile is active or inactive from a business perspective. Profiles that have not had any events for a year can be marked as inactive.
    
26. interests: Contains key-value pairs representing the interests of the profile. For example, { "sports": 0.86 } indicates that the person is 86% interested in sports.
    
27. aux: Stores auxiliary data related to conflicts or data discrepancies, allowing temporary preservation of obsolete or migrating data.
    
28. trash: Holds data that should be removed at some point. It can be used to temporarily store obsolete or data created during the migration process.
    
29. misc: A field used to store data that does not need to be searched or indexed. It can include operational flags or data that does not require grouping or indexing.