Marketing teams whose every segment turns into an engineering request
The most-used conditions move into data tags first, so marketers pick them on screen instead.
Customer Data Integration
A data design service that settles the events and user attributes a campaign needs and feeds them into OneSignal.
- Customer Engagement
- Strategy & design
- Build & onboarding
- Managed operations
01Overview
Service overview
Customer Data Integration defines the events and user attributes your campaigns need and builds the structure that sends them into OneSignal. The ceiling of a personalized campaign is set by the data, not the copy. Start piling things up without a rule for which behaviour becomes a custom event and which attribute is managed as a data tag (a Key-Value user property), and every new segment comes back as another engineering request. Collection items are settled by working backwards from the campaigns. Roles are divided with the analytics tools already in use before anything gets built.
02Who it fits
Where it fits
Product teams that have already piled events into an analytics tool
Items worth reusing are picked out of the collection scheme already in place, so the same event never gets planted twice.
Services whose member data sits scattered across systems
Identifiers from the app, the web, and the backend are tied to one person, then the items campaigns need get connected.
03What we deliver
Scope of delivery
01
Event and data taxonomy design
Working backwards from the campaign scenarios, the names and rules for custom events, user attributes, and data tags are set. Every item carries its use in writing, so data that nobody will use never gets created.
02
Identifier and event delivery
Following the agreed definitions, the integration that sends identifiers, custom events, and data tags into OneSignal is implemented, or your team's implementation is reviewed. Timing and format errors are caught at build time, stopping segment misfires.
03
Measurement role division
Between the analytics and attribution tools already in use and OneSignal, which number is read where gets settled. The same metric no longer reads differently in each tool, so performance debates get shorter.
How the service works
Connect the data each campaign needs
Define events and attributes from campaign needs, then align identifiers, transmission timing and measurement tools.
Define events and user attributes
Connect identifiers and data transmission
Align measurement and tool responsibilities
04Why this way
Points of difference
Each point lists the deliverable that backs it.
Data tags and events are divided by purpose
OneSignal has two data channels of different character. States that rarely change belong in data tags, behaviour with a timestamp in custom events; that division is what balances management cost against expressive power. Pile everything into events and segments slow down; pile everything into tags and journey triggers become impossible. So the purpose rule comes first.
Backed by
- CRM status assessment report
- Campaign design and data definition
Client work · Cooperative
Cooperative, company C — member management
Member records sat at the centre, and product, stock, and supplier management were built on the same data.
Learn moreThe data already there gets reused
When an organization that already runs analytics tools adopts CRM, planting the same event twice is common. The existing taxonomy is read first, items are split into reuse and new collection, and new implementation is kept to the minimum. With less left to implement, the engineering workload drops and the integration schedule shortens with it.
Backed by
- Working campaigns and integration records
- Performance report and expansion backlog
05How to start
From first call to kickoff
Every stage ends with an agreed scope and a deliverable in your hands.
Step 01
Assess the baseline
We gather campaign history, customer data structure, and channel status, and turn them into a baseline within two weeks of kickoff.
DeliverableCRM status assessment report
Step 02
Design the scenario
We fix one or two key campaigns against the KPIs and settle the data items they require at the design stage.
DeliverableCampaign design and data definition
Step 03
Build and verify
We build the channel integrations, segments, and journeys, then confirm missends and omissions through test sends.
DeliverableWorking campaigns and integration records
Step 04
Hand over and expand
We review results with you for four weeks after handover and agree the next quarter campaigns in priority order.
DeliverablePerformance report and expansion backlog
06Contract options
Ways to work together
- Remote delivery
- Fixed price
07Service levels
Service levels
2weeks
Baseline diagnosis after kickoff
1–2campaigns
Key campaigns set against the KPI
4weeks
Results reviewed after handover
08Example engagements
Client work and example engagements
Work we took on, plus example engagements where we have no case yet.
All client workA marketer who files a dev request every time a segment is needed
Assume every single segment has to start with a request to the development team.
Example approachFrequently used conditions go into data tags, behaviour that needs a timestamp into custom events.
Intended directionMarketers build segments with no engineering request.
Cooperative, company C — member management
Members, suppliers, products, and stock all had to run inside one system.
What we doMember records sat at the centre, and product, stock, and supplier management were built on the same data.
What it leavesWhat goes out to members, and the operations behind it, come from one record.
09FAQ
Frequently asked questions
A data tag is a Key-Value attribute holding a current state, such as a tier or a preferred category. A custom event is a timestamped behaviour record, such as a purchase or a sign-up. Segment conditions mostly rest on tags, journey triggers on events.
Under the OneSignal announcement, existing accounts need a paid plan for mobile push and in-app messages from October 1, 2026 once they exceed 1,000 MAU. Web push and email stay free, and IXC reviews the transition quote and plan selection with you.
OneSignal is a customer engagement platform used, by its own published figures, by one in four global app publishers. IXC supports adoption and operations in Korea for commerce, media, and gaming.
It splits into the OneSignal licence and the IXC service fee. The licence is usage-based on MAU, and the service fee is quoted per project or as a monthly subscription depending on scope. Send us an inquiry and we will follow up with a detailed quote.
We begin with campaign history, customer-data structure, and channel status. A baseline is prepared within two weeks of kickoff, then one or two key campaigns aligned with KPIs and their required data collection are finalized during design.
We review performance together for four weeks after handover. Results inform the performance report and priorities for campaigns to expand in the following quarter, recorded in an expansion backlog for the internal team.
We share the findings from the first stage, then agree scope and schedule on that basis before delivery. A finished request for proposal is not required: the current environment and the outcome you want are enough to start.
Engineering & Operations
2026-09-26 · 18 min read
Why a CRM still cannot run your campaign—check events, customer attributes and identifiers first
CRM data readiness checks whether the events, attributes, identifiers and receiving states needed for campaign decisions are correctly connected to the same customer. Visible events alone do not establish current eligibility after cancellations, withdrawals or account switches.
Reliability & Observability
2026-09-26 · 18 min read
Why abandoned-cart messages reach customers who already purchased
Prevent post-purchase cart reminders by checking Journey-entry and send-time eligibility separately and excluding customers whose order is in progress or complete. Investigate event delays, duplicates and identity errors independently.
Engineering & Operations
2026-09-26 · 23 min read
Preserving customer identity, subscription states, and campaigns when changing CRM tools
CRM migration is an operational transition that carries customer identity, messaging eligibility, active campaigns, and sending responsibility into a new environment. Even while the same customer exists in both tools, only one should own each business message.
12Related resources
Resources for this service
Guides and checklists you can use during review and kickoff.
See all resources
Guides
2026.04.16
OneSignal onboarding and data definition checklist
A checklist of what engineering and marketing agree on once adoption is decided, grouped into identity, events and properties, permissions, testing, and handover.
Guides
2026.09.10
OneSignal user identity and event specification kit
A practical specification and example for user-to-subscription relationships, event fields, delivery timing, and missing, duplicate, or out-of-order data.
Contact
Contact us
Tell us your current environment and target outcome, and our team will review it and reply.
Direct line
Phone lines are open weekdays 09:00–18:00
ServiceCustomer Data Integration
Collection and use of personal information
- Purpose · Responding to and following up on this inquiry
- Items · Name, company, work email, message, visit source (first page visited, referring site domain, campaign parameters)
- Retention · 36 months from the date consent is given
You may decline; the inquiry cannot be submitted without consent.
More ways to explore