Event data is rich information that is important to leverage when planning sales and marketing campaigns. See this article for more information on event data and some examples on how to use it in your campaigns.
Event types in D&B Lattice support an option for users to configure specific attribute on the event they are interested in tracking. The table below shows the default attributes and configurations.
Event | What is configurable? |
1st Party Intent (Web Traffic) | Web Page URL |
Opportunity | Opportunity Stage |
Marketing Activity | Activity Type |
But, these defaults may not be sufficient. Your organization may have put the information in collecting additional information with each event and you would like to create aggregate attributes in the platform using this additional information.
Let's look at an example to understand this better. The table below shows a sample opportunity event data.
Date | ID | Account ID | Stage | Product |
2/24/2020 | 808278 | 0011M00002V4gdR | Commitment | Security |
8/22/2020 | 648025 | 0011M00002WLVny | Lost | Security |
6/12/2020 | 111657 | 0011M00002Vmmmz | Purchase | IoT |
11/26/2020 | 156439 | 0011M00002DmPn9 | Purchase | Mobility |
4/15/2020 | 34997 | 0011M00002DmRcv | Open | Mobility |
2/2/2020 | 473839 | 0014100001MXx3S | Complete | Networking |
By default, the product will allow you to track opportunities by Opportunity stage. But what if you wanted to track the # of opportunities in a given stage grouped by the product that the account is interested in?
This can be done by working with our Customer Success Team. To take advantage of custom attributes for event data, you will need to provide the following:
Attribute Name | Attribute Name in the event | Attribute Name in the event | Attribute Name in the event |
<Specify the name of the attribute> Note: This is the name you will see in the product |
<regular expression that identifies the event that should be included> | <regular expression that identifies the event that should be included> | <regular expression that identifies the event that should be included> |
Please note the following when defining your criteria:
- Any number of attributes can be included for your events
- The event must match the specified criteria for the attributes you define (e.g. If you specify 5 attributes, the event must have 5 outputs to map)
- If you intent to include all events regardless of value, use "*" (don't leave the field empty)
Based on these rules, if you want to use the product information from the event to create your attribute, here is how you can complete the table defined above.
Attribute Name | Stage | Product |
Security - Open Opportunities | Open | .*Security.* |
Mobility - Open Opportunities | Open | .*Mobility.* |
IoT - Open Opportunities | Open | .*IoT.* |
Network - Open Opportunities | Open | .*Network.* |
Security - Lost Opportunities | Lost | .*Security.* |
Mobility - Lost Opportunities | Lost | .*Mobility.* |
IoT - Lost Opportunities | Lost | .*IoT.* |
Network - Lost Opportunities | Lost | .*Network.* |
Security - Complete Opportunities | Complete | .*Security.* |
Mobility - Complete Opportunities | Complete | .*Mobility.* |
IoT - Complete Opportunities | Complete | .*IoT.* |
Network - Complete Opportunities | Complete | .*Network.* |
Comments
0 comments
Please sign in to leave a comment.