Getting Started Overview
DriveMetaData works best when teams set it up around a clear operating model: what data enters the platform, how identity is resolved, which events matter, which reports are trusted, and which audiences are safe to activate.
Use this overview to align stakeholders before the first workspace is configured.
Recommended setup sequence
-
Define business goals. Decide whether the first rollout is focused on acquisition measurement, customer analytics, lifecycle activation, fraud prevention, or a combined workflow.
-
List data sources. Identify the systems that contain user behavior, campaign exposure, transactions, subscriptions, support events, and offline conversions.
-
Agree on identity rules. Document the identifiers available in each source, such as user ID, device ID, email hash, CRM ID, order ID, or anonymous browser ID.
-
Standardize events. Choose the events and properties that will power reporting and segmentation. Prioritize high-value actions such as signup, product view, add to cart, checkout, purchase, subscription, cancellation, and refund.
-
Configure reporting views. Define the funnel, retention, campaign, cohort, and KPI views that teams will use every week.
-
Launch controlled activations. Start with low-risk audiences such as abandoned cart, high-intent visitors, new signups, or dormant customers before expanding to automated journeys.
Team responsibilities
| Team | Owns |
|---|---|
| Marketing | Campaign taxonomy, attribution review, activation goals, channel handoff |
| Growth | Experiment design, funnel health, conversion rate, audience performance |
| Product | Lifecycle events, feature usage, retention analysis, customer behavior questions |
| Analytics | Data validation, KPI definitions, identity logic, reporting QA |
| Engineering | SDK, connector, consent, and event implementation support |
Minimum viable launch
A useful first launch usually includes:
- One production workspace.
- One primary business objective.
- A small set of approved events.
- Two or three connected data sources.
- One trusted funnel report.
- One trusted retention report.
- One activation audience with manual review before launch.
Start with fewer events and higher confidence. A small trusted dataset is more useful than a large event stream with unclear definitions.
Common setup risks
- Campaign names differ between channels, making attribution hard to compare.
- Events fire at different points in the user journey across web and app.
- Offline conversions arrive late and are not clearly timestamped.
- CRM fields contain duplicate or stale customer identifiers.
- Activation audiences are built before consent and suppression rules are confirmed.
Use the quick start when you are ready to configure the first workspace.