| ISSUE 573728 | CPC incremental lift does not include an out-of-the-box omni-channel
model. | This issue will be fixed in an upcoming release. |
| ISSUE 576367 | Notifications for all paid media destinations are shown in the
Channels tab of Next-Best-Action Designer as a consolidated
list but do not indicate the hierarchy level where the notification was
generated. | This issue will be fixed in an upcoming release. |
| ISSUE 617478 | If a real-time offline conversion push and a historical conversion push both
fail, the Retry link only appears for the last failed
job. | This issue will be fixed in an upcoming release. |
| ISSUE 620539 | Offline event sets are not deleted from Paid Media tables after deleting a paid
destination. This can cause issues if you later create another destination with the
same name and type, but linked to a different ad account. | Do not create new destinations with the same name as a previously deleted
destination. Use a unique name instead. This issue will be fixed in an upcoming
release. |
| ISSUE 620546 | When a paid media destination setting is deleted in the
Channels tab of Next-Best-Action Designer, the sync jobs for
the deleted destinations still show up in the Paid media > Sync
tracking landing page. | This issue will be fixed in an upcoming release. |
| ISSUE 622565 | For real-time events executed for paid channels, actions in the Wait stage that
have been previously processed by next best action through an outbound run or
real-time event are filtered out in the response. | This issue will be fixed in an upcoming release. |
| ISSUE 594193 | If historical conversion push is triggered higher volumes in interaction
history tables (at around 30 million records in interaction history and at least 3
million records with an Accepted outcome), the historical conversion data flow fails
during initialization. | Create an index on the pr_data_ih_fact table for column
pzOutcomeID. This issue will be fixed in an upcoming
release. |
| ISSUE 641836 | The performance of paid runs with paid strategies including AI models is 10 to
15 times slower when delayed learning is enabled. | By default, delayed learning for models is disabled. If you want to configure a
paid strategy that includes adaptive models, see "Enabling delayed learning for paid
strategies" in the Pega Customer Decision Hub Implementation Guide. |
| ISSUE 640609 | Occasionally the progress of the historical conversion sync is not refreshed
after you click the Continue icon in the paid destination
settings. | No action is required. Although the progress is not refreshed, the sync job is
still initiated. You can view its status on the Paid media > Sync
tracking landing page. |
