The same customer shows up as three different people in the CRM, email tool and analytics
We introduce a shared identifier and stitch profiles by email, phone and user ID. Duplicates merge under written rules you can review.
One customer profile across your site, ads and CRM
Your site, ad accounts, CRM and email tool each see a different version of the same customer. A customer data platform (CDP) merges them into one profile. You see where people came from and what they bought, and your automations and AI agents work from clean data.
Quote and schedule after your brief
Who it's for
- Online stores running Google and Meta ads with a separate CRM
- Businesses where customers touch the site, chat, phone and email
- Teams tired of exporting data to spreadsheets to see the full picture
- Companies preparing data for AI agents and personalised messaging
Problems we solve
I can't tell which ads actually bring buyers
We collect events from the site and CRM in one place and send purchases back to Google Ads and Meta. The ad platforms optimise on real revenue, not just clicks.
Every new tool means another developer ticket
Events are collected once in RudderStack or Segment. After that, any new destination is a configuration change, not a code change on the site.
We're worried about privacy compliance
We set up consent handling for GDPR and similar rules, strip fields you don't need, and document what is sent where.
What's included
- Audit of current tools and data: site, CRM, ads, email
- Tracking plan: which events and properties, and how they are named
- Platform choice: Segment, RudderStack Cloud or self-hosted RudderStack
- Source setup: website, app, CRM, forms, chat
- Identity resolution rules for merging profiles
- Event delivery to Google Ads, Meta, GA4 and your email platform
- Data warehouse connection (BigQuery, Snowflake or similar) when needed
- Consent management setup
- Data quality checks: test scenarios and duplicate control
- Documentation and a handover session on adding new events
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Start
A small store or service site with one or two data sources
- Tracking plan
- Site and CRM connection
- Events to GA4 and one ad platform
- Data quality checks
02
Customer Profile
A business with ads, CRM and email that needs one unified profile
- Everything in Start
- Identity resolution rules
- Google Ads, Meta and email platform connections
- Consent management
- Documentation
03
CDP + Warehouse
Multi-channel companies needing reporting, segments and AI-ready data
- Everything in Customer Profile
- Data warehouse (BigQuery or similar)
- Segments and ad audiences
- Data prepared for AI agents
- Team training
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Tracking plan
We agree the list of events and properties with you. This is the foundation, and mistakes here are costly later.
Implementation
We configure sources and destinations in the chosen platform. Every account is created under your company.
Testing
We run real scenarios: a lead, a purchase, a refund. We compare data across the CDP, CRM and analytics.
Pilot with a KPI
We agree a measurable target up front, such as the share of events that carry a complete customer profile, and check it during the pilot.
Handover
You get documentation, access and a short training session. The system then runs without us.
Scope and limits
- We don't promise a CDP will raise sales by itself: it gives you clean data, and the decisions stay with you
- We can't merge profiles without an identifier: if a visitor never leaves an email or phone, their anonymous history may stay separate
- We can't recover data that was never collected: profiles fill up from launch day onward
FAQ
Does a small business need a CDP?
Often not. With one site and one CRM, well-configured analytics is enough. A CDP pays off when you have several data sources that don't match. We'll tell you honestly during the audit whether you need one.
Segment or RudderStack: which should I pick?
Segment is a hosted service with many integrations, but its price grows with event volume. RudderStack is usually cheaper at higher volumes and can be self-hosted. We choose based on your volume, budget and data requirements.
Are platform fees included?
No. Our price covers the studio's work. Segment or RudderStack subscriptions, the warehouse and hosting are billed separately to your own account. We give you an estimate before we start.
Who owns the data and accounts?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
What do you need from me?
Access to your site, CRM, ad accounts and email tool. We also need one person who decides what counts as a customer and which events matter to the business. That takes a few hours.
How does payment work?
Payment terms are agreed with the quote before work starts. For a staged project, we describe the result and acceptance criteria for each stage. Support and third-party services are listed separately.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.