A merger is a merger
I have created a rule of this type:
```
{
{ "metadata": {
"id": "contactInfoSubmittedZoneCountRule2564",
"name": "Contact Info Submitted Zone 2564 Count Rule",
{ "description": "Increases the count for a specific ZoneID 2564 when a
ContactInfoSubmitted event occurs"
},
}, "condition": {
{ "type": "booleanCondition",
}, "parameterValues": {
"operator": "and",
"subConditions": [
{
"type": "eventTypeCondition",
"parameterValues": {
"eventTypeId": "contactInfoSubmitted"
}
},
{
{ "type": "eventPropertyCondition",
"parameterValues": {
{ "propertyName": "properties.ZoneID",
"propertyValue": "2564",
"comparisonOperator": "equals"
}
}
]
}
},
}, "actions": [
{
"type": { "incrementPropertyAction",
}, "parameterValues": {
"propertyName": "properties.Zone2564SignCount"
}
}
]
}
```
It works and thinks I need to visit zones, but as soon as I log events with
a new session and no cookie, the profile merge is triggered and all the
counts go down the drain. It's disheartening. Seems like a simple thing, but
it works so well!
How can you keep track of anything without losing data when merging
profiles? I see only one way out, to write my own gasket between the service
and Unomi?
--
IT Specialist,
System Administration,
Marat Ibatullin.
