Usually events are triggered by user and defined in the sitemap. But is this the only way to do this? Here is how you can send multiple events to Marketing Cloud Personalization without adding it to the sitemap. Let’s send single, multiple and as many events as you want!
When you need to send additional events or test events?
Events are one of the key components in Marketing Cloud Personalization. We use them to track specific user behavior. We create segments from events, and we build rule-based Web Campaigns with them. Usually events are triggered by user and defined in the sitemap. But what if we want to record additional events in our dataset? And what if we want to add hundreads of them quickly?
During sitemap development, it is normal to define events using sendEvent() function. Then, when user will peform an action that will trigger this event, it will be sent to MCP. After about 10 minutes the event will be populated and available in Actions list and it will be ready to use in campaigns and segments.
But what if we have got a new Web Template with additional sendEvent() in its code? Do we need to trigger Web Campaign with this Template to gather this event? And what if we have dynamic event name with several variables in this Template - will we need to perform all possible sequences to gather all possible event name combinations? What if we clone the whole dataset and want to get all events names that we used in segments? Will we need to manually collect all these events once again?
Fortunately - we won’t.
Adding single ad-hoc event from the Marketing Cloud Personalization Web Campaign UI
One simple way to add new action is to add event manually in Web Campaign creation. Just create new Web Campaign, add Action to rules and write your custom event name.
Seems easy, right? Well, but it is not so perfect. Events added manually through Web Campaign creation are not treated as “normal events” that were sent properly from the user. So you can add new action for the Web Campaign, but they won’t be saved in the backend. Web Campaign will trigger when this action will be triggered by user, but the value will not be stored unless this will occur.
This option is perfect when you forget to perform one specific event, but already creating a Web Campaign, but not if you want to have this action stored in the backend.
Read also: [What is hyper-personalization?](/blog/what-is-hyper-personalization)
