Version 1.18.1 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 | 2/29/2024 |
| Production Update | All Digital Source Tracker installs in production orgs will receive the update automatically | 3/07/2024 |
Release At-a-Glance
|
Item |
Type |
Summary |
Automatically visible to all users |
Not automatically visible, requires some setup |
Contact Support to enable |
|---|---|---|---|---|---|
| LinkedIn API Update | Improvement | Additional updates to bypass LinkedIn API limitations of 100 creatives (ads) per day using batching techniques. | X | ||
| LinkedIn API Update | Improvement | Improved parsing of "+" symbols in LinkedIn UTM Parameters | X | ||
| Bing API Update | Improvement | Improved exception handling around the BingUtils class and the parsing of responses | X |
Post-release instructions
After improving any API call, you may want to re-run the Digital Source Tracker Aggregate Database Rebuild for any date range you are reporting on.
Steps
- Go to the Full Circle Platform Configuration page
- Click Digital Source Tracker "Configure" button
- Click the "Daily Aggregate Database Configuration" tab
- Change the "Daily Aggregation Database Rebuild Interval (Minutes)" to 1*
- At the bottom of the page, click the "Rebuild Aggregate Data" button
- Enter a date range and click the "Start Rebuild" button
- Change the "Daily Aggregation Database Rebuild Interval (Minutes)" back to 15*
* This is the minimum number of minutes between initiation of aggregation rebuild requests. If you are only rebuilding for a small number of days, the default value of 15 is fine. But if you are rebuilding for months at a time, it's best to set the value to "1" temporarily, so that the async requests will finish more quickly.
Comments
0 comments
Please sign in to leave a comment.