The Bizible Salesforce Package will include a field labeled “Enable Bizible Touchpoints” on the Campaign object. Once the field has been added to the page layout, it’ll appear similar to this:
The options available in the picklist are:
Please note that campaign members must have an email address associated to their record in order for Bizible to create a touchpoint. Without an email address, Bizible will not assign a touchpoint to the campaign member.
Campaign Sync Dates
With the installation of the package, Bizible will also include 2 date fields on the Campaign object: Touchpoint Start Date and Touchpoint End Date.
These dates tell Bizible when we should start or stop including Campaign Members from the Campaign into the touchpoint journey. You can either set one date, or both, or none at all.
Use Case for Touchpoint Start Date
Start date can be used in the case that an existing Campaign is used for tracking Leads and Contacts, but the user only wants to start measuring once new systems or processes have been in place, so they decide to set a start date once Bizible should start tracking those Campaign Members.
Use Case for Touchpoint End Date
Campaign Members are nested under Campaigns, and are related to a Lead or Contact. A Lead or a Contact can only be added once to a Campaign, which can be problematic depending on the use case of the Campaign. When a Campaign is synced, the campaign membership is used as a marketing activity that is put into the touchpoint journey and treated like a form fill.
Bizible Touchpoint Status
If enabled, Bizible will push a status value onto the Campaign Member across 4 different fields that’s included in the installed package: Touchpoint Status (Lead), Touchpoint Status (Contact), Touchpoint Status (Opportunity), and Touchpoint Status Date. This helps customers audit whether or not a touchpoint has been created as a Bizible Touchpoint or Bizible Attribution Touchpoint, depending on the object that it’s related to. The Touchpoint Status Date is simply the last date that the status was updated on the Campaign Member.
Bizible Touchpoint Date
With the installation of the package, Bizible also includes a field on the Campaign Member labeled “Bizible Touchpoint Date.” This allows the user to override the date that Bizible would use for the Touchpoint Date on the Touchpoint record.
This could be necessary if a list was uploaded days/weeks/months after an event actually occurred. There are ways to update all records at once, which is explained below.
To know if you need to use the Bizible Touchpoint Date or not, here are how the dates are determined by Bizible depending on the Sync Type that is selected for the Campaign.
If the Sync Type is set to “Include all Campaign Members,” the priority of setting the Touchpoint Date is from top to bottom:
If the Sync Type is set to “Include only ‘Responded’ Campaign Members,” the priority of setting the Touchpoint Date is from top to bottom:
Bulk Update Touchpoint Date
If a large number of Campaign Member records needs to be updated, you can use the Bulk Update Touchpoint Date button to mass edit.
If there are unique use cases that this interface doesn’t cover, you can also use the Data Loader to export the records, make the change, and upload the records back in.
Start by searching for the records and filtering the ones that you want to set a Bizible Touchpoint Date for.
If you don’t need to use the search and just apply the dates to every Campaign Member record, use the “Include All Records” checkbox (see screenshot below), which will check all records on all pages.
Select the date and time from the calendar picker. If you want to select the current date and time, click the date/time that is shown next to the calendar picker.
Once your date and time is set, click the Update Selected Records button to apply the changes.
Bizible does not import the Cost that is entered on the Campaign record.
The logic behind this is twofold. We would require that both the Start and End Date is set for the Campaign, which is typically not set. In addition, the way that costs are distributed between the start of the campaign and the end of the campaign is arbitrary because it can be divided by day or by month, or even by the number of Campaign Members.
Because Bizible’s Marketing Spend page provides the Campaign Id, you can export the Salesforce Campaigns with their Id and Cost, then map it to the Marketing Spend CSV. This allows the user more control over how much is allocated across each month.
Campaign Member Removal
The way that Bizible keeps up with any deleted records in Salesforce, whether they’re deleted Leads or Accounts or Opportunities is to see those records in the API and track that an entry is marked as “IsDeleted.” Unfortunately with Campaign Members, Salesforce introduced a different way of deleting these Campaign Members from a Campaign and they’re actually just marked as “removed” as opposed to “deleted” so the issue is that touchpoints were still living in Salesforce that were related to deleted Campaign Members.
To get around this issue, Bizible created a Bizible History object and a trigger to track whenever Campaign Members are removed and then delete the corresponding touchpoint. You will need Bizible Marketing Analytics package V6.15 or higher to use this feature.
|Marketo whats next|