Context
Data Sources
Crosshatch integrates with popular platforms to provide a unified view of user activities across different applications. This page outlines the available data sources, the types of events they provide, and how frequently they're updated.
Core data sources
These platforms are directly integrated with Crosshatch and provide a range of user activity data.
| Source | Key Events | Data Type | Update Frequency | Description |
|---|---|---|---|---|
plaid | purchased | track | 15 minutes | Financial transactions and merchants |
google-mail | purchased, confirmed | derived | 5 minutes | Activities detected in email content |
google-calendar | confirmed | track | 3 hours | Scheduled events and appointments |
fitbit | exercised, slept | track | 12 hours | Fitness activities and sleep tracking |
strava | exercised | track | 12 hours | Detailed exercise and route data |
Email-derived activities
The
google-mailsource discovers activities from email content, providing context from many services without requiring direct integration. Here are common sources found in emails:
| Source Type | Events | Example Data |
|---|---|---|
| Retail | purchased | Amazon, Walmart, Instacart, Target, Best Buy |
| Restaurants | confirmed | OpenTable, Resy, Tock, restaurant confirmations |
| Travel | confirmed | Hotel bookings, flight confirmations, car rentals |
| Entertainment | confirmed | Event tickets, reservations, bookings |
| Services | confirmed | Appointments, subscriptions, memberships |
All email-derived activities are updated every 5 minutes and marked with
type: "derived"to indicate they were extracted from unstructured content.
Event types
Each activity in the Context Layer is represented by an event type that describes the user action.
purchased
Represents a completed transaction or purchase made by the user, typically from financial transactions.
Available in: Plaid, Google Mail (derived) Key data points:- Merchant name and location - Transaction amount and currency - Purchase date and time - Categories and item details (when available)
confirmed
Represents a confirmation of an upcoming event, reservation, booking, or purchase.
Available in: Google Calendar, Google Mail (derived) Key data points:- Venue or service name - Reservation/event date and time
- Location details - Confirmation details and reference numbers
Note: Purchases can appear in both
purchasedevents (from financial transactions) and
confirmedevents (from purchase confirmation emails). The key difference is that
purchasedevents represent completed transactions with verified amounts, while purchase
confirmedevents represent order confirmations that may occur before the financial transaction.
exercised
Represents a physical activity or workout.
Available in: Fitbit, Strava Key data points:- Activity type (run, cycle, swim, etc.) - Duration and distance - Start and end time - Location (for outdoor activities) - Performance metrics (pace, calories, etc.)
slept
Represents sleep activity and patterns.
Available in: Fitbit Key data points:- Sleep start and end time - Duration and quality measures - Sleep stages when available
Data freshness
Different data sources update at different frequencies:
- High frequency (5-15 min): Email-derived activities (5 min) and financial transactions (15 min)
- Medium frequency (3 hours): Calendar events
- Lower frequency (12 hours): Fitness and activity data
These update cadences balance data freshness with system performance.
Upcoming integrations
Crosshatch is continuously expanding its data source integrations:
- Q4 2024: Whoop, Oura Ring, Reddit, YouTube
- Q1 2025: Google Maps*, Google Chrome*, Apple Music
- Backlog: Spotify, Pinterest, Eight Sleep, Apple Health
*EU users only
Special considerations
- Receipt details: Itemized receipts may be available in the
order_summary
field for some purchases detected in emails - Data variability: The level of detail available varies by source and specific content
- User permissions: All data access requires explicit user consent through Crosshatch Link
- Historical data: When users first connect, Crosshatch syncs approximately 6 months of historical data where available
Next steps
- See data mappings to understand how sources are transformed
- Learn how to query this data effectively
- Explore the schema for field definitions