Before attempting to review or export trace logs, Ensure Tracing has been enabled, then perform the necessary action in CRM for the applicable Acoustic Campaign Integration feature.
Contact Insight Tracing Logs
Open a single Lead or Contact record that is set to Sync to Acoustic Campaign Campaign. Scroll to the Acoustic Campaign Integration section to see the Contact Insight iframe on the form.
When troubleshooting Contact Insight issues related to accessing Acoustic Campaign, review the following custom entity with Dynamics 365’s Advanced Find tool.
- Acoustic Campaign API Command
Ensure the following columns are included in the view for the API Command entity, some may have to be added using “Add Columns”
|Name||The API Command Name. “Get Token” would be the only command for Contact Insight.|
The Endpoint URL used to get an access token from Acoustic Campaign. The format should be like the following examples.
(# represents the pod number for your Acoustic Campaign organization)
The Service URI depends on the Endpoint set the Acoustic Campaign General Settings during the integration setup.
|Request||The API Request submitted to Acoustic Campaign|
|Response||The API Response received from Acoustic Campaign|
|Error Log||Displays any errors encountered while submitting or receiving the API call|
|Send Status||The status of the API call, “Succeeded” or “Failed”|
|Attempts||Number of attempts made to submit the API call. For “Get Token” the max is 3 before a complete failure is returned.|
|Access Token||The access token granted by Acoustic Campaign after the call was successful. For Acoustic Campaign Oauth access tokens, the length of time allowed for access is 4 hours. The same token will appear for other API commands submitted through CRM up 3 hours from when the initial “Get Token” request was created. For contact insight this means multiple record views will not generate a new “Get Token” command unless the access token expires.|
|Error Log Client||A summary of the Error|
|Error Log Full||Details of the Full Error|
|Created On||Date and Time the API Command was generated in CRM|
|Modified On||Date and Time the API Command was generated in CRM|
Send Acoustic Campaign Email and Campaign to Contact List Tracing Logs
When troubleshooting Send Acoustic Campaign Email issues review the following custom entities with Advanced Find
- Acoustic Campaign API Command
- Acoustic Campaign Fetch Manager
- Acoustic Campaign Fetch Processor
For the Send Acoustic Campaign Email feature the following additional API commands appear in ascending order
|Get List Metadata|
|Preview Mailing||Multiple instances are possible if viewing multiple templates within CRM|
|Init Scheduled Mailing|
|Add Recipients To Scheduled Mailing||Multiple instances appear for more than 100 recipients, Each instance represents a batch of 100 recipients|
|Commit Scheduled Mailing|
Ensure the following columns are included in the view for the Acoustic Campaign Fetch Manager entity, some may have to be added using “Add Columns”. The Fetch Manager offers extended logging of the “Add Recipients To Scheduled Mailing” API for each batch of recipient records (contacts and leads) to be added to an Acoustic Campaign Email
|Continuation Token||Similar to a Paging cookie for CRM’s API. A bookmark for the Acoustic Campaign API when handling batches of records in a request until the response is completed.|
|Attempts||Number of attempts made to submit the API call. For “Add Recipients To Scheduled Mailing” the max is 5 before a complete failure is returned.|
|Request||The API Request submitted to Acoustic Campaign for the Batch|
|Response||The API Response received from Acoustic Campaign for the Batch|
|Error Log||Displays any errors encountered while submitting or receiving the API call for the Batch.|
|Processor ID (optional)||Links to the related Acoustic Campaign Fetch Processor record for the batch|
|Batch ID||For Acoustic Campaign Mailing recipients, each batch of 100 recipients is assigned a Batch ID.|
|Created On||Date and Time the Fetch was generated in CRM|
|Modified On||Date and Time the Fetch was generated in CRM|
When troubleshooting CRM Campaign to Acoustic Campaign Contact List issues review the Acoustic Campaign Fetch Processor entity with Advanced Find.
Ensure the following columns are included in the view for the Acoustic Campaign Fetch Processor entity, some may have to be added using “Add Columns”
|Action||The Fetch Processor Action. Usually “Fetch” or “Count”|
The CRM Entity Type. Expected entities are
|Campaign||The CRM Campaign Name|
|Campaign ID||The CRM Campaign ID|
|Acoustic Campaign Campaign ID||
The Acoustic Campaign Campaign ID used by Scribe online to create the Acoustic Campaign Contact List. Usually corresponds with a “Count” Action.
A new id is created each time the “Sync Acoustic Campaign Campaign” action is performed, and the previously associated records are deleted, including the campaign members.
|List Info||When Dynamic Marketing Lists are involved, this will display the Query (FetchXML) used by CRM to obtain the recipients for the Contact Lists. Usually corresponds with a “Count” Action|
|Processed Lists||Displays the Marketing List(s) associated with the CRM Campaign that have been processed at that point in trace.|
|Is More Recipients||Yes or No , if more recipients need to be processed from the associated Marketing List(s)|
|Next Paging Cookie||A page counter showing the last recipient processed from the previous batch and next recipient to be processed for the next batch. (1000 records per page for campaign members, 100 for Email recipients) Usually corresponds with a “Fetch” Action|
|Current List||The current Marketing List being processed at that point in the trace.|
|Processing Lists||Displays the Marketing List(s) associated with the CRM Campaign still waiting to be processed at that point in the trace.|
|Batch Count||Number of Records being processed in the Batch|
|Batch Size||Number of Records allowed to process per Batch. 1000 for Campaign Members, 100 for Email Recipients|
|Total Recipients||Total Count of Members or Recipients that will be processed. Usually corresponds with a “Count” Action|
|Created On||Date and Time the Fetch or Count was generated by the “Sync Acoustic Campaign Campaign” or “Send Acoustic Campaign Email” action in CRM.|
|Modified On||Date and Time the Fetch or Count was generated by the “Sync Acoustic Campaign Campaign” or “Send Acoustic Campaign Email” action in CRM.|
Tip: The Fetch Manager and Fetch Processor columns can be combined in one view from the Fetch Manager entity. When adding columns to the Fetch Manager view, select the related Fetch Processor columns.
Click Results, then click “Export Acoustic Campaign…(API Commands, Fetch Managers or Fetch Processors)”. Select “Static Worksheet” for the export type. If an Acoustic Campaign CRMi Support case has been opened, attached the exported results to the case.