Skip to main content

Operational considerations for Salesforce Pardot Reader

Limitations

  • The Account Engagement API supports up to five concurrent transactions (see Get Started with Account Engagement API > Rate Limits). Exceeding this limit may cause your application to terminate.

  • When an object does not support incremental load, all records for that object are synced at each poll. To avoid duplicate records, enable Merge mode for the targets of such objects.

  • When an object does not have a createAt or updatedAt field and Striim can not otherwise determine a timestamp for the object, it will be duplicated in the target at every polling interval.

  • The Salesforce Pardot Reader formats all timestamps using the Striim server's timezone, regardless of the timezone configured on the Pardot instance. If the Striim server and the Pardot instance are not in the same timezone, created_at and updated_at values in WAEvents may not match the values returned by the Account Engagement API. To avoid this mismatch, ensure that the Striim server and the Pardot instance use the same timezone.