Reports

Sent report

To view the sent report for your campaigns, click on “Sen report” menu, select the campaign from the dropdown and click on “Submit” button to see the details. Refer below image…

Top performing campaign report

Click on menu “Top performing campaign report”, enter the start date and end date and click on “submit” button.

Performance by campaign report

Click on menu “Performance by campaign report”, enter the start date and end date and click on “submit” button.

Contact Metrics:

Administrator will have to perform below mentioned steps to add contact metrix on contact object.   

            a. Go to Setup-> Profiles->

            b. Go to ->User profiles -> select appropriate User (admin/any other user) 

            c. Select ->Object -> setting ->Contacts>Select TDX contact layout > Save

d. If user wants to uninstall the package then user will have to remove the tdx layout and associate the default contact layout .Above mentioned steps can be used as a reference to perform this. Otherwise when user will try to uninstall the app an error will occur due  to layout.

   2. Email Tracking Statistics:

• This statistics provides information on your contact's engagement with any activity sent from the platform such as whether your contact has been sent an email, opened an email or clicked a link etc.
• User will see a section ‘TDX Email Tracking Statistics’ in Salesforce on the Contact summary page. Expanding which a button ‘Refresh List’ is shown to user.
• Clicking this button will fetch the first 15 statistics from TDX and display the same to Salesforce user.
• In case contact is not synced with TDX, salesforce user won’t be able to see any statistics here.
• API used:

              GET /v1/Contacts/Activity/{FieldName}/{FieldValue}

3. Subscriber List Membership:

• This tab provides all the Lists your contact belongs to along with the history.
• User will see a section ‘TDX Subscription List Membership’ in Salesforce on the Contact     summary page. Expanding which a button ‘Refresh List’ is shown to user.
• Clicking this button will fetch the first 15 contact list details from TDX and display the same to Salesforce user.
• In case contact is not synced with TDX, salesforce user won’t be able to see any data here.
• API used:

                GET /v1/Contacts/{FieldName}/{FieldValue}/ContactLists}

4. TDX Campaign History:

• This section provides the list of campaigns that the contact has been sent and interactions in relation to the campaign, such as opens or clicks.
• User will see a section ‘TDX Campaign History’ in Salesforce on the Contact summary page. Expanding which a button ‘Refresh List’ is shown to user.
• Clicking this button will fetch the first 15 campaign details from TDX and display the same to Salesforce user.
• In case contact is not synced with TDX, salesforce user won’t be able to see any data here.
• API used:

                 GET /v1/Contacts/{FieldName}/{FieldValue}/ContactCampaignSummary}

Contact Sync Data Cleanup For Contact Mapping Change 

Below are the cases which may require data cleanup. 

1. Add a new field mapping in Contact Mapping
2. Remove a Field mapping from Contact Mapping
3. Update a field in Contact Mapping
4. Change the Identifier Mapping 

For point 1, 2 and 3: 

There can be situation where user might need to add, remove or update a field in contact mapping but contact sync has already been executed many times. User can go and add/remove/update the field in mapping but they should be aware about below mentioned points

• The changes in field mapping will only be considered for the records which are going to be processed by the job after the change.
• The records and fields which have already been processed before this change and are in sync with the traction next will not be considered by the job automatically.
• If user want to apply the new changes in old records, they will have to update the previously sync records to make them eligible for next sync.
• The changes which have been done by the previous jobs cannot be roll backed.
• User should not trigger retry fail before clean up. All the requests which got failed earlier cannot be executed (User cannot trigger retry fail).
• A data cleanup is required from the TDX Sync Error Log .
• Delete all the records from TDX_Sync_Error_Log__c.

Change the Identifier Mapping:

If user need to change the identifier mapping and sync has already been executed multiple time then complete data cleanup is require by the Administrator before changing the identifier mapping. User should aware about below mentioned points and will have to perform action mentioned below.

• The fields and records which have been updated by the previous execution cannot be rolled back.
• Delete all the records from TDX Failed Contact Log (TDX_Failed_Contacts_Log__c).
• Delete all the records from TDX Sync Error Log (TDX_Sync_Error_Log__c).
• Null out the below mentioned fields of Contact object
  • SF_Identifier__c
  • TDX_Contact_Id__c
  • TDX_Duplicate_Contact__c
  • TDX_Global_Subscriber__c
  • TDX_Sync_Date__c
  • TDX_Sync_Error_Details__c
  • TDX_Sync_Status__c
• Delete all records from contact mapping custom setting (contact_field_mapping__c). Better to do entire mapping again.
• Update fields of ‘TDX Configuration Setting’ (tdx_configuration_setting__c) with below mentioned details. There will be only one record in this custom setting with Name ‘Admin Settings’.
  • Initial Sync Completed TDX to SF = False
  • Initial Sync Completed SF to TDX = False
  • is Identifier Mapping Batch Completed = False
  • Salesfoce to TDX Last Sync Date = Null
  • Last Sync Date Time = Null
• Now user will have to do the identifier mapping and wait for the batch job which populates the SF Identifier fields of contact object with new identifier value.
• Once the job is complete, user will map the remaining fields of the mapping.
• User will have to initiate the Initial Sync of Traction Next to Salesforce first.
• Then user will execute SF to TDX initial Sync.
• Once the initial sync completed, user can schedule or manually execute the records.