FAQs - ProntoEngage

Q - Why is the 'New Campaign' button not visible on Campaigns Tab?

A - There may not be a New button if the user is not a 'Marketing User'.

Q - Can you import data to custom fields on the Campaign using ProntoEngage?

A - ProntoEngage is primarily a Campaign Member import, so unfortunately custom fields on a Campaign cannot be mapped. However custom fields on the Campaign Member can be mapped and imported to.

Q - When importing campaign members, do you need to create the campaign in Salesforce first?

A - ProntoEngage will check whether the Campaign exists, and if not, it will create a new Campaign in Salesforce and create the campaign members.

Q - Why is the campaign field required on the import page when I already have the Campaign name in the CSV file?

A - ProntoEngage upload the campaign members to the Campaign specified in you CSV file, and if there are any lines that do not have a specified campaign, it will use the Campaign on the Import page as the 'default'.

Q - Does ProntoEngage only check for existing leads in Salesforce?

A - It will check both Leads and Contacts for existing records based on the unique identifiers chosen, however it will only create Leads. You can then use the Mass Lead Conversion feature to convert them to Contacts if you wish.

Q - Do the Campaign to Opportunity mappings and the Opportunity to Contact Role mappings only apply when import a CSV file through ProntoEngage?

A - No, once the mapping has been created in ProntoEngage, they will apply whenever you are creating an Opportunity from a Campaign or just creating the Opportunity.

Q - A field from my opportunity layout is missing from the Campaign to Opportunity Mappings dropdown

A - Only fields that are editable and can be left blank (i.e not required) show on the list as available to map to.