A campaign goal calculates its actual from a semantic metric definition whose data resolves to a campaign. How you connect the data depends on where the campaign lives in your semantic model. Three examples show how the metric's data connects to the campaign in each case.
- Example: Track Delivered Emails for a Campaign Goal in Marketing Planning and Operations
The marketing team at Northern Trail Outfitters (NTO) sets a goal on an email campaign to deliver 50,000 marketing emails. They want the goal to track delivered emails automatically, without manual updates. Because the email data in Marketing Intelligence already includes the campaign, the admin creates one metric that counts delivered emails. Use this example when your metric's data already stores the campaign. - Example: Track Click-Through Rate for a Campaign Goal in Marketing Planning and Operations
The marketing team at Northern Trail Outfitters (NTO) sets a goal on an email nurture campaign to reach a 5% click-through rate. They want the goal to track click-through rate automatically, without manual updates. The engagement data connects to the campaign only through the email message. So, the admin uses that relationship to create a click-through-rate metric. Use this example when your metric's data doesn't store the campaign but connects to it through a related object that stores the campaign. - Example: Track Registrations for a Campaign Goal in Marketing Planning and Operations
The events team at Northern Trail Outfitters (NTO) sets a goal on a webinar campaign to reach 2,000 registrations. The registrations come from an external system, with no campaign field. They want the goal to track registrations automatically, without manual updates. So, the admin ingests the registrations as a custom data object, joins that object to the campaign, and then creates a metric that counts registrations. Use this example when your metric's data has no campaign field, so you join it to the campaign in the semantic model.