Version 1.18.3 of Digital Source Tracker contains a number of improvements and fixes.
Release Schedule
| Name | Description | Date |
|---|---|---|
| Sandbox Update | All Digital Source Tracker installs in Sandboxes will receive the update automatically | TBD |
| Production Update | All Digital Source Tracker installs in production orgs will receive the update automatically | TBD |
Improvements & Fixes
Version 1.18.3 contains the following improvements and fixes.
- Touchpoint Capture Sync Timing Fix: Previously, Digital Source Tracker would not sync UTM values to a Campaign Member if there was a gap of more than 24 hours between the Response Date and the time that the site visit and its associated UTM values was tracked. This fix ensures that UTM values get synced for Campaign Members where the gap between the site visit and the Response Date is up to 31 days; this accounts for cases where there is a delay between the form submission and when the Marketing Automation Platform creates a Campaign Member in the Salesforce org.
- Removing the LinkedIn API Version from the Digital Source Tracker configuration page. Instead, the LinkedIn API version will automatically be set by the Digital Source Tracker package.
- Meta Ads Integration fixes
- Fixing a bug in the Meta Ads integration that caused an error if UTM values are null.
- The Meta Ads API does not allow retrieval of data for a date over 37 months from the current date. Previously, Digital Source Tracker would attempt to retrieve data from the Meta Ads API for dates over 37 months before the current date if a Digital Source Tracker Aggregate Database rebuild were triggered for those dates and would log an error. This fix ensures that Digital Source Tracker does not attempt to retrieve data from the Meta Ads API for dates over 37 months before the current date and exits gracefully instead.
Comments
0 comments
Please sign in to leave a comment.