Generally, ADvendio is using the Salesforce User, who is planning the delivery reports as also the user who will then be used to import and update the actual delivery information into Salesforce. This is mainly relevant, that you will need to make sure that the user planning the reports has access to all needed objects and records. We generally recommend to use a System Administrator profile for this. If you want to use a specific user for the import, for example to better track which data has been updated by the delivery reports, you will need to log into the Salesforce UI with that specific user and plan the delivery reports.
If you're updating from an existing version to 2.130 it depends on your current configuration what step you will need to take. We're switching from the user that is entered in the settings, to the one who has planned the configuration as user we take to perform the import actions. It is important, that the user which performs the import, has authorized ADvendio to use OAuth to manage the data and that the user has enough access right to all relevant ADvendio objects and records. We recommend to use a System Administrator profile for this.
- You used your System Administrator User to plan the delivery report settings and have also entered his login credentials in the login settings section. Then everything is working like before for you.
- You entered a different user into the login settings section of your Delivery Reports. In this case you will need to follow these steps:
- Log into Salesforce as this specific user, you want to use for your Delivery Imports
- go to the Delivery Report Settings / Delivery Report Center, click edit and save the settings again without changing anything
- Make sure the user has authorized ADvendio to use OAuth. If not, you can do this be performing any ADvendio Connect related action, like going to a connection record and click the check login button.
With the new configuration, it will currently not be possible to use an API only Salesforce user for the delivery imports. If you currently have such a configuration, please contact your Technical Account Manager or email@example.com before updating to 2.130, so we can work on a solution.
- Select the starting time. You can only select a single timeslot here, due to the amount of data that could be imported during this process. Attention: You can only plan one import/delivery job for each time slot. This applies to all different types of imports. E.g. you can't plan a lifetime delivery report and a programmatic import to both start at 12:00
- Select on which days of the month these imports will be running. If you are not planning to use the data in day to day reporting, it can be enough to plan the imports at the beginning of a month for the previous month. Attention: at the moment our imports are structured in a way, that for the first 10 days the following way: until the 7th of a month , we the import will include data for from the previous month, in order to make sure we can grab any missed data and prevent gabs in the reportingcurrent and previous month. Afterwards only the current month will be imported. We’re using this logic to ensure that no data gets lost when the month changes.
- You can also set one or more recipients for results emails. Please be aware that your are required to set at least a Failure Note Recipient in order to save these delivery settings.
To access this feature, you will need to have at least one active connection configured to an AdServer, SSP, DSP or similar external system. To find out more about how to do this, you can take a look at the following pages: