Introducing Rules
mParticle customers can transform their data without source code updates to ensure that each service receives data in the correct format.
Today we are excited to introduce Rules, giving mParticle customers the ability to transform their data without source code updates to ensure that each service (such as their attribution vendor or marketing automation platform) receives data in the correct format.
Most companies have dozens of different platforms and tools in their growth stacks, which capture data in a variety of different ways. Sometimes the data gets keyed in manually by customer service reps, sometimes it’s system-generated or sometimes it’s collected via website “tags” or from mobile apps, configured by in-house developers or multiple external agencies.
The problem is that with every platform and tool speaks their own language, and multiple developers and agencies writing and updating code, there arise inconsistencies that make it difficult to combine the data together into a single, marketing-meaningful view.
Rules makes it easy for brands to manage the availability, usability and integrity of their data, providing a streamlined way to:
- Govern and Cleanse Data: For example rename all ‘completed transaction’ events coming from System X to ‘purchase’ events in mParticle
- Enrich and Manipulate Data: Enrich events with metadata not available in the app or client side. For example, whenever product id is collected, metadata such as product category and hierarchy can be added to the event.
mParticle customers can create a new rule by using our inline code editor to drop in a Javascript function or host it themselves as an AWS Lambda Function. They can then apply the rule to transform data across all their connected services, or selectively for a chosen few.
Check out the docs and contact us to learn more about Rules!
